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

73%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/content-strategy/SKILL.md

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 skill description with excellent trigger term coverage and clear differentiation from related skills. Its main weakness is that the 'what it does' portion could be more specific about concrete actions and deliverables (e.g., building topic clusters, creating editorial calendars, mapping content gaps). The explicit cross-references to related skills are a notable strength for reducing conflict risk.

Suggestions

Add more specific concrete actions/deliverables at the beginning, such as 'Builds topic cluster maps, creates editorial calendars, identifies content gaps, and prioritizes content ideas based on business goals.'

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,' and 'figure out what topics to cover,' but these are somewhat general and don't list multiple concrete, specific actions like 'build topic clusters, create editorial calendars, map content pillars to business goals.'	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) which further clarifies when to use it.	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	The description explicitly differentiates itself from copywriting, SEO audit, and social media skills with clear boundary statements ('not just writing it'). The focus on content planning and strategy decisions creates a distinct niche that is unlikely to conflict with other skills.	3 / 3
	Total	11 / 12 Passed

Implementation

57%

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

This is a comprehensive content strategy skill with good structure and progressive disclosure, but it suffers from verbosity and could be significantly tightened. The frameworks (searchable vs shareable, pillar structure, prioritization scoring) are genuinely useful, but much of the surrounding explanation covers marketing concepts Claude already understands. The workflow would benefit from explicit sequencing with validation checkpoints between major phases.

Suggestions

Trim explanatory text around well-known marketing concepts (buyer stages, what case studies are, what thought leadership means) — keep only the frameworks, templates, and decision criteria that are specific to this workflow.

Add an explicit numbered workflow at the top (e.g., '1. Gather context → 2. Research → 3. Identify pillars → 4. Validate pillar alignment → 5. Generate topics → 6. Prioritize → 7. Produce output') with validation checkpoints between phases.

Make the prioritization scoring more actionable by providing a concrete worked example showing how to score a real topic idea through all four factors, rather than just the template with placeholder numbers.

Dimension	Reasoning	Score
Conciseness	The skill is quite long (~250+ lines) and includes some content Claude would already know (e.g., general marketing concepts like buyer stages, what case studies are, basic keyword modifier patterns). However, the frameworks and structured templates add genuine value. Could be tightened by 30-40% without losing actionable content.	2 / 3
Actionability	Provides structured frameworks, scoring templates, and output formats which are useful, but lacks executable code/commands. The guidance is concrete in places (e.g., search query patterns like `site:reddit.com [topic]`, scoring templates) but much of it remains descriptive rather than directly executable. No actual tool usage examples or concrete step-by-step commands.	2 / 3
Workflow Clarity	The skill has a logical flow from gathering context → research → ideation → prioritization → output, but the sequence is implicit rather than explicitly numbered as a workflow. There are no validation checkpoints (e.g., 'verify pillars align with business goals before proceeding to topic selection'). The 'Before Planning' section establishes a good starting point but the overall process lacks explicit sequencing and feedback loops.	2 / 3
Progressive Disclosure	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` is appropriately placed. Content is structured for easy scanning with headers, tables, and bullet points. However, no bundle files were provided to verify the referenced path exists.	3 / 3
	Total	9 / 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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: coreyhaines31/marketingskills
Commit: 1145878

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.