How to use the Blog Draft Writer agent skill (blog-draft)

What the blog-draft skill makes the agent do

The skill's description says it writes blog drafts from your ideas and source material. It is meant for situations where you want to write a blog, create content based on research, or draft an article. The process covers research, brainstorming, outlining and iterative drafting with version control.

The agent works through the steps in order and pauses at the points where it needs your input. It creates a project folder named with the date and a short topic slug, collects and summarises your sources in a resources folder, and proposes an outline. After you approve the outline, it writes the draft, adds inline citations and a references list, and saves each revision as a new numbered file.

• Creates a dated project folder, for example a name in the format YYYY-MM-DD plus a short topic name, inside blog-posts/
• Saves one summary file per source in resources/ with key points, quotes or data, and relevance to the topic
• Asks clarifying questions about the takeaway, emphasis, target length and anything to exclude
• Writes OUTLINE.md only after you approve the outline
• Saves drafts as draft-v0.1.md, draft-v0.2.md and so on, so you can see how the post changed

Install the blog-draft skill

Download the ZIP for this skill from this page. You can install it in one of two ways, depending on how you use your agent.

For Claude Code, unzip the download into your personal skills folder ~/.claude/skills/ to make it available in all your projects. To limit it to one project, unzip it into that project's .claude/skills/ folder instead.

If you use the Claude apps, upload the ZIP under Settings, then Capabilities, then Skills.

• Personal use across projects: unzip into ~/.claude/skills/
• One project only: unzip into the project's .claude/skills/ folder
• Claude apps: Settings → Capabilities → Skills, then upload the ZIP

Ask for a blog post in a way that triggers the skill

You do not need a special command. The skill is meant to activate when you ask for help writing a blog post, creating content from research, or drafting an article. Say what you want to write about and, if you have them, include the sources.

The skill lists four inputs you can give: the idea or topic (the one thing that matters most), resources such as URLs, files or reference material (optional but recommended), the target reader (optional), and the tone, such as formal, casual or technical (optional). Giving more detail up front means fewer clarifying questions later.

• "I want to write a blog post about remote onboarding. Use these three links as sources."
• "Draft an article for junior developers on choosing a database. Research it first and show me an outline before writing."
• "Help me write a casual blog post for small shop owners about email marketing, based on the attached PDF."

Work through the approval steps

The skill is built around checkpoints. The agent is told not to skip steps or continue past a point that needs your confirmation. In practice you review the research summary, answer the questions, approve or edit the outline, and then review the draft.

When you ask for changes, the agent returns to drafting, increments the version, incorporates your feedback and saves a new file. When you approve, it can rename the final version to final.md if you ask, and it summarises how many versions were made, the main changes between them, the final word count and the files created.

• Review the research summaries before the brainstorm
• Answer the clarifying questions about the main takeaway, length and exclusions
• Approve or edit the outline; OUTLINE.md is saved only after approval
• Give feedback on each draft; each revision is kept as its own file
• Ask for final.md when you are satisfied

Understand the output folder and version history

Every post gets its own folder. Earlier drafts are kept, so you can go back to an earlier version if a revision made the post worse. The folder structure the skill produces looks like this.

Check the citations before you publish

The skill asks the agent to cite every statistic, comparison and factual claim with an inline reference, and to list the references at the end of the draft. Citations make the draft easier to check, but they do not prove it is correct. The skill's own guidance warns that the agent can still misquote or invent references.

Open each cited source and confirm the figure, quote and claim match. Remove any reference you cannot find.

• Confirm every number and quote against the original source
• Make sure each reference link or citation points to a real source
• Delete claims you cannot verify rather than keeping them for flow

Use Git (optional) to save outlines and drafts

The skill checks whether the current directory is a Git repository. If it is, the agent stages the post folder, the resources and OUTLINE.md, commits with a message like docs: Add outline for blog post, and pushes to the remote. It does the same after each draft. If the directory is not a Git repository, the agent skips this and tells you.

You only need Git and a remote repository if you want this automatic committing and pushing. The skill does not require it.