AI Blog Writing & SEO Optimization Skill for Claude Code (claude-blog)

Two versions of this skill. Choose the one that fits how you work:

• 🌐 Public open-source: AgriciDaniel/claude-blog. MIT-licensed, public releases, open to anyone. Use this if you want the stable, downloadable, no-membership-required version.
• 🔒 Community private mirror (this repo): AI-Marketing-Hub/claude-blog. Early access to in-development work (v1.9.0+ Blog Delivery Contract, hero ladder, mutation-tested regression coverage), and direct collaboration with the AI Marketing Hub Pro community. Requires membership.

The badges above track the public repo (AgriciDaniel/claude-blog) since the private mirror is not visible to shields.io. The publishing workflow (private dev, review, public release) is documented in docs/PUBLISHING.md.

Blog: See how claude-blog works

claude-blog is a Claude Code skill suite that writes, optimizes, and audits blog content at scale. Every article is dual-optimized for Google rankings (December 2025 Core Update, E-E-A-T) and AI citation platforms (ChatGPT, Perplexity, AI Overviews). A v1.9.0 5-gate Delivery Contract scores every draft against a 100-point rubric and blocks anything below 90 from reaching you.

Key takeaways

• What it is: a full-lifecycle blog engine: 30 sub-skills, 5 agents, 12 content templates, 21 on-demand references, 9 root-level Python scripts, 160 passing tests.
• Who it is for: solo bloggers, marketing teams, agencies, and Claude Code skill builders who want production-grade content output, not one-shot drafts.
• Core promise: every draft passes a 5-gate delivery contract (Capability, Format, Visual, Content Review, Asset Integrity) or the writer iterates up to 3 times before escalating to you.
• What makes it different: it eats its own dogfood. Version-coherence is CI-enforced across 14 surfaces, prose-hygiene runs on every PR, three mutation-tested regression suites lock the v1.9.0 fixes, and blog-reviewer is a BLOCKING gate, not advisory.
• Today: v1.9.0, released 2026-05-18. Works on Next.js MDX, Astro, Hugo, Jekyll, WordPress, Ghost, 11ty, Gatsby, and static HTML.

Who is claude-blog for?

claude-blog serves three audiences with one engine:

Solo bloggers and creators who want to ship one high-quality post per week without spending three hours on the SEO checklist. The orchestrator handles research, outline, draft, schema, internal linking, and citation verification in a single /blog write invocation.

Marketing teams and agencies managing many posts across topics, languages, and platforms. The skill ships topic-cluster planning (/blog cluster), multilingual one-command publishing (/blog multilingual), cannibalization detection (/blog cannibalization), and persona-driven voice profiles (/blog persona) so the same engine produces consistent content across the team.

Claude Code skill builders who want a production-grade reference for skill architecture, agent dispatch, delivery contracts, and CI gating. The repo demonstrates the Agent Skills open standard at Tier 4 complexity with 160 tests, version-coherence enforcement, installer-sync regression tests, and the v1.9.0 5-gate contract pattern. Read the source for inspiration; fork the patterns into your own skills.

What does claude-blog produce?

Every draft ships as 8 artifacts in a single folder. A condensed specimen of the .md output:

---
title: "Where Should a Claude Code Skill Plugin Install Itself?"
description: "A working answer to the install-path question..."
date: "2026-05-18"
author: "Daniel Agrici"
tags: [claude-code, skills, plugins, installation]
canonical: "https://example.com/blog/skill-plugin-install-path"
---

# Where Should a Claude Code Skill Plugin Install Itself?

The short answer: most user-installable Claude Code skill plugins
should ship to `~/.claude/skills/<name>/` for skill content,
`~/.claude/agents/<name>.md` for agents, and
`~/.claude/scripts/<helper>.py` for any Python helpers.

## Key Takeaways
- `~/.claude/skills/` is the SKILL.md surface area.
- `~/.claude/agents/` holds agent markdown files.
- ... (full article, sourced citations, FAQ, schema JSON-LD)

Alongside the .md, the contract also produces: rendered .html (XSS-safe JSON-LD, dark-mode-aware CSS), .pdf (Playwright or weasyprint), hero.<ext> (1200x630, generated via Banana MCP, Gemini, stock APIs, or Openverse), 3 viewport screenshots (mobile-375.png, tablet-768.png, desktop-1280.png), review.md (5-category scorecard with BLOCKING line), and preflight-report.json (the full audit trail).

Table of Contents

• Demo
• Quick Start
• Commands
• How does claude-blog compare?
• Features
• Delivery contract (v1.9.0)
• Architecture
• Requirements
• Frequently Asked Questions
• Roadmap
• Uninstall
• Integration
• Documentation
• How to cite
• Security & Code of Conduct
• Contributing
• License
• Related projects
• Author

Demo

Watch the Demo on YouTube

Quick Start

ℹ️ Which version are you installing?

• Not an AI Marketing Hub Pro member? Install from the public repo: AgriciDaniel/claude-blog. All the install commands below work there. Just swap AI-Marketing-Hub/claude-blog for AgriciDaniel/claude-blog and the plugin slug claude-blog@ai-marketing-hub-claude-blog for claude-blog@agricidaniel-claude-blog. Public releases ship there; this private mirror runs ahead.
• Pro member? The commands below install the community version with early access to in-development features. They require an authenticated gh auth login (or GitHub PAT) session with access to the AI-Marketing-Hub org. If /plugin marketplace add fails with a 404, your account is not in the org yet. DM in the Skool community to get added.

Plugin Install (Claude Code 1.0.33+):

# Add marketplace (one-time)
/plugin marketplace add AI-Marketing-Hub/claude-blog

# Install plugin
/plugin install claude-blog@ai-marketing-hub-claude-blog

Recommended: clone, verify, then install (lets you inspect install.sh and pin a release tag):

git clone https://github.com/AI-Marketing-Hub/claude-blog.git
cd claude-blog
git checkout v1.9.0          # pin to a release tag (latest as of 2026-05-18)
chmod +x install.sh && ./install.sh

One-Command Install (Unix/macOS):

curl -fsSL https://raw.githubusercontent.com/AI-Marketing-Hub/claude-blog/main/install.sh | bash

One-Command Install (Windows PowerShell):

irm https://raw.githubusercontent.com/AI-Marketing-Hub/claude-blog/main/install.ps1 | iex

Piping curl or irm to a shell gives the script execution authority on your machine. The clone-then-checkout-tag flow is safer because you can inspect what runs. Both flows authenticate against the private repo using your existing gh auth / GitHub credentials.

Verify installer integrity (recommended, VULN-IAC-001 hardening):

# Download, verify SHA-256, then run if the hash matches.
curl -fsSL -o install.sh https://raw.githubusercontent.com/AI-Marketing-Hub/claude-blog/main/install.sh
echo "029388e448dd29bed259b130c