claude-blog

Free, open-source AI blog writer for Claude Code. Posts that are researched, sourced and reviewed before you read a word.

Install · Demo · Commands · Team · Pricing · How it works · FAQ

Claude Blog is a free blog writing skill for Claude Code. Give it a topic and it researches current sources, writes the post, checks the SEO, has an independent reviewer score it and runs five delivery gates. You only see the post once it passes.

What you get:

• A finished post. Markdown, rendered HTML and PDF, a hero image with its license, and screenshots at phone, tablet and desktop widths plus dark mode.
• A reviewer that can say no. The blog-reviewer agent scores every post out of 100 and blocks anything under 90 or with a P0 issue.
• Sources you can check. Statistics come from tier 1 to 3 sources with dates, and /blog factcheck fetches every cited page to confirm the claim is there.
• SEO for Google and AI answers. Answer-first structure, Schema.org markup and Google's latest guidance, so one post works for rankings and for citations in Google AI Overviews, ChatGPT, Perplexity and Gemini.
• Any language. /blog multilingual writes the post, translates and localizes it, and adds the hreflang tags.

Claude Blog is built from 32 skills and 5 specialist agents, with 30 /blog commands for everything around the post: strategy, topic clusters, audits, refreshes, images and audio.

See it in action

Type /blog in Claude Code to see every command:

Write a post from one line, through research, review and all five gates:

Watch the full walkthrough on YouTube or read how it works.

Install

You need Claude Code and Python 3.11 or newer. Run these two commands inside Claude Code, then restart it:

/plugin marketplace add AgriciDaniel/claude-blog
/plugin install claude-blog@agricidaniel-blog

The analyzer's two packages install with pip install -r requirements.txt. Rendering, screenshots and generated heroes use the optional presentation extra in pyproject.toml (Patchright, WeasyPrint, Markdown, Pillow, requests and google-genai); without a renderer, gate 3 blocks delivery instead of skipping it.

Standalone installer for Unix, macOS and Windows, with digests and uninstall

Recommended: clone, review, then install. <commit-sha-or-release-tag> is a release from v2.3.0 on or a commit you reviewed, ideally a full commit SHA.

git clone https://github.com/AgriciDaniel/claude-blog.git
cd claude-blog
git checkout <commit-sha-or-release-tag>
# Review install.sh, uninstall.sh and scripts/installer_ownership.py.
chmod +x install.sh
./install.sh

Download and run on Unix and macOS, with the digest check:

curl -fsSL -o install.sh https://raw.githubusercontent.com/AgriciDaniel/claude-blog/main/install.sh
echo "fea1faa0bbdea3f1b577bd84cc685a2f7c4f75da248b7a116b39969b2817f6e3  install.sh" | sha256sum -c
CLAUDE_BLOG_REF=<commit-sha-or-release-tag> bash install.sh

Windows PowerShell:

$env:CLAUDE_BLOG_REF = "<commit-sha-or-release-tag>"
irm https://raw.githubusercontent.com/AgriciDaniel/claude-blog/main/install.ps1 -OutFile install.ps1
pwsh -File ./install.ps1

Integrity is only as pinned as CLAUDE_BLOG_REF. Each digest is the SHA-256 of that one file with CRLF line endings normalized to LF, the form raw.githubusercontent.com serves (install.sh: the digest above; install.ps1: 55c40999f3d9c2261917f5160c8e880c23debc2941b1c13df4a6fc2379de180e). The digests do not cover the code that does the work: the wrapper clones the repository at CLAUDE_BLOG_REF and hands over to that revision's own installer. A branch such as main moves, a tag can be re-pointed by whoever controls the repository, and a full commit SHA cannot. Pin a commit SHA you reviewed.

Do not install or uninstall from the v2.2.0 tag: its uninstall.sh deletes whole blog and blog-* skill folders, including files you added. The safe installer starts at v2.3.0. It never uses sudo, backs up any file it replaces to ~/.claude/claude-blog-backups/<timestamp>/, and stops with recovery steps if it finds a managed file you edited.

Uninstall with ./uninstall.sh (Unix, macOS) or .\uninstall.ps1 (Windows). More in docs/INSTALLATION.md.

Your first post:

claude                                       # start Claude Code

/blog strategy "freelance CRM software"      # find the topics worth writing
/blog write "best CRM for freelancers"       # research, write, review, gates
/blog analyze posts/best-crm.md              # score any post you already have
/blog multilingual "best CRM for freelancers" --languages de,fr,es

The platform is detected for you (Next.js MDX, Astro, Hugo, Jekyll, WordPress, Ghost, 11ty, Gatsby or static HTML), and frontmatter, images and schema follow it.

Commands

30 commands in six groups. Open one to see what is inside; the full reference is in docs/COMMANDS.md.

Write and shape (7 commands)

• /blog write <topic>: A new post: researched, written, reviewed and gated
• /blog rewrite <file>: Improve an existing post with sourced statistics (alias /blog update)
• /blog outline <topic>: An outline shaped by what already ranks
• /blog brief <topic>: A content brief with competitive analysis
• /blog style learn <paths>: Learn your voice from 5 to 10 of your posts
• /blog persona [create | list | use | show]: Writing personas with tone settings
• /blog brand [init | show | update]: BRAND.md and VOICE.md that every skill reads

Plan and research (5 commands)

• /blog strategy <niche>: Positioning and the topics worth writing
• /blog calendar [monthly | quarterly] [niche]: An editorial calendar built on topic clusters
• /blog cluster [plan | execute] <seed or cluster-plan.json>: Plan and write a pillar with its supporting posts
• /blog discourse <topic>: What people ask on Reddit, YouTube and Hacker News, no API keys
• /blog notebooklm ask <question>: Source-grounded answers from your NotebookLM notebooks

Check quality (6 commands)

• /blog analyze <file or url>: The 100-point score in five categories
• /blog seo-check <file>: On-page SEO checklist after writing
• /blog factcheck <file>: Fetch every cited source and check the claim
• /blog audit [directory]: Health check for a whole blog
• /blog cannibalization [directory]: Posts competing for the same keyword
• /blog decay <current> <previous>: Posts losing clicks, from Search Console exports

Search and AI answers (4 commands)

• /blog geo <file>: How ready a post is to be cited by AI answers
• /blog schema <file>: JSON-LD structured data for the post
• /blog google [command]: PageSpeed, CrUX, Search Console, GA4, NLP, YouTube and Keyword Planner data
• /blog flow [find | optimize | win | prompts | sync]: FLOW framework prompts

More languages (4 commands)

• /blog multilingual <topic> --languages <codes>: Write, translate, localize and add hreflang in one go
• /blog translate <file> --to <language>: Translation that keeps formatting, schema and charts
• /blog localize <file> --locale <locale>: Cultural adaptation for one market
• /blog locale-audit <directory>: Quality checks across every language version

Media and distribution (4 commands)

• /blog image [generate | edit]: Hero and inline images with Gemini, after you approve the cost
• /blog audio [generate | voices | setup]: Narration with Gemini text to speech, after you approve the cost