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".

Quality

96%

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

Quality

Content

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

An exemplary lean redirect stub: maximally token-efficient, unambiguous, and single-purpose, delegating the real workflow to a canonical skill one level deep. The only structural weakness is that its entire function depends on an external sibling path (../../seo/content-planner/SKILL.md) that is not part of this bundle and cannot be verified from it.

Suggestions

Add a one-line fallback for when the canonical sibling skill is not installed (e.g., 'If that file is missing, report the missing dependency instead of proceeding'), so the skill degrades gracefully rather than silently failing.

Consider noting what the canonical file covers (one short clause), so a reader can confirm the delegation target is correct before committing context to reading it.

Dimension	Reasoning	Score
Conciseness	Two sentences, zero padding, no explanation of concepts Claude already knows. "Read ../../seo/content-planner/SKILL.md completely, then follow it as the active workflow. Resolve every relative reference from that file against ../../seo/content-planner/." — every token earns its place.	5 / 5
Actionability	For an instruction-only skill the guidance is fully concrete: it names the exact file to read, mandates reading it completely, and gives an explicit rule for resolving its relative references. Nothing is left ambiguous, matching the level-5 instruction-skill standard.	5 / 5
Workflow Clarity	A simple single-action skill whose one action — read the canonical workflow file and follow it, with a defined reference-resolution base — is unambiguous. No destructive or batch operations are described in the body, so no validation checkpoint is required under the simple-skill exception.	5 / 5
Progressive Disclosure	The body is a clear, well-signaled one-level-deep reference ("Resolve every relative reference from that file against ../../seo/content-planner/" keeps nesting at one level). Not a 5 because the sole reference points outside the skill's own bundle to a sibling directory that contains no files in the reviewed bundle — it is unverifiable here and fragile if the sibling skill is absent, with no local fallback content.	4 / 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 description: third-person, concrete, quantitatively specific about the analysis it performs, with an explicit and extensive 'Use when' trigger list. Its only weakness is slight trigger overlap with adjacent SEO/keyword-research skills.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete, specific actions covering the full pipeline — "Pulls real Search Console data", "finds the highest click-potential opportunities (striking-distance queries at positions 5-20, unanswered query intent, related-keyword expansions)", "produces a dated, prioritized content calendar" — with quantitative specifics. Not a 4 because coverage is comprehensive for the skill's stated scope rather than having minor gaps.	5 / 5
Completeness	Explicitly answers both questions: the "what" is the GSC data pull, opportunity analysis, and calendar output; the "when" is an explicit "Use when the user asks…" clause with concrete trigger phrases. Matches the level-5 good example structure exactly.	5 / 5
Trigger Term Quality	Ten natural user phrasings including synonyms and variations: "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", "schedule my SEO content". Comprehensive natural-term coverage matching the level-5 anchor.	5 / 5
Distinctiveness Conflict Risk	Clear niche (GSC-driven content planning) with distinct calendar/planning triggers and an explicit handoff boundary to /content-writer. Not a 5 because "find quick-win SEO topics" and "click-potential analysis" carry minor overlap risk with a closely related keyword-research skill.	4 / 5
	Total	19 / 20 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
relative_links	Relative link issues: 1 suspicious	Warning

	Total	14 / 16 Passed

Repository: nowork-studio/notfair-plugin
Path: skills/content-planner/SKILL.md
Commit: 5094263

Reviewed: 5 days 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.