content-strategy

Develop a content strategy covering editorial positioning, content pillars, formats, calendar, governance, and topical authority planning. Use this skill whenever the user wants to plan a content program, define content pillars, build an editorial calendar, structure topic clusters, set up content governance, or align content production with broader brand and SEO goals. Triggers on content strategy, content plan, editorial strategy, content pillars, content calendar, editorial calendar, topical authority, topic clusters, content governance, content roadmap, content production. Also triggers when the user is about to start producing content without a strategic plan.

Quality

77%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

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

Quality

Content

62%

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

This is a well-organized content strategy skill with a clear 5-layer framework and explicit workflow. Its main weaknesses are verbosity (explaining concepts like content formats and roles that Claude already understands) and lack of concrete filled-in examples showing what a completed strategy artifact looks like. The workflow is strong, but the referenced template files are missing from the bundle, undermining the progressive disclosure structure.

Suggestions

Add a concrete, filled-in example of a completed content strategy (even abbreviated) showing editorial positioning, one pillar with sub-topics, and a sample calendar row—this would significantly boost actionability.

Trim sections that explain concepts Claude already knows, such as the format dimensions breakdown (length, depth, type categories) and the roles list—replace with a concise checklist or table.

Provide the referenced bundle files (content-strategy-template.md, editorial-calendar-template.md) so the progressive disclosure structure actually functions, and move detailed governance/lifecycle content into those references.

Dimension	Reasoning	Score
Conciseness	The skill is well-structured but verbose in places. Sections like 'Content formats and types' enumerate dimensions (length, depth, type, originality, evergreen vs. timely) that Claude already understands. The 'Roles' list and format dimension breakdowns add bulk without adding novel insight. However, the framework itself and failure patterns are genuinely useful additions.	2 / 3
Actionability	The skill provides a clear framework and workflow steps, but guidance remains largely conceptual rather than executable. There are no concrete code/command examples (understandable for a strategy skill), but even the strategy outputs lack filled-in examples—the 'We help X' template is the only concrete example, and the editorial calendar description is abstract rather than showing a sample row. The template references help but aren't provided in the bundle.	2 / 3
Workflow Clarity	The 8-step workflow is clearly sequenced with an explicit first step to confirm inputs before proceeding. The production workflow within governance includes a clear pipeline (Idea → Brief → Outline → Draft → Edit → Review → Publish → Measure → Update or Retire). The failure patterns section serves as implicit validation checkpoints. Step 1 explicitly gates progress on missing inputs.	3 / 3
Progressive Disclosure	The skill references external files (content-strategy-template.md, editorial-calendar-template.md) and related skills (content-and-copy, landing-page-copy, etc.), which is good structure. However, no bundle files are provided, so the referenced templates don't actually exist. The main file itself is quite long (~200 lines of substantive content) with detailed inline content that could be split into reference files (e.g., the full pillar selection criteria, format dimensions, governance details).	2 / 3
	Total	9 / 12 Passed

Description

92%

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 that clearly articulates specific deliverables, provides comprehensive trigger terms, and explicitly states both what the skill does and when to use it. The only minor weakness is potential overlap with adjacent skills in SEO, brand strategy, or content writing domains, though the focus on strategic planning helps differentiate it. The description uses proper third-person voice and avoids vague language.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: editorial positioning, content pillars, formats, calendar, governance, and topical authority planning. These are distinct, well-defined deliverables.	3 / 3
Completeness	Clearly answers both 'what' (develop a content strategy covering editorial positioning, pillars, formats, calendar, governance, topical authority) and 'when' (explicit 'Use this skill whenever...' clause plus a detailed triggers list). Also includes a proactive trigger scenario.	3 / 3
Trigger Term Quality	Excellent coverage of natural trigger terms including 'content strategy', 'content plan', 'editorial strategy', 'content pillars', 'content calendar', 'editorial calendar', 'topical authority', 'topic clusters', 'content governance', 'content roadmap', and 'content production'. These are terms users would naturally use.	3 / 3
Distinctiveness Conflict Risk	While the content strategy niche is well-defined, terms like 'SEO goals', 'content production', and 'brand' could overlap with SEO-specific skills, brand strategy skills, or content writing/copywriting skills. The broad scope of 'content' could cause some conflict with adjacent skills.	2 / 3
	Total	11 / 12 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: rampstackco/claude-skills
Commit: c0b6ba8

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.