CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

77%

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

61%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.

The body is a well-organized, concrete strategy playbook with actionable formulas, queries, and templates, and a properly linked single reference file. It loses points for inlining generic SEO knowledge Claude already has, leaving the end-to-end workflow implicit without validation checkpoints, and a reference file with dangling out-of-bundle links.

Suggestions

Trim or compress sections that restate standard SEO knowledge Claude already has (e.g., the "When Writing Searchable Content" bullet list) and replace soft directives like "Tell stories that make people feel something" with concrete criteria.

Add an explicit numbered workflow near the top (gather context → identify pillars → map keywords by buyer stage → generate and score ideas → produce the output format) so the section sequence reads as steps with checkpoints rather than reference material.

Fix the dangling links in references/headless-cms.md that point to ../../../tools/integrations/*.md files not present in this bundle, and consider moving the detailed keyword-modifier and ideation-source material into reference files to slim SKILL.md.

DimensionReasoningScore

Conciseness

The body is mostly efficient domain methodology (formulas, modifier lists, scoring weights, tables), but includes generic SEO knowledge Claude already has ("Place keywords in title, headings, first paragraph, URL", "Target a specific keyword... Match search intent exactly") plus soft filler like "Tell stories that make people feel something". Not a 2 because there is no tutorial-style padding of basic concepts, and not a 4 because the trimmable material is more than minor.

3 / 5

Actionability

Concrete, executable guidance throughout: the "[persona] + [use-case]" formula, exact search queries ("site:reddit.com [topic]"), buyer-stage keyword modifiers with worked example titles, a weighted scoring template with sample numbers, and an explicit output format. Not a 5 because of vague spots ("Interlink strategically", a Total column whose computation is never demonstrated) leaving minor gaps.

4 / 5

Workflow Clarity

A rough sequence exists ("Before Planning" context gathering → ideation sources → "Prioritizing Content Ideas" → "Output Format"), but the overall process order is implicit — the middle sections read as reference material rather than steps — and there are no checkpoints validating plan quality. Not a 2 because the sequence and expected deliverable are clearly present; not a 4 because sequencing and checkpoints are not explicit.

3 / 5

Progressive Disclosure

Good structure with a single clearly signaled, one-level-deep reference ([Headless CMS Guide](references/headless-cms.md)) that exists in the bundle. Not a 5 because substantial detail (keyword research by buyer stage, six ideation sources) is inlined in SKILL.md rather than split out, and the reference file itself contains dangling links to ../../../tools/integrations/*.md paths that are not in this bundle.

4 / 5

Total

14

/

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 with an explicit "Use when..." trigger clause, concrete stated actions, and natural trigger terms. Its main weakness is that it omits several natural trigger variations and specific capabilities (pillars, keyword research, prioritization) that the skill body clearly covers.

DimensionReasoningScore

Specificity

The description lists several concrete actions ("plan a content strategy, decide what content to create, or figure out topics") beyond just naming the domain. It is not a 5 because coverage has gaps — core capabilities like keyword research, content pillars, and prioritization are unmentioned.

4 / 5

Completeness

It explicitly answers both what ("plan a content strategy, decide what content to create, or 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

"content strategy, content planning, or editorial calendars" are natural phrases users would say, giving good keyword coverage. It falls short of 5 because common variations the skill body itself lists ("content ideas", "blog topics", "what should I write about") are missing from the description.

4 / 5

Distinctiveness Conflict Risk

The planning/strategy framing ("plan a content strategy", "content planning") carves out a mostly distinct niche from writing-execution skills. Not a 5 because "decide what content to create" and "figure out topics" carry minor overlap risk with ideation- and copywriting-adjacent skills.

4 / 5

Total

17

/

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

administrakt0r/AI-Agents-Safe-Coding-Skills

Path

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