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

75%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/content-strategy/SKILL.md

Quality

Content

61%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-structured, actionable content-strategy guide that leans on real one-level-deep references and concrete templates. It is held back by rhetorical padding and a stray time-sensitive date that hurt conciseness, and by a planning workflow that lacks explicit validation checkpoints.

Suggestions

Trim editorial/rhetorical prose (e.g. the 'brand surface area' and 'Pouring effort…' passages) to keep the body lean and assume Claude's intelligence.

Move the time-sensitive citation ('Foundation Inc.'s B2B Backlink Intelligence Report, March 2026') into a dated/deprecated-style note or strip the specific date so it doesn't age the skill and penalize conciseness.

Add an explicit validation/feedback checkpoint to the planning workflow (e.g. after gathering context, confirm the pillars and prioritization against the stated business goal before producing the final output).

Dimension	Reasoning	Score
Conciseness	Mostly substantive domain guidance, but padded with rhetorical/editorial prose ('brand surface area… hundreds of doorways working 24/7', 'Pouring effort into a single flagship…') and a time-sensitive date (March 2026) embedded in the main body, fitting the 'mostly efficient but could be tightened' anchor.	3 / 5
Actionability	Provides concrete, executable guidance—keyword-modifier tables by buyer stage, a weighted scoring template with formula, copy-paste search operators ('site:reddit.com [topic]'), and a defined output format—matching the 'mostly executable with minor gaps' anchor; a few sections remain abstract ('Identify opportunities: Topics you can cover better').	4 / 5
Workflow Clarity	The 'Before Planning' section sequences context-gathering (steps 1-4) and the Output Format sequences deliverables, but there are no explicit validation/feedback checkpoints in the process, matching the 'steps listed but checkpoints missing or implicit' anchor.	3 / 5
Progressive Disclosure	Clear section structure with two real one-level-deep references (content-distribution.md, headless-cms.md, both verified present) and a related-skills block; fits the 'good structure, mostly well-placed, minor organization gaps' anchor given the long inline body.	4 / 5
	Total	14 / 20 Passed

Description

90%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 with comprehensive natural trigger terms, explicit what/when guidance, and clear disambiguation from related skills. The only soft spot is specificity, where the stated actions are high-level planning verbs rather than concrete capabilities.

Dimension	Reasoning	Score
Specificity	Names the domain with a few actions ('plan a content strategy, decide what content to create, or figure out what topics to cover'), but they are high-level verbs rather than concrete capabilities, matching the 'names domain and 1-2 concrete actions' anchor and falling short of the multi-action list at 4.	3 / 5
Completeness	Explicitly answers what ('help deciding what content to produce, not just writing it') and when ('Also use when the user mentions…' / 'Use this whenever someone needs help deciding what content to produce') with concrete trigger phrases, matching the top anchor.	5 / 5
Trigger Term Quality	Comprehensive natural trigger coverage including synonyms and phrasings users actually say ('content strategy,' 'content ideas,' 'blog strategy,' 'editorial calendar,' 'content pillars,' 'what should I write about,' 'I don't know what to write'), matching the comprehensive-coverage anchor.	5 / 5
Distinctiveness Conflict Risk	Explicit disambiguation ('For writing individual pieces, see copywriting. For SEO-specific audits, see seo-audit. For social media content specifically, see social') carves a clear niche with minimal conflict risk, matching the top anchor.	5 / 5
	Total	18 / 20 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
Path: skills/content-strategy/SKILL.md
Commit: 5b2c000

Reviewed: ~3 hours 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.