CtrlK
BlogDocsLog inGet started
Tessl Logo

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审计/排名诊断

72

Quality

92%

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

85%Weight 40%Scale 1-3

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

The body is a well-structured, actionable audit workflow with strong progressive disclosure and clear decision-gate checkpoints; its main weakness is conciseness, with redundant example prompts and some lengthy prose blocks that could be trimmed.

Suggestions

Consolidate the five Quick Start example prompts into 2-3 representative prompts plus a one-line note, since several (single-page, competitor compare, pre-publish) overlap heavily.

Tighten the Data Sources section: move the firecrawl JS-rendering fallback detail into references/ or a short bullet, keeping only the invocation command inline.

Consider moving the full 11-step instruction detail into references/audit-templates.md and keeping SKILL.md as a tighter overview that points to it, reducing inline token load.

DimensionReasoningScore

Conciseness

The body is mostly efficient and SEO-specific, but several sections could be tightened: Quick Start lists five near-duplicate example prompts, and the Data Sources firecrawl-fallback paragraph is lengthy prose. It avoids explaining general concepts Claude knows, so it is above level 1, but does not earn level 3 due to padding.

2 / 3

Actionability

Provides concrete executable commands (e.g. `python3 "${CLAUDE_PLUGIN_ROOT}/scripts/connectors/onpage.py" <url>`, `document.querySelectorAll('script[type="application/ld+json"]')`) plus specific thresholds (50-60 char titles, 150-160 char meta); per scoring_notes, instruction-style guidance with concrete specifics is actionable for an audit skill.

3 / 3

Workflow Clarity

An 11-step sequenced workflow with explicit Decision Gates ("Stop and ask when" / "Continue silently") and a "Done when" verification criterion serves as clear checkpoints; the read-only audit scope and routing of batch work to the playbook avoid the destructive-operation cap.

3 / 3

Progressive Disclosure

Clear overview with one-level-deep references to real bundle files (audit-templates.md, audit-example.md, bulk-audit-playbook.md, scoring-rubric.md), all confirmed present in references/, and a dedicated Reference Materials section with descriptions — easy navigation, no nested reference chains.

3 / 3

Total

11

/

12

Passed

Description

100%Weight 40%Scale 1-3

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

The description is exemplary: concrete actions, natural trigger terms, explicit what-and-when guidance, and explicit conflict avoidance against sibling skills. Voice is third-person throughout, consistent with the rubric's voice guideline.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "scores titles, meta, header structure, keyword placement, links, and images with prioritized fixes" — matching the level-3 anchor of several specific concrete actions rather than a vague domain mention.

3 / 3

Completeness

Explicitly answers both what ("scores titles, meta, header structure...") and when ("Use when the user asks to 'audit on-page SEO' or 'diagnose why a single page dropped'") with explicit triggers, matching the level-3 anchor.

3 / 3

Trigger Term Quality

Natural user phrasing is present ("audit on-page SEO", "diagnose why a single page dropped") with good coverage of terms a user would actually say; not jargon-only or generic.

3 / 3

Distinctiveness Conflict Risk

Carves a clear niche with explicit negative guidance — "Not for E-E-A-T / publish-readiness scoring — use content-quality-auditor; not for crawl / CWV / indexing — use technical-seo-checker" — making it unlikely to trigger for the wrong skill.

3 / 3

Total

12

/

12

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.

Validation12 / 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
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.