CtrlK
BlogDocsLog inGet started
Tessl Logo

blog-strategy

Blog strategy development including topic cluster architecture with hub-and-spoke design, audience mapping, competitive landscape analysis, AI citation surface strategy across ChatGPT/Perplexity/AI Overviews, distribution channel planning (YouTube, Reddit, review platforms for AI-citation SEO), content scoring targets, measurement framework, and content differentiation through original research and first-hand experience. Use when user says "blog strategy", "content strategy", "blog positioning", "what should I blog about", "blog topics", "content pillars", "blog ideation".

74

Quality

92%

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

SKILL.md
Quality
Evals
Security

Quality

Content

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is highly actionable with concrete templates, a well-sequenced 8-step workflow including validation gates, and good progressive disclosure via clearly signaled reference files. Its main weakness is conciseness, owing to repeated channel tables and some hedging prose.

Suggestions

Consolidate the duplicate YouTube/Reddit/review-platform/distribution tables that recur in Step 5.5 (Off-Site Presence) and Step 6 (Distribution Channel Strategy) into a single canonical table referenced once.

Tighten hedging prose such as 'Treat vendor-reported off-site citation percentages and channel multipliers as non-causal observations, not strategy targets' into a short directive (e.g. 'Treat vendor citation percentages as observations, not targets').

Consider moving the ASCII cluster diagram and full cluster-build-plan template into internal-linking.md, keeping SKILL.md as a lean overview that links out.

DimensionReasoningScore

Conciseness

Mostly efficient and avoids explaining concepts Claude already knows, but the near-identical YouTube/Reddit/review-platform channel tables recur across Steps 5.5 and 6, and hedging prose like 'Treat vendor-reported off-site citation percentages and channel multipliers as non-causal observations' could be tightened. It is not level 3 because of this redundancy and padding.

2 / 3

Actionability

Provides concrete, copy-paste-ready templates (cluster build plan table, audience-segment block, output strategy document), specific commands ('/blog analyze', target '80+'), and exact word-count and template guidance — matching the fully-actionable anchor for an instruction skill.

3 / 3

Workflow Clarity

Eight numbered steps with clear sub-sequencing, validation gates ('Posts below 80 quality score should be revised before going live', 'validate source URLs before citing', 'validate it against official Google sources'), and a checklist-style 90-day roadmap — matching the clear-sequence-with-checkpoints anchor.

3 / 3

Progressive Disclosure

SKILL.md acts as the overview with well-signaled one-level-deep references (research-quality.md, internal-linking.md, distribution-playbook.md, geo-optimization.md, content-templates.md) and a consolidated 'Reference Documents' list, matching the clear-overview-with-one-level-references anchor.

3 / 3

Total

11

/

12

Passed

Description

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.

The description is specific, complete, and uses natural trigger terms with an explicit 'Use when' clause in third-person voice. It clearly conveys both what the skill does and when to invoke it.

DimensionReasoningScore

Specificity

Lists multiple concrete capabilities — 'topic cluster architecture with hub-and-spoke design', 'audience mapping', 'competitive landscape analysis', 'AI citation surface strategy across ChatGPT/Perplexity/AI Overviews', 'content scoring targets' — matching the multiple-specific-actions anchor.

3 / 3

Completeness

Explicitly answers both what (the capability list) and when (the 'Use when user says...' trigger clause), matching the highest anchor; it is not capped at 2 because explicit trigger guidance is present.

3 / 3

Trigger Term Quality

The 'Use when user says "blog strategy", "content strategy", "blog positioning", "what should I blog about", "blog topics", "content pillars", "blog ideation"' clause gives strong coverage of natural phrases users would actually say.

3 / 3

Distinctiveness Conflict Risk

The blog-strategy niche with distinct blog-specific triggers is clearly distinguishable from adjacent skills; not level 2 because the triggers (e.g. 'blog topics', 'content pillars') are niche-specific rather than broadly overlapping.

3 / 3

Total

12

/

12

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository
AgriciDaniel/claude-blog
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.