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".

69

Quality

85%

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

71%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 highly actionable, well-sequenced strategy skill with concrete templates and metrics, weakened mainly by redundant distribution/AI-citation tables repeated across steps and by references to bundle files that are not actually present.

Suggestions

Consolidate the near-duplicate distribution channel tables in Steps 5.5, 5.7, and 6 into a single canonical table referenced once, to remove repeated YouTube/Reddit/review-platform/Wikipedia rows.

Either ship the referenced files under references/ (internal-linking.md, distribution-playbook.md, geo-optimization.md, content-templates.md, research-quality.md, synthesis-contract.md, flow-alignment.md) or remove the dangling references, so progressive-disclosure pointers resolve to real bundle files.

Drop the opening restatement of the description and let the body begin directly with the workflow, trimming the token budget without losing clarity.

DimensionReasoningScore

Conciseness

Most content is task-specific tables and templates rather than concept-padding, but the distribution channel table (YouTube, Reddit, review platforms, Wikipedia/Wikidata, industry publications) is nearly duplicated across Step 5.5, Step 5.7, and Step 6, and the opening paragraph restates the description.

3 / 5

Actionability

Provides concrete, executable artifacts: ASCII cluster diagrams, specific metrics (80+ quality score, 8-12 spokes, 3000-4000w pillars, 1500-2500w spokes), 12 named content templates, named commands (/blog analyze, /blog calendar, /blog brief, /blog write), and copy-ready output tables.

5 / 5

Workflow Clarity

Eight clearly sequenced steps culminate in a concrete strategy-document template and a 90-day roadmap; this is a generative strategy skill so the destructive/batch validation cap does not apply, though explicit user-checkpoint feedback loops are absent.

4 / 5

Progressive Disclosure

References to skills/blog/references/*.md files are clearly signaled and one level deep, but those files are absent from the (empty) bundle, and substantial content (full output template, multiple tables) that could live in separate files is inlined in SKILL.md.

3 / 5

Total

15

/

20

Passed

Description

100%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, third-person description that comprehensively states concrete capabilities and pairs them with an explicit, natural-language trigger clause. It cleanly satisfies the what/when requirements with minimal conflict risk.

DimensionReasoningScore

Specificity

Lists multiple concrete actions (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, content scoring targets, measurement framework, content differentiation via original research) with comprehensive coverage.

5 / 5

Completeness

Explicitly answers both 'what' (the enumerated strategy development capabilities) and 'when' (the concrete 'Use when user says...' trigger phrases), matching the score-5 anchor.

5 / 5

Trigger Term Quality

The 'Use when user says' clause enumerates natural phrases users would actually say — 'blog strategy', 'content strategy', 'blog positioning', 'what should I blog about', 'blog topics', 'content pillars', 'blog ideation' — covering synonyms and common variations.

5 / 5

Distinctiveness Conflict Risk

Occupies a clear blog-strategy niche with distinct, specific triggers (blog positioning, content pillars, blog ideation) that are unlikely to fire for unrelated skills, giving minimal conflict risk.

5 / 5

Total

20

/

20

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.