CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

on-page-seo-checker

Use when the user asks to "audit on-page SEO" or "diagnose why a single page dropped"; scores titles, meta, header structure, keyword placement, links, and images with prioritized fixes. Not for E-E-A-T / publish-readiness scoring — use content-quality-auditor; not for crawl / CWV / indexing — use technical-seo-checker. 页面SEO审计/排名诊断

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

88%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-engineered instructional skill body: highly actionable, with an explicit step sequence, decision gates, and validation loops, and a clean split of detail into four real reference files. The residual issues are minor trimming opportunities and a handful of cross-bundle links whose targets are not verifiable from the skill itself.

Suggestions

Trim the JS-rendering fallback paragraph and the Decision Gates paragraph (which skill NOT to redirect to and why) to one line each, moving the rationale to a reference file — this tightens conciseness toward the lean anchor without losing routing behavior.

De-duplicate the 11-step list: keep one-line step names in SKILL.md and let references/audit-templates.md own the per-step criteria (Step Map plus checklists), reducing overlap between the body and the templates file.

Consolidate or inline the out-of-bundle pointers (skill-contract.md, CONNECTORS.md, SECURITY.md, core-eeat-benchmark.md) into a single 'Plugin resources' reference section so navigation does not depend on unverifiable relative paths.

DimensionReasoningScore

Conciseness

The body is efficient and assumes SEO domain knowledge (no concept teaching), but passages like the JS-rendering fallback paragraph and the Decision Gates explanation of why not to redirect to rank-tracker/content-writer/performance-monitor could be trimmed without losing guidance — minor over-explanation, not the pervasive padding of anchor 3.

4 / 5

Actionability

Guidance is fully executable: copy-paste commands (`python3 "${CLAUDE_PLUGIN_ROOT}/scripts/connectors/onpage.py" <url>`, the firecrawl scrape invocation), exact numeric criteria (title 50-60 chars, meta 150-160 chars, first 200 words, 2-3 samples per cluster), and a precise DOM query for JSON-LD verification cover the common cases.

5 / 5

Workflow Clarity

Eleven clearly sequenced steps with explicit Decision Gates (stop-vs-continue conditions), a keyword-inference fallback sub-procedure, validation via the Measured/User-provided/Estimated/N-A labeling rules, a false-negative confirmation loop for JS-injected JSON-LD, and a bulk path whose playbook flags extrapolation confidence and open loops — feedback loops and checkpoints are present throughout.

5 / 5

Progressive Disclosure

Structure is good: four real one-level-deep reference files (scoring-rubric, audit-templates, audit-example, bulk-audit-playbook), each well-signaled in the body and indexed in a Reference Materials section. It falls short of anchor 5 because the body's 11-step list overlaps the templates file's Step Map, and several links point outside the bundle (../../../references/skill-contract.md, ../../../CONNECTORS.md, ../../../SECURITY.md, sibling SKILL.mds) that cannot be verified within this skill's directory, creating minor navigation uncertainty.

4 / 5

Total

18

/

20

Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description that pairs concrete capability statements with explicit natural-language triggers and clear de-scoping of adjacent skills. The only weakness is modest synonym coverage of user phrasings beyond the two quoted trigger sentences.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — "scores titles, meta, header structure, keyword placement, links, and images with prioritized fixes" — giving comprehensive coverage of the on-page domain with no gaps, matching the anchor-5 example's breadth.

5 / 5

Completeness

It explicitly answers both questions with concrete trigger phrasing — "Use when the user asks to 'audit on-page SEO' or 'diagnose why a single page dropped'" for when, and the scored-elements list with prioritized fixes for what — matching the anchor-5 example structure.

5 / 5

Trigger Term Quality

Natural trigger phrases are present ("audit on-page SEO", "diagnose why a single page dropped") plus Chinese equivalents ("页面SEO审计/排名诊断"), but common user variations such as "check my page's SEO" or "why isn't my page ranking" are missing, so it sits at good-but-not-comprehensive coverage.

4 / 5

Distinctiveness Conflict Risk

Explicit negative boundaries ("Not for E-E-A-T / publish-readiness scoring — use content-quality-auditor; not for crawl / CWV / indexing — use technical-seo-checker") carve out a clear niche and actively route away neighboring skills, minimizing wrong-skill triggering.

5 / 5

Total

19

/

20

Passed

Validation

75%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 12 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

relative_links

Relative link issues: 15 suspicious

Warning

referenced_paths_exist

Referenced path issues: 1 missing, 1 deeper-than-1-level

Warning

Total

12

/

16

Passed

Repository

aaron-he-zhu/aaron-marketing-skills

Path

seo-geo/tune/on-page-seo-checker/SKILL.md

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.