CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

80%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/seo-plan/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

68%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 skill skeleton with clean progressive disclosure into real asset files and useful error-handling guidance. Its weakness is depth of execution guidance: the core analysis and strategy steps name topics without methods, and the workflow lacks explicit validation checkpoints.

Suggestions

Add concrete methods for the vague analysis steps — e.g., how to estimate domain authority or what 'quality gates' means for the sitemap — or point to where in the asset templates those methods live.

Insert explicit validation checkpoints into the workflow (e.g., confirm business type and KPI targets with the user before generating the 12-month roadmap).

Fill in or replace the KPI table's '...' placeholder cells with example target values so the expected output format is concrete.

DimensionReasoningScore

Conciseness

The body is a lean outline of terse bullets that assumes Claude's competence throughout — E-E-A-T, Core Web Vitals, GEO, and schema concepts are used without explanation, and every section carries operational content. Only trivial redundancy exists (two error-table rows both resolving to generic.md), which is short of the "minor instances of over-explanation" that would drop it to anchor 4.

5 / 5

Actionability

Concrete elements are present (exact asset filenames, specific DataForSEO tool names, phase timelines, named deliverable files, error-table actions), but the core process steps are topic lists rather than instructions — "Estimate their domain authority" and "Sitemap structure with quality gates applied" give no method, and the KPI table is '...' placeholders. Key execution details are missing, matching anchor 3 rather than anchor 4's "minor gaps".

3 / 5

Workflow Clarity

The 6-step process is clearly sequenced with a phased roadmap and week ranges, and the error-handling table covers failure recovery. However, validation checkpoints in the main flow are absent or implicit — quality gates are mentioned but never defined, and there is no step confirming assumptions (e.g., business type) with the user — matching anchor 3. This is a planning skill, so the destructive/batch cap does not apply.

3 / 5

Progressive Disclosure

The overview appropriately splits industry detail into six well-signaled one-level-deep asset files, all of which exist in the bundle and are listed with their use cases. Minor organization gap: assets/ecommerce.md references schema/templates.json, which is not present in the bundle, a dangling referenced path that keeps this below anchor 5.

4 / 5

Total

15

/

20

Passed

Description

83%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 explicitly states capabilities and includes an explicit 'Use when' clause with eight concrete trigger phrases in third-person voice. The only weaknesses are minor: capability coverage and trigger synonyms have small gaps, and two triggers ("content strategy", "site architecture") create slight overlap risk with adjacent skills.

DimensionReasoningScore

Specificity

Names the domain and four concrete capability areas ("Industry-specific templates, competitive analysis, content strategy, and implementation roadmap") but presents them as deliverable nouns rather than actions, with minor coverage gaps (e.g., technical SEO, link building). Not anchor 5 because the action coverage is not comprehensive; above anchor 3 because more than 1-2 specific capabilities are listed.

4 / 5

Completeness

Clearly answers both what ("Strategic SEO planning for new or existing websites. Industry-specific templates, competitive analysis, content strategy, and implementation roadmap.") and when ("Use when user says 'SEO plan', 'SEO strategy', ... 'SEO roadmap'") with concrete trigger phrases — an explicit match for the anchor-5 pattern.

5 / 5

Trigger Term Quality

Eight natural trigger phrases ("SEO plan", "SEO strategy", "SEO planning", "content strategy", "keyword strategy", "content calendar", "site architecture", "SEO roadmap") with good synonym coverage across plan/strategy/roadmap. A few natural terms users would say are missing (e.g., "keyword research", "rank higher", "organic traffic"), so it falls short of anchor 5's comprehensive coverage.

4 / 5

Distinctiveness Conflict Risk

A clear SEO-planning niche with distinct triggers, but "content strategy" and "site architecture" are not SEO-specific and could overlap with content-writing or site-building skills — minor overlap risk per anchor 4 rather than the minimal-conflict profile of anchor 5.

4 / 5

Total

17

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

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

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.