CtrlK
BlogDocsLog inGet started
Tessl Logo

content-strategy

Use when the user wants to plan a content strategy, decide what content to create, figure out topics, or mentions content strategy, content planning, or editorial calendars.

62

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills/skills/content-strategy/SKILL.md

The canonical home for this skill is content-strategy in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

68%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 comprehensive, well-structured strategy skill with strong actionability via formulas, modifiers, and templates. The main gap is workflow clarity: the process is sequenced but lacks explicit validation checkpoints between stages.

Suggestions

Add explicit checkpoints between phases (e.g., 'Before moving to ideation, confirm pillars map to product and have search/social interest') to give the workflow clear validation gates.

Trim definitional restatements like 'Searchable content captures existing demand' to tighten conciseness without losing the searchable/shareable distinction.

DimensionReasoningScore

Conciseness

Mostly lean bullet lists, formulas, and templates rather than padded prose; minor instances of explanatory restatement (e.g., 'Searchable content captures existing demand...') could be trimmed.

4 / 5

Actionability

Concrete, copy-paste-ready guidance: persona+use-case formulas, buyer-stage keyword modifiers, a weighted scoring template with example rows, and a defined output format; minor gaps where framework-level direction could be more specific.

4 / 5

Workflow Clarity

A clear planning sequence is present (context gathering → searchable/shareable → pillars → ideation → prioritization → output) but there are no explicit validation checkpoints or feedback loops between stages.

3 / 5

Progressive Disclosure

Well-organized sections with a single clearly-signaled one-level-deep reference to references/headless-cms.md (a real bundle file); most content is appropriately inline for a strategy skill with only minor organization gaps.

4 / 5

Total

15

/

20

Passed

Description

78%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 that clearly states both capability and trigger conditions with natural user language. Specificity is the weakest dimension because the stated actions are somewhat high-level.

Suggestions

Sharpen the 'what' with more concrete verbs (e.g., 'map topics to buyer stages, prioritize content ideas, design pillar/cluster structures') rather than 'plan/decide/figure out'.

Move a couple of high-signal natural triggers ('content ideas', 'blog topics', 'what should I write about') from the body into the description for fuller keyword coverage.

DimensionReasoningScore

Specificity

Names the content-strategy domain and lists a few actions ('plan a content strategy, decide what content to create, figure out topics'), but the verbs are high-level and generic rather than concrete operations.

3 / 5

Completeness

Explicitly answers both what ('plan a content strategy, decide what content to create, figure out topics') and when ('Use when the user wants to... or mentions content strategy, content planning, or editorial calendars') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Good natural-term coverage ('content strategy', 'content planning', 'editorial calendars', 'decide what content to create', 'figure out topics'); a few common variations users say (e.g. 'content ideas', 'blog topics') appear only in the body, not the description.

4 / 5

Distinctiveness Conflict Risk

Clear content-strategy niche with distinct triggers and low conflict risk; minor overlap with adjacent skills like copywriting via phrases such as 'decide what content to create'.

4 / 5

Total

16

/

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
administrakt0r/AI-Agents-Safe-Coding-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.