content-strategy

When the user wants to plan a content strategy, decide what content to create, or figure out what topics to cover. Also use when the user mentions "content strategy," "what should I write about," "content ideas," "blog strategy," "topic clusters," "content planning," "editorial calendar," "content marketing," "content roadmap," "what content should I create," "blog topics," "content pillars," or "I don't know what to write." Use this whenever someone needs help deciding what content to produce, not just writing it. For writing individual pieces, see copywriting. For SEO-specific audits, see seo-audit. For social media content specifically, see social.

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Quality

Content

85%

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

The body is a comprehensive, actionable content-strategy playbook with strong sequencing and a clean reference structure. Its main shortcoming is conciseness — several sections overlap and could be consolidated to reduce the token footprint.

Suggestions

Consolidate the duplicated hub/spoke and searchable-vs-shareable explanations that appear across the Content Types and Content Pillars sections to cut length.

Move the detailed keyword-research modifiers and scoring template into a reference file, keeping only the framework in SKILL.md to improve token efficiency.

Tighten the Content Ideation Sources section by merging the forum-research and competitor-analysis search-operator blocks into a single referenceable pattern.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and well-organized, but the ~360-line body restates some concepts (hub/spoke appears in both Content Types and Content Pillars; searchable vs shareable criteria repeat) and could be tightened to respect the token budget.	2 / 3
Actionability	Highly concrete guidance: stage-specific keyword modifiers, exact search operators ("site:reddit.com [topic]"), a weighted prioritization formula, ready-to-fill scoring tables, and a structured output format.	3 / 3
Workflow Clarity	A clear, well-sequenced process flows from Before Planning through Ideation and Prioritizing to Output Format; the skill involves analytical planning rather than destructive operations, so the absence of validation checkpoints is acceptable.	3 / 3
Progressive Disclosure	SKILL.md serves as an overview with a single, well-signaled one-level-deep reference to references/headless-cms.md (a real file), and content is appropriately split rather than deeply nested.	3 / 3
	Total	11 / 12 Passed

Description

100%

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 is a strong, trigger-rich statement of purpose that clearly answers both what and when, with explicit disambiguation against sibling skills. Its only weakness is verbosity — the long enumeration of trigger phrases could be trimmed without losing coverage.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "plan a content strategy, decide what content to create, or figure out what topics to cover" — matching the top anchor for listing several specific actions.	3 / 3
Completeness	Explicitly answers both what it does and when to use it via "Also use when the user mentions..." and "Use this whenever someone needs help deciding what content to produce," satisfying the top anchor.	3 / 3
Trigger Term Quality	Excellent natural-language trigger coverage including "content strategy," "what should I write about," "content ideas," "blog strategy," "topic clusters," and "I don't know what to write" — phrases users would actually say.	3 / 3
Distinctiveness Conflict Risk	Occupies a clear niche (deciding what content to produce, not writing it) and explicitly disambiguates from copywriting, seo-audit, and social, making misfires unlikely.	3 / 3
	Total	12 / 12 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: coreyhaines31/marketingskills
Commit: 30dbd7f

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.