blog-seo-check

Post-writing SEO validation with pass/fail checklist covering title tag length and keyword placement, meta description quality, heading hierarchy and keyword density, internal/external link audit with anchor text analysis, canonical URL verification, Open Graph meta tags (og:title, og:description, og:image), Twitter Card validation, structured data presence and validity, URL structure optimization, and image alt text presence. Produces prioritized fix list with specific recommendations. Use when user says "seo check", "check seo", "validate seo", "blog seo", "seo validation", "on-page seo", "title tag check", "meta description check", "heading check", "link audit".

Quality

96%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

92%

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

The body is lean, specific, and well-sequenced with concrete pass criteria and a copy-paste report template. Its main weakness is progressive disclosure: a long monolithic checklist with no split-out reference files.

Suggestions

Move the detailed per-check pass-criteria tables for lower-priority steps (e.g., OG, Twitter Card, structured data) into a reference file such as references/checks.md and link to it from SKILL.md to keep the overview concise.

Extract the full report template block into references/report-template.md and reference it from Step 11, leaving only the field summary inline.

Clarify that the references to skills/blog/references/flow-alignment.md and skills/blog-google/scripts/run.py point to sibling skills, or remove them if this skill is meant to be self-contained.

Dimension	Reasoning	Score
Conciseness	The body is a compact set of pass-criteria tables that assume Claude's knowledge without explaining what SEO, title tags, or structured data are, so most tokens earn their place. Minor prose such as 'Historical third-party anchor-text tests suggest...' adds a little non-essential context but does not pad with known concepts.	3 / 3
Actionability	Provides concrete, specific pass criteria (e.g., '3-10 internal links per post', 'og:image 1200x630 minimum dimensions, absolute URL', 'twitter:title under 70 characters') and a copy-paste-ready report template with concrete run.py commands, which is fully actionable for an instruction-only audit skill.	3 / 3
Workflow Clarity	A clearly numbered Step 1 through Step 11 sequence (with sub-steps 5.5 and 9.5) leads to a synthesized report with PASS/FAIL/WARN/N/A statuses and priority fixes, and Step 1 gates URL fetching behind explicit safety checks. The feedback-loop cap does not apply since this is a read-only audit rather than a destructive or batch operation.	3 / 3
Progressive Disclosure	The skill is monolithic: all per-check pass criteria and the full report template live inline in a ~220-line SKILL.md with no bundle files in references/, scripts/, or assets/, and its only file references point to other skills' files. This matches the anchor for some structure but content that should be separate being inline rather than the anchor for well-signaled one-level-deep references.	2 / 3
	Total	11 / 12 Passed

Description

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.

The description is highly specific, complete, and well-triggered, with concrete checklist coverage and a natural 'Use when' trigger clause in third-person voice. Its only weakness is verbosity — the long enumeration of checks could be tightened without losing clarity.

Suggestions

Tighten the description's enumerated checklist (e.g., group related checks) to reduce length while preserving the concrete actions and triggers.

Consider condensing the OG tag enumeration 'Open Graph meta tags (og:title, og:description, og:image)' to 'Open Graph meta tags' since the per-tag detail belongs in the body.

Dimension	Reasoning	Score
Specificity	Lists many concrete, distinct checklist actions such as 'title tag length and keyword placement', 'meta description quality', 'heading hierarchy and keyword density', 'internal/external link audit with anchor text analysis', 'canonical URL verification', and 'Open Graph meta tags (og:title, og:description, og:image)'. This matches the anchor for listing multiple specific concrete actions rather than naming a domain plus a few actions.	3 / 3
Completeness	Explicitly answers what ('Post-writing SEO validation with pass/fail checklist...Produces prioritized fix list with specific recommendations') and when ('Use when user says...'), matching the anchor for clearly answering both what AND when with explicit triggers.	3 / 3
Trigger Term Quality	Provides natural phrases a user would say including 'seo check', 'check seo', 'validate seo', 'blog seo', 'seo validation', 'on-page seo', 'title tag check', 'meta description check', 'heading check', and 'link audit', giving good coverage of common variations rather than jargon.	3 / 3
Distinctiveness Conflict Risk	The niche is clearly scoped to post-writing blog SEO validation with SEO-specific triggers unlikely to fire for unrelated skills, matching the anchor for a clear niche with distinct triggers and low conflict risk.	3 / 3
	Total	12 / 12 Passed

Validation

93%

Warnings & errors only

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

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: AgriciDaniel/claude-blog
Path: brain/.raw/sources/claude-blog-skill/skills/blog-seo-check/SKILL.md
Commit: aec971a

Reviewed: about 13 hours ago

Table of Contents

Discovery Implementation Validation

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.