seo-onpage
Run a comprehensive on-page SEO audit or optimization pass covering title tags, meta descriptions, header structure, content quality, internal links, image optimization, URL hygiene, and on-page schema. Use this skill whenever the user asks to optimize a page, audit on-page SEO, fix titles or meta tags, review header structure, check internal linking, improve a single URL's search performance, or write SEO-friendly copy. Triggers on on-page SEO, page audit, title tag, meta description, H1, header structure, internal links, image alt, URL slug, page optimization, optimize this page, SEO this page. Also triggers for any single-page review where ranking, click-through, or relevance signal quality is the goal, even if the user does not say 'SEO' explicitly.
67
81%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
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 an excellent skill description that thoroughly covers specific capabilities, provides explicit trigger guidance with both a 'Use when' clause and a dedicated trigger term list, and carves out a clear niche around on-page SEO. It uses proper third-person voice throughout and balances comprehensiveness with clarity. The inclusion of the fallback trigger condition for non-explicit SEO requests is a thoughtful addition.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: title tags, meta descriptions, header structure, content quality, internal links, image optimization, URL hygiene, on-page schema, writing SEO-friendly copy. Very comprehensive enumeration of capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (comprehensive on-page SEO audit covering specific elements) and 'when' (explicit 'Use this skill whenever...' clause plus a 'Triggers on...' list). Both dimensions are thoroughly addressed. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would say: 'optimize a page', 'audit on-page SEO', 'fix titles or meta tags', 'review header structure', 'SEO this page', 'optimize this page', 'H1', 'URL slug', 'image alt'. Also includes the smart note about triggering even when the user doesn't say 'SEO' explicitly. | 3 / 3 |
Distinctiveness Conflict Risk | Clearly scoped to on-page SEO specifically, distinguishing it from technical SEO, off-page SEO, or general content writing. The specific triggers like 'title tag', 'meta description', 'H1', 'URL slug' create a distinct niche unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
62%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-organized, clearly structured on-page SEO skill with a strong workflow and useful 8-dimension framework. Its main weaknesses are the lack of concrete examples (no sample audit output, no example title tag rewrites) and moderate verbosity in the checklist items that could be tightened or offloaded to reference files. The referenced bundle files don't exist, which undermines the progressive disclosure strategy.
Suggestions
Add a concrete example of a scored dimension (e.g., a sample title tag scored as 'Needs work' with the specific fix and rewritten version) to boost actionability.
Include a brief example audit output snippet showing what the final markdown report looks like, so Claude has a concrete template to follow even without the referenced audit-template.md.
Trim the 8-dimension checklists to only non-obvious, high-value criteria and move the full detailed checklists into the referenced onpage-checklist.md file to improve conciseness and progressive disclosure.
Provide the referenced bundle files (audit-template.md, onpage-checklist.md, title-and-meta-patterns.md) to make the progressive disclosure structure functional.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is generally well-structured and avoids explaining basic SEO concepts at length, but some sections are more verbose than necessary. For example, the 'When to use' and 'When NOT to use' sections could be tighter, and some checklist items state obvious best practices that Claude would already know (e.g., 'No broken internal links', 'Lowercase, hyphen-separated'). However, the 8-dimension framework does provide genuinely useful, specific criteria. | 2 / 3 |
Actionability | The skill provides a clear framework and specific criteria for each dimension, but lacks concrete executable examples. There are no code snippets for inspecting HTML, no example audit output, no sample title tag rewrites, and no example of a scored dimension. The guidance is specific enough to follow but stops short of being copy-paste ready. | 2 / 3 |
Workflow Clarity | The 7-step workflow is clearly sequenced with logical progression from confirming inputs through rendering, auditing, prioritizing, and reporting. It includes validation checkpoints (confirm target query before proceeding, check crawlability before optimizing) and the 'Failure patterns' section serves as an effective error-recovery/pushback mechanism. The prioritization step (Critical/Important/Nice-to-have) adds a useful triage layer. | 3 / 3 |
Progressive Disclosure | The skill references three external files (audit-template.md, onpage-checklist.md, title-and-meta-patterns.md) with clear one-level-deep navigation, which is good structure. However, no bundle files were provided, meaning these references are broken. Additionally, the 8-dimension framework is quite detailed inline and some of it (especially the checklist-style items) could arguably live in the referenced checklist file to keep the main skill leaner. | 2 / 3 |
Total | 9 / 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 | |
- Repository
- rampstackco/claude-skills
- Commit
8e70d03
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.