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-content.
85
81%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Quality
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong description with excellent trigger term coverage and completeness, including helpful cross-references to related skills that reduce conflict risk. Its main weakness is that the 'what' portion is somewhat general—it describes the domain well but doesn't enumerate specific concrete deliverables or actions the skill performs (e.g., building topic clusters, creating editorial calendars, performing content gap analysis).
Suggestions
Add more specific concrete actions/deliverables the skill produces, e.g., 'Builds topic clusters, creates editorial calendars, performs content gap analysis, maps content pillars to audience segments, and prioritizes content opportunities.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain (content strategy/planning) and mentions some actions like 'plan a content strategy,' 'decide what content to create,' 'figure out what topics to cover,' but doesn't list multiple concrete specific actions (e.g., 'build topic clusters, create editorial calendars, map content pillars, identify content gaps'). | 2 / 3 |
Completeness | Clearly answers both 'what' (plan content strategy, decide what content to create, figure out topics) and 'when' with an extensive explicit trigger list. It also helpfully distinguishes itself from related skills (copywriting, seo-audit, social-content). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms including 'content strategy,' 'what should I write about,' 'content ideas,' 'blog strategy,' 'topic clusters,' 'content planning,' 'editorial calendar,' 'content marketing,' 'content roadmap,' 'blog topics,' 'content pillars,' and the very natural 'I don't know what to write.' These are terms users would actually say. | 3 / 3 |
Distinctiveness Conflict Risk | Explicitly differentiates itself from copywriting (writing individual pieces), seo-audit (SEO-specific audits), and social-content (social media content). The cross-references and the clear 'planning not writing' distinction make it highly distinguishable from related skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, well-structured content strategy skill that provides highly actionable frameworks, scoring templates, and research methodologies. Its main weakness is moderate verbosity—some marketing concepts are over-explained for Claude's knowledge level, and the workflow could benefit from explicit sequencing and validation checkpoints. The progressive disclosure and cross-referencing to related skills is excellent.
Suggestions
Tighten the 'When Writing Searchable Content' and 'When Writing Shareable Content' bullet lists—these describe general content marketing principles Claude already knows; reduce to only non-obvious, skill-specific guidance.
Add an explicit numbered workflow at the top (e.g., '1. Gather context → 2. Identify pillars → 3. Ideate topics → 4. Prioritize → 5. Validate with stakeholder → 6. Deliver strategy') with a validation checkpoint before final output.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but includes some sections that could be tightened. The 'Searchable vs Shareable' writing tips and buyer stage examples are somewhat verbose, explaining marketing concepts Claude likely already knows. However, most content earns its place with specific frameworks and templates. | 2 / 3 |
Actionability | The skill provides highly concrete, actionable guidance: specific keyword modifier formulas, scoring templates with weighted percentages, structured output formats, exact search queries for research (e.g., `site:reddit.com [topic]`), and clear content type formulas like '[persona] + [use-case]'. The prioritization scoring template is copy-paste ready. | 3 / 3 |
Workflow Clarity | The skill has a logical flow from gathering context → understanding content types → ideation → prioritization → output format, but lacks explicit validation checkpoints. There's no feedback loop for verifying strategy quality, no 'check with stakeholder' steps, and the sequencing between sections is implicit rather than explicitly numbered as a workflow. | 2 / 3 |
Progressive Disclosure | Content is well-organized with clear sections and headers. References to related skills (copywriting, seo-audit, programmatic-seo, etc.) are clearly signaled and one level deep. The reference to `references/headless-cms.md` and the product marketing context file are appropriately externalized. The skill serves as a comprehensive overview without burying content in nested files. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- coreyhaines31/marketingskills
- Commit
1bcff9f
- 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.