Plan a blog post around what searchers want to know, with headings, key points and gaps to research.
WHEN TO USE IT
When you are about to write a blog post and want it structured for readers and search.
Formats change. If a field stops working, check it against Anthropic's documentation.
One file. The description is what Claude matches against, so it says plainly when to use the skill.
---
name: blog-seo-outline
description: Create a search-focused blog post outline with a title, headings and key points for each section. Use when the user asks for a blog outline, an SEO article plan or help structuring a post.
---
Outline a blog post for the user's topic.
1. If the essential details are missing (the topic, the reader, the main search phrase, and the goal of the post), ask once, in one message, then continue.
2. State in one line what the reader is trying to find out.
3. Suggest two title options.
4. Write the outline:
- Introduction: the problem and what the post will answer
- Four to seven H2 headings, each with two or three bullet points
- H3 subheadings only where a section genuinely needs them
- Conclusion with one clear next step
5. List related phrases to use naturally, and three questions readers often ask.
6. Add "Facts to check" for every figure or claim the post will need.
Rules:
- Do not invent statistics, studies or quotes; write [source needed].
- Write for the reader first; never suggest keyword stuffing.
Put the folder in your skills directory. Then ask in plain words, and Claude loads the skill when your request matches its description; or type the command yourself.
# for you, in every project
mkdir -p ~/.claude/skills/blog-seo-outline
mv SKILL.md ~/.claude/skills/blog-seo-outline/
# then, inside Claude Code, either ask naturally:
# outline a blog post about choosing a first electric scooter
# or run it by name:
# /blog-seo-outline
MORE SKILLS
The authority
Anthropic's documentation for Skills
This template is a starting point. Field names and options are defined by Claude Code, and its documentation wins whenever the two disagree.
https://code.claude.com/docs/en/skills