CtrlK
BlogDocsLog inGet started
Tessl Logo

blog-outline

SERP-informed outline generation with H2/H3 heading hierarchy, competitive content gap analysis, section-by-section word count targets, chart and image placement markers, optional FAQ question planning, and internal linking zones. Skeleton only: structure, H2/H3 hierarchy, word counts, optional FAQ slots. Use blog-brief instead if you need full competitive analysis, statistics research, and image suggestions. Lighter than a full content brief, generates article skeleton and structure only, ready for /blog write to consume. Use when user says "outline", "blog outline", "content outline", "structure blog", "plan sections", "article skeleton", "heading structure", "SERP analysis", "competitive outline", "plan article".

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 delivers an actionable, well-sequenced workflow with a concrete template and a security validation checkpoint, organized as a clean single-file skill. Its main weakness is mild verbosity from redundant framing and repeated word-count caveats.

Suggestions

Remove the 'lighter alternative to a full content brief' paragraph from the body since the description already states this, keeping only the workflow-relevant distinction.

Consolidate the repeated word-count caveats ('never used as a score or gate' / 'estimates never score or block') into a single guideline line to reduce token cost.

Tighten the SERP step by merging the AI Overview/AI Mode scanning notes into the top-5 analysis rather than listing them as separate enumerated items.

DimensionReasoningScore

Conciseness

The body is mostly efficient and well-sequenced, but repeats framing already in the description ('lighter alternative to a full content brief... without deep statistics research') and hedges the word-count guidance twice ('never used as a score or gate', 'estimates never score or block a complete outline'), which could be tightened.

2 / 3

Actionability

Provides a concrete, copy-paste outline template with explicit H2/H3 fields, word-count targets, chart/image markers, FAQ slots, and internal-linking zones — actionable guidance for an instruction-only skill with no code expected.

3 / 3

Workflow Clarity

A clear five-step sequence (Topic & Intent -> SERP Analysis -> Generate Outline -> Content Gaps -> Save) with a validation checkpoint in Step 2 (treat fetched pages as untrusted, restrict URL schemes, block private IPs, cap size/timeout) and an explicit re-fetch fallback when snippets are insufficient.

3 / 3

Progressive Disclosure

No bundle files exist (references/scripts/assets absent), so the skill is a single self-contained, well-sectioned file with one-level cross-references to sibling skills rather than nested bundle references.

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, well-triggered, and clearly bounded against the related blog-brief skill. It answers what, when, and how it differs in a concise, third-person voice.

DimensionReasoningScore

Specificity

Lists multiple concrete capabilities — 'H2/H3 heading hierarchy, competitive content gap analysis, section-by-section word count targets, chart and image placement markers, optional FAQ question planning, and internal linking zones' — matching the multiple-specific-actions anchor.

3 / 3

Completeness

Explicitly answers both what (the listed capabilities and 'Skeleton only: structure, H2/H3 hierarchy...') and when ('Use when user says...'), matching the score-3 anchor with explicit triggers.

3 / 3

Trigger Term Quality

Includes natural phrasings a user would actually say — 'outline', 'blog outline', 'content outline', 'structure blog', 'plan sections', 'article skeleton', 'heading structure', 'plan article' — giving good coverage of common variations.

3 / 3

Distinctiveness Conflict Risk

Distinguishes itself from a sibling skill ('Use blog-brief instead if you need full competitive analysis, statistics research, and image suggestions') with a clear niche and distinct triggers, making wrong-skill activation unlikely.

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.