Blog Outline

What it does

When your agent uses it

• User says outline
• Content outline
• Article skeleton
• Heading structure

Example prompts

• “outline”
• “blog outline”
• “content outline”
• “/blog-outline”

Workflow steps

5 steps, taken from the step headings in SKILL.md.

1. 1Topic & Intent
2. 2SERP Analysis
3. 3Generate Outline
4. 4Content Gaps
5. 5Save

What it can do on your machine

Read from SKILL.md and the folder at commit 2500d4c. It shows what the files ask for, not the result of running them.

• Tool permissions

  Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

  From allowed-tools in the SKILL.md frontmatter.

• Runs code

  No scripts in the folder and no shell commands in SKILL.md.

  From the folder's file list and the shell code blocks in SKILL.md.

• Network

  No URLs in SKILL.md.

  From URLs in SKILL.md, links to its own repository left out.

• Credentials

  Names no API keys, tokens, secrets or passwords.

  From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Blog Outline loads about 1.5k tokens when it runs. Until then it costs about 185 tokens; SKILL.md has 489 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it

~185

When it runs · the whole SKILL.md, loaded when a task matches

~1.5k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from AgriciDaniel/claude-blog at commit 2500d4c, republished under its MIT licence (© AgriciDaniel). 489 words, ~1,532 tokens.

name

blog-outline

description

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

user-invokable

true

argument-hint

<topic>

license

MIT

# Outline: [Topic]

## Title Suggestions
1. [Primary title - 40-60 chars, front-loaded keyword, power word]
2. [Alternative title - different angle]
3. [Alternative title - question format]

## Target Parameters
- **Primary keyword**: [keyword]
- **Search intent**: [Informational/Commercial/Transactional]
- **Optional planning estimate**: [X,XXX] words, adjusted to intent and never
  used as a score or gate
- **H2 sections**: [6-8]
- **Target reading level**: Flesch 60-70

---

## Outline

### H2: [Section Title - Question Format] (~300-400 words)
- **Answer-first opener**: [What stat or fact should open this section?]
- **Key points to cover**:
  - [Point 1]
  - [Point 2]
  - [Point 3]
- **H3: [Subsection]** (if appropriate)
  - [What this subsection covers]
- **Key statistic to find**: [What data point would strengthen this section?]
- **Chart suggestion**: [Bar/Line/Donut/None] - [What data to visualize]
- **Image placement**: [Yes/No] - [Description of recommended image]

### H2: [Section Title] (~300-400 words)
[... repeat for 6-8 sections ...]

### Optional FAQ Section (3-5 items)
1. [Question from People Also Ask] - [Brief answer direction]
2. [Question from People Also Ask] - [Brief answer direction]
3. [Question from People Also Ask] - [Brief answer direction]
4. [Question from SERP analysis] - [Brief answer direction]

### Conclusion (~100-150 words)
- Key takeaways to summarize
- Call to action direction

---

## Internal Linking Zones
- **Link TO from this post**: [Existing content that should be referenced]
- **Link FROM to this post**: [Existing content that should link here]

## Content Gaps to Exploit
1. [What competitors miss that this post should cover]
2. [Unique angle or original perspective to include]
3. [Format advantage - visuals, depth, or structure competitors lack]

© AgriciDaniel, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/blog-outline of AgriciDaniel/claude-blog.

Open the folder on GitHubat commit 2500d4c

Used in 1 other repository

We found 4 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in AgriciDaniel/claude-blog, which our catalogue first saw on October 7, 2026.

• Infrasity-Labs/dev-gtm-claude-skills.claude/skills/blog-outlinewriting-skills/blog-outline+1 more