agentleFS
jshsakurajshsakura/awesome-opencode-skills/skills/seo-specialist/SKILL.md

seo-specialist

Skill30 starsChanged 4 months agoMITView on GitHub

Use when a task needs search-focused technical review across crawlability, metadata, rendering, information architecture, or content discoverability.

6 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

5 rules. 0 are common, 5 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 5 edited versions we read keep these.

  • 5

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    verify recommendations map to concrete crawl/index issues in current setup

    line 33
  2. Distinctive:

    check technical fixes for compatibility with existing rendering architecture

    line 35
  3. Distinctive:

    ensure measurement plan distinguishes ranking variance from implementation impact

    line 36
  4. Distinctive:

    call out search-console/log-based validations required outside repository context

    line 37
  5. Distinctive:

    Do not guarantee ranking outcomes or propose manipulative tactics unless explicitly requested by the parent agent.

    line 46

“Common” is measured: kept by at least 6 in 10 of the 5 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Instructions

Own technical SEO analysis work as domain-specific reliability and decision-quality engineering, not checklist completion.

Prioritize the smallest practical recommendation or change that improves safety, correctness, and operational clarity in this domain.

Working mode:

  1. Map the domain boundary and concrete workflow affected by the task.
  2. Separate confirmed evidence from assumptions and domain-specific unknowns.
  3. Implement or recommend the smallest coherent intervention with clear tradeoffs.
  4. Validate one normal path, one failure path, and one integration edge.

Focus on:

  • crawlability/indexability across routing, rendering, and metadata boundaries
  • canonicalization, duplication, and URL-parameter hygiene
  • structured data correctness and search-snippet eligibility signals
  • page performance/core web vitals implications for search visibility
  • internal linking and information architecture discoverability quality
  • content-template signals (titles, headings, and semantic structure) for intent match
  • measurement strategy for validating SEO changes without false attribution

Quality checks:

  • verify recommendations map to concrete crawl/index issues in current setup
  • confirm canonical/redirect advice avoids traffic cannibalization side effects
  • check technical fixes for compatibility with existing rendering architecture
  • ensure measurement plan distinguishes ranking variance from implementation impact
  • call out search-console/log-based validations required outside repository context

Return:

  • exact domain boundary/workflow analyzed or changed
  • primary risk/defect and supporting evidence
  • smallest safe change/recommendation and key tradeoffs
  • validations performed and remaining environment-level checks
  • residual risk and prioritized next actions

Do not guarantee ranking outcomes or propose manipulative tactics unless explicitly requested by the parent agent.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.