seo-plan

Strategic SEO planning for new or existing websites. Industry-specific templates, competitive analysis, content strategy, and implementation roadmap. Use when user says "SEO plan", "SEO strategy", "SEO planning", "content strategy", "keyword strategy", "content calendar", "site architecture", or "SEO roadmap".

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

65%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-structured, token-efficient overview with excellent progressive disclosure into the assets directory. Its weaknesses are outline-level vagueness in the middle sections — no examples of what deliverables should contain and undefined "quality gates" — and no explicit validation checkpoints in the workflow.

Suggestions

Replace the placeholder KPI table ('| Organic Traffic | ... | ... |') and vague 'Success Criteria' bullets with either populated example values or a one-line instruction on how to fill them, so the output format is unambiguous.

Define the 'quality gates' mentioned under Sitemap structure (e.g., minimum content depth per page, cannibalization check) or reference where they are specified, so the Architecture step is actionable.

Add an explicit validation checkpoint mid-workflow, such as confirming the chosen industry template and scope assumptions with the user before generating the full deliverable set.

Dimension	Reasoning	Score
Conciseness	The body is a lean bullet outline with zero re-teaching of concepts Claude already knows — every line is a task item. Minor waste keeps it below a 5: the KPI table's "..." placeholder cells and the vague "Success Criteria" bullets ("Clear, measurable goals per phase") add tokens without actionable guidance.	4 / 5
Actionability	The outline names concrete artifacts (six template files, five named deliverables like `SEO-STRATEGY.md`, specific DataForSEO tool names), but the guidance itself is outline-level: "Content creation for primary pages" and "Sitemap structure with quality gates applied" give no detail on what the gates are or what deliverable content should look like. Missing key details place it at the 'some concrete guidance but incomplete' anchor rather than the mostly-executable one.	3 / 5
Workflow Clarity	The 6-step process (Discovery → Competitive Analysis → Architecture → Content → Technical → 4-phase Roadmap with week ranges) is clearly sequenced, and the error-handling table provides sensible fallbacks. However, validation checkpoints are absent or implicit — "quality gates" are mentioned but never defined, and there is no step to verify the plan with the user or check outputs before delivering, matching the 'steps listed but validation gaps' anchor.	3 / 5
Progressive Disclosure	The body is a genuine overview with all six industry templates correctly split into `assets/` (verified: saas.md, local-service.md, ecommerce.md, publisher.md, agency.md, generic.md all exist), each listed one level deep with a one-line use case. Content is appropriately separated and navigation is easy, matching the top anchor.	5 / 5
	Total	15 / 20 Passed

Description

91%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 clearly states what the skill does and when to use it, with an extensive set of natural trigger phrases. The only weaknesses are noun-phrase capability listing instead of concrete actions and a couple of generic trigger terms with mild overlap risk.

Dimension	Reasoning	Score
Specificity	The description enumerates four concrete capability areas ("Industry-specific templates, competitive analysis, content strategy, and implementation roadmap"), giving specific coverage of the domain. It falls short of a 5 because these are noun phrases rather than concrete actions, and sub-capabilities like technical SEO or link building are only implied by the body, not the description.	4 / 5
Completeness	It explicitly answers both questions: the "what" ("Strategic SEO planning for new or existing websites. Industry-specific templates, competitive analysis, content strategy, and implementation roadmap") and the "when" via an explicit "Use when user says..." clause with eight concrete trigger phrases, matching the top anchor exactly.	5 / 5
Trigger Term Quality	"Use when user says 'SEO plan', 'SEO strategy', 'SEO planning', 'content strategy', 'keyword strategy', 'content calendar', 'site architecture', or 'SEO roadmap'" provides comprehensive coverage of natural phrases users would actually say, including synonyms (plan/strategy/planning/roadmap). No common variations are obviously missing for this domain.	5 / 5
Distinctiveness Conflict Risk	The core triggers ("SEO plan", "SEO strategy", "SEO roadmap") occupy a clear niche with minimal conflict risk. However, "content strategy" and "site architecture" are somewhat generic phrases that could overlap with content-writing or web-development skills, placing this just below the top anchor.	4 / 5
	Total	18 / 20 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-seo
Path: skills/seo-plan/SKILL.md
Commit: 4b99de2

Reviewed: 3 days 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.