$pages = [

$title =

wp-publish

;

$content = [

wp-publish is a Claude Code skill that turns your conversation with Claude into a WordPress.com site. You write in markdown — in Obsidian, vim, whatever you like. Claude handles everything else: editing your prose, structuring your metadata, converting your content, choosing your theme, debugging your layout, and publishing to WordPress.com. One conversation. Zero browser tabs.


What Claude actually does

Most publishing tools move content from A to B. wp-publish does that too, but that’s really just the start.

When you fire up the skill in Claude Code, Claude becomes a collaborator on your site — not just a deployment pipeline. In a single session, Claude might:

  • Edit your draft for tone, clarity, and structure
  • Handle your metadata — frontmatter, categories, excerpts, SEO fields — all taken care of, so you’ll never need to touch YAML or a dashboard checkbox again, unless you want to
  • Research a theme, compare options, and help you adapt your content to match
  • Spot a design issue and fix it in the block markup before you notice
  • Walk you through the few things that still need a dashboard — like uploading images or tweaking navigation — step by step, so you’re never lost in a menu

The site you’re looking at was built like that. Claude wrote the skill, the converter scripts, the content structure, and most of the words you’re reading. Michael brought the ideas, the feedback, and an extra pair of human subagent hands when it was time to click through dashboards or fret over colour schemes.


Your files, your way

Your content is safe in your WordPress.com database — hosted, backed up, and served to the world. But it’s also yours as plain markdown files in a folder on your machine. Open it in Obsidian for a visual writing experience. Grep it from your terminal. Back it up with git. It’s text. You can do what you want with it.

WordPress.com handles the hosting, the themes, and the infrastructure. Your file system handles the rest.


The tab-switching problem

You’re writing a post in your editor. Now you need to check your site’s SEO settings — that’s a browser tab. Upload an image — another tab. Fix a heading that renders wrong — back to the editor, then back to the preview. Research a theme — four more tabs. Paste your content into a dashboard, lose your formatting, fix it, publish, realise you forgot the excerpt.

wp-publish keeps you in one place. You write, you talk to Claude, things happen. When something does need the dashboard, Claude tells you exactly where to go and what to click — then you’re back in your terminal, where you started.


Built in the open

This site is the product demo. Every page is a markdown file, published by Claude via MCP. The skill and an example site are on GitHub.

Built during an Automattic support rotation in March 2026 by Michael Pick (content designer) and Claude (AI, running in Claude Code on Michael’s terminal). Neither of us could have built it alone.

wp-publish follows the open Agent Skills standard. Pull requests welcome.

Read how we built it | About the project | Get started

];

Is this your new site? Log in to activate admin features and dismiss this message
Log In