tdg-personal/seo
Audit, plan, and implement SEO improvements across technical SEO, on-page optimization, structured data, Core Web Vitals, and content strategy. Use when the user wants better search visibility, SEO remediation, schema markup, sitemap/robots work, or keyword mapping.
79
79%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong skill description that clearly defines its scope across multiple SEO sub-domains, provides an explicit 'Use when' clause with natural trigger terms, and is distinctive enough to avoid conflicts with adjacent skills. It uses proper third-person voice and is concise without being vague.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Audit, plan, and implement SEO improvements' across clearly named domains including 'technical SEO, on-page optimization, structured data, Core Web Vitals, and content strategy.' | 3 / 3 |
Completeness | Clearly answers both 'what' (audit, plan, implement SEO improvements across technical SEO, on-page optimization, structured data, Core Web Vitals, content strategy) and 'when' with an explicit 'Use when...' clause listing specific trigger scenarios. | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'search visibility', 'SEO remediation', 'schema markup', 'sitemap', 'robots', 'keyword mapping', 'Core Web Vitals', 'structured data'. These cover a wide range of terms a user would naturally use when seeking SEO help. | 3 / 3 |
Distinctiveness Conflict Risk | The description carves out a clear SEO-specific niche with distinct triggers like 'schema markup', 'sitemap/robots work', 'keyword mapping', and 'Core Web Vitals' that are unlikely to conflict with other skills such as general web development or content writing. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
50%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a competent SEO skill that covers the domain broadly with reasonable structure and some concrete examples. Its main weaknesses are the lack of explicit validation workflows (e.g., how to verify that a robots.txt change didn't accidentally block important pages) and the inclusion of general SEO knowledge that Claude already possesses. The actionability is moderate — it provides good templates and thresholds but lacks executable tooling commands for performing actual audits.
Suggestions
Add explicit validation/verification steps for risky operations like robots.txt changes, redirect modifications, and canonical updates (e.g., 'After updating robots.txt, verify with: curl -A Googlebot <url>/robots.txt and confirm important paths are not blocked').
Remove or significantly trim content Claude already knows (Core Web Vitals thresholds, basic heading hierarchy rules, 'write for users first') and focus tokens on project-specific conventions or non-obvious patterns.
Split detailed sections (structured data recipes, technical SEO checklist, keyword mapping process) into separate referenced files to improve progressive disclosure and reduce the main skill's token footprint.
Add concrete tool commands or scripts for performing audits (e.g., using lighthouse CLI, checking sitemaps programmatically, validating structured data with schema.org validator).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Generally efficient but includes some content Claude already knows (e.g., Core Web Vitals thresholds, basic SEO principles like 'write for users first'). The principles section and some checklist items explain concepts that are common knowledge for Claude. However, it avoids egregious padding. | 2 / 3 |
Actionability | Provides concrete examples (JSON-LD, title formula, audit output shape) and specific thresholds (LCP < 2.5s, title 50-60 chars), but much of the content is checklist-style guidance rather than executable commands or copy-paste-ready code. The audit output shape is helpful but there are no actual tool commands or scripts for performing audits. | 2 / 3 |
Workflow Clarity | The skill implies a sequence (fix technical blockers before content optimization, keyword mapping has numbered steps) but lacks explicit validation checkpoints or feedback loops. For a multi-step audit process involving potentially destructive changes (redirects, canonical changes, robots.txt modifications), there are no verification steps to confirm changes worked correctly. | 2 / 3 |
Progressive Disclosure | Content is well-organized with clear sections and headers, but it's somewhat monolithic — the technical SEO checklist, on-page rules, keyword mapping, and internal linking sections could benefit from being split into referenced files. The 'Related Skills' section provides some cross-references but the main content is all inline with no progressive disclosure to deeper materials. | 2 / 3 |
Total | 8 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
Reviewed
Table of Contents