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

73

Quality

91%

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

82%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-sequenced, highly actionable instruction skill with a complete output template and sensible safety guardrails for SERP fetching. It is slightly held back by an inlined large template (no progressive disclosure into reference files) and minor redundancy between Step 4 and the template.

Suggestions

Move the full outline template block into a references/outline-template.md file and link to it from Step 3, keeping only the field-by-field notes inline, to improve progressive disclosure.

Remove or consolidate the duplication between Step 4 ('Content Gaps') and the 'Content Gaps to Exploit' section already defined inside the outline template.

Add an explicit validation checkpoint in Step 5 that checks the generated outline against the required Target Parameters and 6-8 H2 section count before declaring it ready for /blog write.

DimensionReasoningScore

Conciseness

The body is largely lean with no padding about concepts Claude already knows, but Step 4 ('Content Gaps') duplicates the 'Content Gaps to Exploit' section already embedded in the outline template, a minor redundancy that could be trimmed.

4 / 5

Actionability

Provides a fully specified, copy-paste-ready output template with concrete placeholders and precise guidelines (60-70% question-format H2s, Flesch 60-70, 6-8 sections, 40-60 char titles), plus explicit WebSearch/WebFetch usage — concrete actionable guidance covering the common cases.

5 / 5

Workflow Clarity

Five clearly sequenced steps with a strong validation checkpoint in Step 2 (treating fetched pages as untrusted, URL/IP/size guardrails), but the final save step only weakly verifies output readiness ('Confirm the outline is ready') rather than validating against the template.

4 / 5

Progressive Disclosure

Good section structure with clear headers and a signaled cross-reference to sibling skills; however the ~55-line outline template is inlined in SKILL.md with no reference files, a minor organization gap that could justify splitting the template out.

4 / 5

Total

17

/

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.

The description is exemplary: it states concrete capabilities, gives an explicit 'Use when' clause with comprehensive natural trigger phrases, and draws a clear boundary against the sibling blog-brief skill. Voice is appropriately third-person throughout.

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' — with comprehensive coverage of the skill's actions.

5 / 5

Completeness

Explicitly answers both 'what' (SERP-informed outline generation with the listed capabilities) and 'when' via an explicit 'Use when user says...' clause with concrete trigger phrases.

5 / 5

Trigger Term Quality

Comprehensive natural trigger list including synonyms and variants: 'outline', 'blog outline', 'content outline', 'structure blog', 'plan sections', 'article skeleton', 'heading structure', 'SERP analysis', 'competitive outline', 'plan article' — phrases users would naturally say.

5 / 5

Distinctiveness Conflict Risk

Clear niche (blog outline skeleton) with distinct triggers and an explicit boundary statement ('Use blog-brief instead if you need full competitive analysis...') that minimizes conflict with the related blog-brief skill.

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.