CtrlK
BlogDocsLog inGet started
Tessl Logo

content-planner

GSC-driven content calendar. Pulls real Search Console data, finds the highest click-potential opportunities (striking-distance queries at positions 5-20, unanswered query intent, related-keyword expansions), and produces a dated, prioritized content calendar — ready to hand to /content-writer. Use when the user asks "plan my content", "what should I write next", "content calendar", "content plan", "content roadmap", "editorial calendar", "what topics will rank", "find quick-win SEO topics", "click-potential analysis", or "schedule my SEO content".

75

Quality

94%

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

SKILL.md
Quality
Evals
Security

Quality

Content

92%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-engineered skill body: concrete formulas, a complete JSON schema, explicit sibling-skill boundaries, and a genuine quality-gate checklist with stop conditions. Progressive disclosure is exemplary with a single real reference file, and the only minor inefficiency is a handful of parenthetical rationales that could be trimmed.

DimensionReasoningScore

Conciseness

Largely lean and load-bearing with no concept padding (e.g. no explanation of what GSC is), but a few justificatory clauses ('The Cartesian view is the only one that lets you reason about intent', 'too many entries on the calendar becomes shelfware') could be trimmed without losing guidance.

4 / 5

Actionability

Fully executable guidance throughout — specific bucket thresholds (positions 5-20, impressions ≥100/90d), a concrete clickPotential formula, a complete copy-paste JSON schema, exact viewer invocation ('notfair-content-calendar [--port 8323]'), and a status lifecycle table.

5 / 5

Workflow Clarity

Seven clearly sequenced numbered steps with explicit validation checkpoints, including a dedicated Step 7 quality-gate checklist (GSC connection, <50 rows, bare-keyword titles, duplicate primaryKeywords, unhandled cannibalization) that gates shipping and stops on failure.

5 / 5

Progressive Disclosure

SKILL.md is a focused workflow overview with load-bearing logic offloaded to one clearly signaled one-level-deep reference ('See references/planning-methodology.md for the full classification rubric and the click-potential formula'), which is a real file present in the bundle; no nested references.

5 / 5

Total

19

/

20

Passed

Description

96%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, concrete description that names specific actions, enumerates natural trigger phrases, and answers both what and when explicitly. The only soft spot is mild overlap with sibling SEO skills that the description names but does not fully disambiguate within its own scope.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Pulls real Search Console data, finds the highest click-potential opportunities (striking-distance queries at positions 5-20, unanswered query intent, related-keyword expansions), and produces a dated, prioritized content calendar' — with comprehensive coverage of inputs, opportunity types, and output.

5 / 5

Completeness

Explicitly answers both what (GSC-driven content calendar from striking-distance/unanswered/related opportunities) and when (an explicit 'Use when the user asks...' clause with concrete trigger phrases).

5 / 5

Trigger Term Quality

Comprehensive coverage of natural phrases users would say — 'plan my content', 'what should I write next', 'content calendar', 'content plan', 'content roadmap', 'editorial calendar', 'find quick-win SEO topics', 'schedule my SEO content' — including synonyms and variations.

5 / 5

Distinctiveness Conflict Risk

Has a clear niche (GSC-driven prioritization vs brainstorming) and the description itself is bounded; minor overlap risk remains with closely related sibling skills (keyword-research, content-writer) which are named but not differentiated inside the description field.

4 / 5

Total

19

/

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
nowork-studio/NotFair
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.