CtrlK
BlogDocsLog inGet started
Tessl Logo

seo-content-planner

Creates comprehensive content outlines and topic clusters for SEO. Plans content calendars and identifies topic gaps. Use PROACTIVELY for content strategy and planning.

52

Quality

58%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/seo-content-planner/SKILL.md

The canonical home for this skill is seo-content-planner in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

57%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.

The content is well-organized and reasonably concise for an instruction-only skill, but it lacks executable steps and validation checkpoints, and its only external reference points to a non-existent file. Tightening actionability and fixing the reference would meaningfully improve it.

Suggestions

Add concrete, actionable steps: specify how to derive keywords/intent (e.g., tools or explicit heuristics) and how priority scores are computed rather than just listing 'prioritize creation order'.

Fix or remove the broken reference to 'resources/implementation-playbook.md' (no such bundle file exists), or create the referenced file and signal it clearly as one-level-deep.

Add a validation checkpoint to the workflow — e.g., verify the outline covers the stated intent and that internal links form a coherent cluster before finalizing deliverables.

DimensionReasoningScore

Conciseness

The body is mostly efficient with well-organized bullet lists and a compact output template; it avoids explaining SEO basics Claude already knows, with only minor padded phrasing like 'You are an SEO content strategist'.

4 / 5

Actionability

It gives structured deliverables and an outline template, but guidance is descriptive rather than executable — there is no concrete tool, command, keyword-research step, or copy-paste procedure, fitting the 'some concrete guidance but incomplete; missing key details' anchor.

3 / 5

Workflow Clarity

The 'Approach' section lists a numbered sequence, but it is a linear plan with no validation checkpoints, feedback loops, or verification of outputs for a planning skill that produces multiple deliverables — matching the 'steps listed but checkpoints missing' anchor.

3 / 5

Progressive Disclosure

The body is essentially a monolithic single-file list with one buried, dangling reference ('open resources/implementation-playbook.md') to a file that does not exist in the bundle, so structure is minimal and the one reference is broken — matching the 'minimal structure; references buried/broken' anchor.

2 / 5

Total

12

/

20

Passed

Description

58%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.

The description states concrete capabilities and signals proactive use, but the 'when' trigger is generic ('content strategy and planning') rather than concrete user phrases, and natural trigger terms lack synonyms. It is a competent but not maximally explicit description.

Suggestions

Add concrete trigger phrases users would say, e.g. 'Use when the user asks to plan an editorial calendar, build a topic cluster, map search intent, or find content gaps.'

Include natural synonyms such as 'SEO', 'editorial calendar', 'keyword clusters', and 'pillar pages' to broaden trigger-term coverage.

Tighten the 'Use PROACTIVELY' clause into an explicit 'Use when...' statement to lift completeness above 3.

DimensionReasoningScore

Specificity

Names concrete actions like 'Creates comprehensive content outlines and topic clusters', 'Plans content calendars', and 'identifies topic gaps' — several specific actions with only minor coverage gaps, matching the 'several specific actions' anchor.

4 / 5

Completeness

It clearly states the 'what' (create outlines, plan calendars, identify gaps) and offers a 'when' via 'Use PROACTIVELY for content strategy and planning', but the trigger is generic guidance rather than concrete trigger phrases, so the 'when' is weakly explicit — capping completeness at 3 per the missing-explicit-trigger guideline.

3 / 5

Trigger Term Quality

Contains relevant terms ('content outlines', 'topic clusters', 'content calendars', 'content strategy') but is missing common natural variations or file/format synonyms a user would say; matches the 'some relevant keywords but missing common variations' anchor.

3 / 5

Distinctiveness Conflict Risk

The SEO content-planning niche is mostly distinct from other skills with only minor overlap risk against general writing or marketing skills, fitting the 'mostly distinct; minor overlap risk' anchor.

4 / 5

Total

14

/

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.

Validation15 / 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
administrakt0r/AI-Agents-Safe-Coding-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.