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
- starl3xx/wallet-to-socialtheir own version, first seen Sep 22, 2026
- beelabstudio/aitheir own version, first seen Sep 20, 2026
- felvieira/claude-skills-fvtheir own version, first seen Sep 2, 2026
- aiunlocked1412/claude-skill-unlocktheir own version, first seen Apr 16, 2026
- nicolasestrem/antigravity-gemini-skillstheir own version, first seen Jan 17, 2026
- belokonm/claude-supercode-skillstheir own version, first seen Jan 12, 2026
Other versions6 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 6
- felvieira/claude-skills-fv★ 27same name
- aiunlocked1412/claude-skill-unlock★ 18same name
- belokonm/claude-supercode-skills★ 11same name
- nicolasestrem/antigravity-gemini-skills★ 8same name
- starl3xx/wallet-to-social★ 1same name
- beelabstudio/ai★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository174 other files it gives its agents.
- ab-test-analysisSkill
- accessibility-testerSkill
- ad-security-reviewerSkill
- agent-installerSkill
- agent-organizerSkill
- ai-engineerSkill
- ai-governance-auditorSkill
- ai-observability-engineerSkill
- ai-writing-auditorSkill
- angular-architectSkill
- anti-ui-slop-reviewerSkill
- api-designerSkill
- api-documenterSkill
- architect-reviewerSkill
- assumption-mappingSkill
- azure-databricks-platform-architectSkill
- azure-infra-engineerSkill
- backend-developerSkill
- backlog-groomingSkill
- backstage-specialistSkill
- blockchain-developerSkill
- browser-debuggerSkill
- build-engineerSkill
- business-analystSkill
- chaos-engineerSkill
- cli-developerSkill
- cloud-architectSkill
- codebase-orchestratorSkill
- code-mapperSkill
- code-reviewerSkill
- cohort-analysisSkill
- competitive-analystSkill
- compliance-auditorSkill
- content-marketerSkill
- content-quality-editorSkill
- context-managerSkill
- cpp-proSkill
- csharp-developerSkill
- customer-success-managerSkill
- data-analystSkill
- database-administratorSkill
- database-optimizerSkill
- data-engineerSkill
- data-researcherSkill
- data-scientistSkill
- debuggerSkill
- dependency-managerSkill
- deployment-engineerSkill
- design-bridgeSkill
- devops-engineerSkill
- devops-incident-responderSkill
- django-developerSkill
- docker-expertSkill
- docs-researcherSkill
- documentation-engineerSkill
- dotnet-core-expertSkill
- dotnet-framework-4.8-expertSkill
- dx-optimizerSkill
- electron-proSkill
- elixir-expertSkill
- The first 60 shown.
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
- Distinctive: line 33
verify recommendations map to concrete crawl/index issues in current setup
- Distinctive: line 35
check technical fixes for compatibility with existing rendering architecture
- Distinctive: line 36
ensure measurement plan distinguishes ranking variance from implementation impact
- Distinctive: line 37
call out search-console/log-based validations required outside repository context
- Distinctive: line 46
Do not guarantee ranking outcomes or propose manipulative tactics unless explicitly requested by the parent agent.
“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.
Files
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:
- Map the domain boundary and concrete workflow affected by the task.
- Separate confirmed evidence from assumptions and domain-specific unknowns.
- Implement or recommend the smallest coherent intervention with clear tradeoffs.
- 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.
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
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.

