CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

69

Quality

85%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Discovery

100%

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, well-crafted skill description that clearly defines what the skill does with specific deliverables, provides explicit 'Use when' guidance, and includes comprehensive trigger terms that users would naturally use. It uses proper third-person voice and is distinctive enough to avoid conflicts with adjacent skills like general SEO or copywriting tools.

DimensionReasoningScore

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 for when users lack a strategic plan.

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

Occupies a clear niche around content strategy and editorial planning. The specific terminology (content pillars, topical authority, content governance, topic clusters) is distinct enough to avoid conflicts with general marketing, SEO-only, or writing skills.

3 / 3

Total

12

/

12

Passed

Implementation

70%

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 strategic skill with excellent workflow clarity and progressive disclosure. Its main weaknesses are verbosity—explaining concepts Claude already knows like content formats and editorial roles—and a lack of concrete, filled-out examples that would make the guidance more immediately actionable. Trimming explanatory content and adding one complete worked example would significantly improve it.

Suggestions

Add a concrete, filled-out example of at least one complete content pillar (theme, justification, sub-topics, cornerstone, supporting content) to improve actionability.

Trim the 'Content formats and types' section significantly—Claude knows what articles, case studies, and podcasts are. Focus only on the selection criteria and the '3 to 5 formats' guidance.

Remove or drastically shorten the 'Roles' subsection under Governance—Claude understands what editors and writers do. Keep only role-specific quality bar expectations or non-obvious responsibilities.

DimensionReasoningScore

Conciseness

The skill is well-structured but verbose in places. Sections like 'Content formats and types' and 'Governance and lifecycle' explain concepts Claude already understands (e.g., what article types are, what roles like 'editors' and 'writers' do). The format dimensions and role definitions could be significantly tightened. However, the framework layers and failure patterns add genuine value.

2 / 3

Actionability

The skill provides a clear framework and workflow steps, plus an example sentence structure for editorial positioning. However, it lacks concrete, copy-paste-ready artifacts—no filled-out example of a complete pillar definition, no sample calendar row, no example strategy document excerpt. The guidance is structured but remains largely descriptive rather than executable.

2 / 3

Workflow Clarity

The 8-step workflow is clearly sequenced with an explicit first step to confirm inputs before proceeding. The governance section defines a production pipeline with stages, and the failure patterns section serves as a validation checklist. The 'if any are missing, surface that first' instruction provides a feedback loop for the critical input-gathering step.

3 / 3

Progressive Disclosure

The skill clearly delineates its scope from related skills (content-and-copy, landing-page-copy, email-sequences, seo-keyword, seo-content-audit) and references two specific template files for detailed artifacts. The main document serves as a strategic overview with well-signaled one-level-deep references. Content is appropriately split between strategy (here) and templates (referenced files).

3 / 3

Total

10

/

12

Passed

Validation

90%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

10

/

11

Passed

Repository
rampstackco/claude-skills
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.