Guide · Agent skill
How to use the Blog Post Drafter agent skill (blog-draft)
Updated · written with AI from the project's own documentation and checked against our catalogue data
The blog-draft skill is a set of instructions that tells an AI agent to write a blog post in stages rather than producing one block of text. It is useful for bloggers, content writers, students and researchers who want research, outline and drafting handled in one structured workflow. After this guide you will know how to install the skill, trigger it with a plain request, and work through its approval checkpoints.
Blog Post Drafterluongnv89/claude-howto · MIT Download the skill Quick start
- 1Install the skill. Download the blog-draft ZIP and unzip it into ~/.claude/skills/ or a project's .claude/skills/ folder, or upload it under Settings → Capabilities → Skills in the Claude apps.
- 2Ask for a blog post. Describe your topic in plain language and attach any URLs, files or research you want used.
- 3Confirm the project folder. The agent creates a dated blog-posts folder with a resources/ subfolder and asks you to confirm before continuing.
- 4Answer the clarifying questions. Reply with your main takeaway, target length, points to emphasise and points to exclude.
- 5Approve the outline. Review the proposed structure and sources, request changes, then approve so it is saved as OUTLINE.md.
- 6Review the draft and iterate. Read draft-v0.1.md, give feedback, and the agent saves each revision as the next numbered draft.
What the blog-draft skill makes the agent do
Once installed, the agent walks you through writing a blog post step by step. It creates a dated project folder, gathers and summarises your sources (URLs, files, or web searches) into notes, asks clarifying questions, and proposes an outline for your approval before it writes anything.
Its draft cites factual claims inline and ends with a references list. Each revision is saved as a new numbered draft, so you can compare versions or go back to an earlier one.
- Creates a folder named YYYY-MM-DD-short-topic-name with a resources/ subfolder
- Writes one summary file per source in resources/
- Saves the approved outline as OUTLINE.md
- Saves drafts as draft-v0.1.md, draft-v0.2.md and so on
- Commits outline and draft to git only if the folder is a git repository
Install the blog-draft skill
Download the ZIP for blog-draft from this page. You can install it in one of two ways.
For Claude Code, unzip the download into ~/.claude/skills/ to make it available everywhere, or into a project's .claude/skills/ folder to make it available only in that project. For the Claude apps, upload the skill under Settings → Capabilities → Skills.
- Personal install: unzip into ~/.claude/skills/
- Project install: unzip into the project's .claude/skills/ folder
- Claude apps: Settings → Capabilities → Skills, then upload
Trigger the skill with a natural request
You do not need a special command. The skill's description tells the agent to use it when you want to write a blog post, create content from research, or draft articles. Ask in ordinary language and include whatever you have.
The source says the user should provide an idea or topic. Resources (URLs, files or references), target audience and tone are optional, but resources are recommended. The skill also accepts the length you want, which it asks about during brainstorming.
- Give the topic in one sentence
- Add any URLs or file paths you want researched
- State the audience and tone if you know them
Work through the checkpoints
The skill is deliberately sequential. It stops and waits for your input at several points: after creating the folder, after the brainstorm questions, after the outline is proposed, and after each draft is presented. Reply at each checkpoint before the agent moves on.
When you ask for changes to an existing post, the skill skips the setup steps and starts at the iteration step. It reads the existing draft file first and then creates the next version.
- Confirm the folder creation
- Answer the clarifying questions (takeaway, length, points to exclude)
- Approve or modify the outline
- Give feedback on each draft version
Check citations and versions
The skill requires inline citations for statistics, comparisons and factual claims, with a References section at the end. The agent may still misquote or mis-cite sources, so check every claim against the original before you publish.
Because every draft is kept, you can compare v0.1 with later versions or revert to an earlier one.
- Verify each statistic against its source
- Confirm each URL in the References section opens and matches the claim
- Keep older draft files if you may want to revert
What people use it for
- Turning a set of URLs and PDFs into a researched blog post with a references list
- Drafting a student or research article from a folder of source files
- Keeping a team's blog outlines and drafts committed to a git repository as they are approved
- Revising an existing post by asking for changes, which saves a new numbered version
Frequently asked questions
Is the blog-draft skill free?
The source material for this page does not state pricing. The skill is listed under the MIT licence, which is shown on this page. Check the repository licence file for the full terms.
What do I need to run blog-draft?
You need web access or a web search tool so the agent can fetch URLs and research topics. Git is only needed if you want the outline and draft commits and pushes to happen automatically. The skill does not run scripts.
Where do I put the skill files?
Unzip the download into ~/.claude/skills/ for a personal install, or into a project's .claude/skills/ folder for a project-only install. In the Claude apps, upload it under Settings → Capabilities → Skills.
Does the skill run scripts or access the network?
According to this listing, it runs no scripts and does use the network, because it fetches URLs and performs web searches for research.
Will the citations be accurate?
The skill asks for citations on every factual claim, but the agent may still misquote or mis-cite sources. Check every claim against the original before publication.
Is this better than just asking an AI for a blog post?
It is slower for quick posts because it waits for your approval at each step. It suits longer pieces where you want research, an approved outline and tracked drafts. For a quick one-off post, asking for a direct draft is usually faster.
New agent skills, repos and AI tools — every week
The best new skills and open-source projects, the fastest-growing repos, and one free prompt. Five minutes to read. Unsubscribe anytime.
Our verdict
Use blog-draft if you want a structured, reviewable process for research-based articles, especially with citations and version history. Skip it for quick one-off posts, since the sequential approvals and folder setup will feel slow, and for any publication that needs independently verified facts beyond what the agent checks.
Download the skill