CtrlK
BlogDocsLog inGet started
Tessl Logo

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," or "content planning." For writing individual pieces, see copywriting. For SEO-specific audits, see seo-audit.

71

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

The risk profile of this skill

SKILL.md
Quality
Evals
Security

Quality

Content

78%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, mostly efficient body that balances a concrete bundled tool and decision rule with qualitative planning guidance. Progressive disclosure is exemplary with real one-level-deep references; the main gap is the absence of an explicit validation/feedback loop in the workflow.

Suggestions

Add an explicit validate-then-proceed checkpoint after topic clustering (e.g., confirm buyer-stage coherence before locking cluster boundaries) to close the feedback-loop gap in workflow clarity.

Tighten the opening framing prose ("Your goal is to help plan content that drives traffic, builds authority, and generates leads...") into directive form to push conciseness toward a 5.

For the most common task (priority topic ideation), give one fully copy-paste-ready example row of the prioritized topic table so actionability matches the bundled-tool command's concreteness.

DimensionReasoningScore

Conciseness

Mostly efficient with bullet lists, a decision rule, and tables, with only minor framing prose (e.g., the opening goal sentence) that could be trimmed.

4 / 5

Actionability

Provides a concrete executable bundled-tool invocation and a concrete if/then decision rule, but much of the planning guidance is qualitative rather than copy-paste-ready across common cases.

4 / 5

Workflow Clarity

Clear sequenced flow (context gathering → classification → clustering → output) with a verification checkpoint on cluster boundaries, but no explicit validate-fix-retry feedback loop.

4 / 5

Progressive Disclosure

Well-organized overview with one-level-deep, clearly signaled references (references/content-strategy-reference.md and scripts/topic_cluster_mapper.py, both present) and bulk detail correctly kept out of the body.

5 / 5

Total

17

/

20

Passed

Description

95%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, well-structured description with explicit what/when guidance, comprehensive natural trigger terms, and clear differentiation from adjacent skills. The only slight gap is that the named actions are planning-oriented rather than a comprehensive list of concrete operations.

DimensionReasoningScore

Specificity

Names the domain and several concrete planning actions ("plan a content strategy, decide what content to create, or figure out what topics to cover"), with minor gaps versus a fully comprehensive action list.

4 / 5

Completeness

Explicitly answers both what (planning strategy, deciding content, finding topics) and when, with a clear "Also use when the user mentions..." clause and concrete trigger phrases.

5 / 5

Trigger Term Quality

Comprehensive natural-language triggers users would actually say ("content strategy," "what should I write about," "content ideas," "blog strategy," "topic clusters," "content planning"), including synonyms and variations.

5 / 5

Distinctiveness Conflict Risk

Clear niche with explicit boundaries to siblings ("For writing individual pieces, see copywriting. For SEO-specific audits, see seo-audit."), minimizing wrong-skill triggering.

5 / 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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
alirezarezvani/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.