CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

seo-content-planner

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

Quality

70%

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 ./skills/seo-content-planner/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

53%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 body is well-organized with a useful output template and a logical planning sequence, but it is undermined by boilerplate filler and high-level steps that describe goals rather than methods. Adding concrete techniques for gap identification and intent mapping plus verification checkpoints would lift the actionable quality substantially.

Suggestions

Delete the circular 'Use this skill when' / 'Do not use this skill when' sections and the generic Instructions bullets; they duplicate the frontmatter description and add tokens without guidance.

Add concrete methods for the vague steps: e.g., how to identify content gaps (compare competitor cluster coverage against existing pages), how to map search intent, and a worked example of a filled-in outline.

Add verification checkpoints to the Approach, such as 'confirm every outline section maps to a stated search intent before generating the calendar' and 'check the cluster map covers all identified subtopics'.

DimensionReasoningScore

Conciseness

The domain material (Focus Areas, Planning Framework, Output template) is lean, but roughly 16 of ~98 lines are filler: the circular trigger sections ('Working on seo content planner tasks or workflows' restates the skill name) and generic Instructions bullets ('Clarify goals, constraints, and required inputs'). More than minor trimming (not 4), but no over-explanation of known concepts (not 2).

3 / 5

Actionability

Concrete artifacts exist — an outline template block and a calendar format spec — but the 'how' is missing for key steps: 'Identify subtopics and angles', 'Map search intent variations', and 'Priority scoring for topics' describe rather than instruct, with no method or worked example. Guidance is present but incomplete with missing key details (not 4).

3 / 5

Workflow Clarity

The Approach gives a coherent 7-step sequence (analyze topic, subtopics, intent, outline, linking, formats, prioritize), matching 'steps listed but validation gaps'. Not 4 because no checkpoints are present (e.g., verify each outline section maps to a search intent before building the calendar); the destructive/batch cap does not apply since this is generative planning.

3 / 5

Progressive Disclosure

No bundle files exist and the body is well-sectioned with clear headers at overview level — good structure with minor gaps. Not 5 because at ~98 lines it exceeds the under-50-line simple-skill allowance and the detailed outline/calendar templates could be offloaded to a reference file; not 3 because nothing is a monolithic wall or misplacement.

4 / 5

Total

13

/

20

Passed

Description

75%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 solid description that names the SEO content-planning niche and four concrete capabilities with an explicit use clause. Its main weaknesses are the generic 'when' phrasing and missing natural synonyms that would strengthen trigger matching and distinctiveness.

Suggestions

Replace 'Use for content strategy and planning' with concrete trigger phrases, e.g. 'Use when the user asks for a content plan, topic clusters, an editorial or content calendar, or SEO content strategy'.

Add natural synonym terms users actually say — 'content marketing', 'editorial calendar', 'keyword research' — to broaden trigger coverage.

DimensionReasoningScore

Specificity

Lists several concrete actions — 'Creates comprehensive content outlines and topic clusters', 'Plans content calendars', 'identifies topic gaps' — matching the several-specific-actions anchor. Falls short of 5 because the actions are deliverable-level rather than fully concrete operations, and capabilities like keyword research and search intent mapping are not mentioned.

4 / 5

Completeness

Clearly answers 'what' (outlines, topic clusters, calendars, gap identification) and includes an explicit 'when' clause ('Use for content strategy and planning'). Not 5 because the when-clause is generic and lacks concrete trigger phrases such as 'when the user asks for a content plan or editorial calendar'.

4 / 5

Trigger Term Quality

Includes natural terms users would say: 'SEO', 'content strategy', 'content calendars', 'topic clusters'. Good coverage per the score-4 anchor, but not comprehensive — common variations like 'content marketing', 'editorial calendar', 'keyword research', or 'blog planning' are missing.

4 / 5

Distinctiveness Conflict Risk

'Topic clusters for SEO' carves a mostly distinct niche with minor overlap risk against general content-writing or marketing-strategy skills. Not 5 because 'content strategy and planning' is broad enough to overlap with those closely related skills.

4 / 5

Total

16

/

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

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

rmyndharis/antigravity-skills

Path

skills/seo-content-planner/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.