Name: content-strategy
Rating: 64 (1 reviews)
Author: administrakt0r

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.

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

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

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

Quality

Content

67%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-organized, actionable instruction-only skill with clear sequencing and a verified external reference at one level of depth. The main weakness is mild verbosity from conceptual framing Claude already knows, which trims token efficiency below the top anchor.

Suggestions

Trim the conceptual explanations of 'searchable vs shareable' and the demand-creation framing to one line each, since Claude already knows these concepts; keep only the actionable 'When Writing...' bullet lists.

Add an explicit validation checkpoint in the workflow before the Output Format step (e.g. 'Confirm each priority topic maps to a buyer stage and has a target keyword') so the prioritization step has a feedback loop.

Consider pulling the detailed scoring template and buyer-stage modifier tables into a references file to further reduce inline weight while keeping the SKILL.md a concise overview.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and actionable, but includes conceptual framing Claude already knows (e.g. 'Searchable content captures existing demand. Optimized for people actively looking for answers.' and 'Shareable content creates demand.'), matching the 'mostly efficient but some unnecessary explanation' anchor; it is not lean enough for a 4.	3 / 5
Actionability	As an instruction-only skill it provides concrete, executable guidance — keyword-modifier lists per buyer stage, a weighted prioritization formula (40/30/20/10) with a scoring template, content-type formulas, and a defined output format — with only minor gaps, fitting 'mostly executable guidance; minor gaps' below the fully copy-paste 5 anchor.	4 / 5
Workflow Clarity	The process is clearly sequenced (gather context → searchable/shareable framing → content types → pillars → ideation → prioritize → output) with mostly explicit checkpoints and an output checklist, but validation/feedback checkpoints are implicit rather than spelled out, matching 'clear sequence with most checkpoints present; minor validation gaps'.	4 / 5
Progressive Disclosure	Structure is good: the SKILL.md is an overview with one real one-level-deep reference (references/headless-cms.md, verified to exist) clearly signaled in the References section, and most content is appropriately sectioned inline, fitting 'good structure; references mostly clear; minor organization gaps' just below the ideal 5 anchor.	4 / 5
	Total	15 / 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, well-formed description that clearly states capability and explicit trigger conditions with natural language users would say. Minor gaps in trigger-term coverage and a small overlap risk with adjacent marketing skills keep specificity and distinctiveness just below the top anchor.

Suggestions

Expand the trigger-term list in the description to include high-frequency variations users say, such as 'blog strategy', 'topic clusters', 'content ideas', and 'content roadmap'.

Sharpen the capability verbs to be more concrete (e.g., 'identify content pillars, map topics to buyer stages, prioritize ideas by customer impact') to lift specificity toward the top anchor.

Dimension	Reasoning	Score
Specificity	The description names the content-strategy domain and lists several concrete actions ('plan a content strategy, decide what content to create, figure out topics'), matching the 'several specific actions; minor gaps' anchor rather than the fully comprehensive 5 anchor.	4 / 5
Completeness	It 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...') with concrete trigger phrases, matching the top anchor.	5 / 5
Trigger Term Quality	It includes natural user phrases ('content strategy, content planning, editorial calendars') that users would actually say, but omits some variations present in the body (e.g. 'blog strategy', 'topic clusters', 'content ideas'), so it is below the comprehensive 5 anchor.	4 / 5
Distinctiveness Conflict Risk	'Content strategy' is a clear niche with mostly distinct triggers, but there is minor overlap risk with closely related marketing skills such as copywriting and seo-audit, placing it at 'mostly distinct' rather than the 5 anchor.	4 / 5
	Total	17 / 20 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills-claude/skills/content-strategy/SKILL.md
Commit: 57c135b

Reviewed: 3 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.