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.

Quality

46%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/seo-content-planner/SKILL.md

Quality

Content

35%Scale 1-5

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

This skill reads more like a general description of SEO content planning than actionable instructions for Claude. It lacks concrete examples, specific methodologies, executable templates, or validation steps. The content is padded with concepts Claude already understands and provides only abstract guidance that wouldn't meaningfully improve Claude's ability to create content plans beyond its baseline knowledge.

Suggestions

Replace abstract steps like 'Analyze main topic comprehensively' with concrete, actionable instructions — e.g., specific frameworks for keyword research, exact prompts to use with search tools, or structured decision trees for prioritizing topics.

Add at least one fully worked example showing a complete topic cluster and content calendar for a real niche, so Claude can pattern-match rather than interpret vague guidance.

Remove explanations of concepts Claude already knows (what pillar pages are, what search intent means) and focus only on project-specific conventions, decision criteria, or non-obvious heuristics.

Either provide the referenced `resources/implementation-playbook.md` bundle file or remove the reference; dead links reduce trust in the skill's structure.

Dimension	Reasoning	Score
Conciseness	The skill is noticeably verbose with significant padding. It explains general SEO concepts Claude already knows (what a pillar page is, what search intent means), includes generic boilerplate instructions ('Clarify goals, constraints, and required inputs'), and lists focus areas that are essentially restating the description. The 'Do not use' section adds no value.	2 / 5
Actionability	The skill provides only high-level, vague guidance with no concrete, executable steps. There are no specific tools, commands, APIs, or real examples. The outline template is a skeleton with placeholders rather than actionable content. Instructions like 'Analyze main topic comprehensively' and 'Map search intent variations' are abstract descriptions, not concrete guidance.	2 / 5
Workflow Clarity	There is a numbered 7-step approach providing a rough sequence, but steps are vaguely defined ('Analyze main topic comprehensively') with no validation checkpoints. There's no feedback loop for verifying the quality of outputs or iterating on the plan. The deliverables section lists expected outputs but doesn't tie them back to specific workflow steps.	3 / 5
Progressive Disclosure	The skill references `resources/implementation-playbook.md` for detailed examples, which is good progressive disclosure in principle. However, no bundle files exist to support this reference, making it a dead link. The content itself is somewhat structured with headers but includes material inline (like the full topic cluster components list and content calendar format) that could be better organized or offloaded.	3 / 5
	Total	10 / 20 Passed

Description

58%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 covers the basics of what the skill does and provides a 'when' clause, which is good. However, it lacks comprehensive trigger terms and synonyms that users would naturally use, and the specificity of actions could be expanded. The distinctiveness is moderate — it could more clearly carve out its niche relative to other content or marketing skills.

Suggestions

Add more natural trigger terms and synonyms users would say, such as 'blog strategy', 'editorial calendar', 'keyword planning', 'content roadmap', or 'content plan'.

Make the 'when' clause more specific with concrete trigger scenarios, e.g., 'Use when the user asks about planning blog posts, organizing content topics, building a content calendar, or developing an SEO content strategy'.

Expand the list of concrete actions to improve specificity, such as 'performs keyword gap analysis, maps content to buyer journey stages, suggests internal linking structures'.

Dimension	Reasoning	Score
Specificity	Names the domain (SEO content strategy) and lists a few concrete actions (creates outlines, topic clusters, plans content calendars, identifies topic gaps), but coverage is not comprehensive — missing details like keyword research, competitor analysis, or content briefs.	3 / 5
Completeness	Has a clear 'what' (creates outlines, topic clusters, plans calendars, identifies gaps) and a 'when' ('Use PROACTIVELY for content strategy and planning'), though the 'when' clause is somewhat generic and could be more specific about trigger scenarios.	4 / 5
Trigger Term Quality	Includes some relevant keywords like 'content outlines', 'topic clusters', 'SEO', 'content calendars', and 'topic gaps', but misses common natural user phrases like 'blog strategy', 'keyword planning', 'editorial calendar', 'content roadmap', or 'content plan'.	3 / 5
Distinctiveness Conflict Risk	The SEO and content strategy focus provides some distinction, but terms like 'content planning' and 'content strategy' are broad enough to overlap with general marketing skills, editorial skills, or other SEO-related skills.	3 / 5
	Total	13 / 20 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

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

	Total	10 / 11 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: skills/seo-content-planner/SKILL.md
Commit: 57c135b

Reviewed: 23 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.