CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

87%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

The canonical home for this skill is content-strategy in rampstackco/claude-skills

SKILL.md
Quality
Evals
Security

Quality

Content

86%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, highly actionable strategy skill: the 5-layer framework, failure patterns, output format, and real templates give Claude everything needed to produce the deliverable. Minor room to tighten editorial phrasing and add an explicit strategy-review checkpoint.

Suggestions

Add an explicit validation step to the workflow (e.g., review the drafted strategy against business goals and capacity with the user before documenting), pairing with the existing confirm-inputs checkpoint.

Trim editorial asides ('Skip layers and the program drifts', 'A stated gap is a complete answer') and the generic unavailable-data boilerplate to a single sentence each to improve token efficiency.

Flesh out the measurement plan slightly (one or two example metric sets per business goal), since it is the only output-document section with no supporting detail in the body.

DimensionReasoningScore

Conciseness

The body is dense and directive with concrete numbers ('3 to 5 pillars', word-count bands, cadence options), and it skips generic concept explanations Claude already knows. A few editorial flourishes ('Skip layers and the program drifts') and a boilerplate data-gap section keep it just short of the lean anchor.

4 / 5

Actionability

For an instruction-only skill the guidance is fully concrete: per-pillar definitions with counts, an example positioning sentence ('We help [audience]...'), format dimensions with numeric bands, an 8-step workflow, an enumerated output document structure, calendar columns, and two real templates in references. It is effectively copy-paste ready for the deliverable.

5 / 5

Workflow Clarity

The 8-step workflow is clearly sequenced with a confirm-inputs checkpoint ('If any are missing, surface that first') and a positioning stress-test, plus a dedicated unavailable-data section. It lacks an explicit review/validation step for the finished strategy, so it matches 'most checkpoints present; minor validation gaps' rather than the full-checkpoint anchor.

4 / 5

Progressive Disclosure

The body serves as a framework overview while the detailed deliverables (content-strategy-template.md, editorial-calendar-template.md) are properly split into references/, clearly signaled with descriptive links, and only one level deep; both referenced files exist and are substantive.

5 / 5

Total

18

/

20

Passed

Description

83%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 that clearly states what the skill does and when to use it, with rich natural trigger coverage and third-person voice. The only weakness is a slightly broad catch-all trigger that could occasionally fire for tactical content-writing requests better served by adjacent skills.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — 'Develop a content strategy covering editorial positioning, content pillars, formats, calendar, governance, and topical authority planning' plus six more verbs (plan, define, build, structure, set up, align) — with comprehensive coverage of the skill's scope, matching the comprehensive-coverage anchor rather than the minor-gaps anchor below.

5 / 5

Completeness

It explicitly answers both questions: what ('Develop a content strategy covering editorial positioning, content pillars, formats, calendar, governance, and topical authority planning') and when ('Use this skill whenever the user wants to...' plus the 'Triggers on...' list with concrete phrases).

5 / 5

Trigger Term Quality

Eleven natural trigger terms ('content strategy, content plan, editorial strategy, content pillars, content calendar, editorial calendar, topical authority, topic clusters, content governance, content roadmap, content production') with synonyms and variations well covered; these are phrases a user would naturally say when needing this skill.

5 / 5

Distinctiveness Conflict Risk

The niche is clear and core triggers are unambiguous, but the broad 'content production' trigger and the catch-all 'Also triggers when the user is about to start producing content without a strategic plan' create minor overlap risk with adjacent copywriting skills (content-and-copy, landing-page-copy).

4 / 5

Total

19

/

20

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

Validation for skill structure

No warnings or errors.

Repository

rampstackco/claude-skills

Path

dist/codex/.agents/skills/content-strategy/SKILL.md

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.