How to edit Ghost posts with Claude, ChatGPT, or Gemini

AI is excellent at rewriting prose, fixing copy, and grinding through tedious edits. The problem is a raw chat window can’t reach your Ghost blog. There’s no plugin that lets it into your Ghost web editor, and your CMS is a hosted admin panel behind a login — so the usual ritual is copy a post out, paste it into a chat, paste the revision back, one post at a time, with no safety net on what lands.

Specter closes that gap. Connect your Ghost blog in the browser and your published posts open as clean, editable content — then run AI as recipes across the whole archive and review what changed before it ships. It edits posts you’ve already published, not just new drafts, and there’s nothing to install. Subscribe now and your workspace opens with 500 free credits.

This is the hands-on version. If you want the bigger-picture case for AI plus Ghost, read the overview first.

A note before we start: Specter isn’t an AI itself. It’s the workflow and control layer that runs the model over your whole site and shows you every change before it ships. Browsing your content and reviewing diffs are free; only AI runs spend credits.

The workflow, step by step

Connect your Ghost blog in the browser. Paste your details (you’ll want a Ghost Admin API key) and every post lands in one workspace as clean, editable content with its title, tags, status, feature image, and excerpt intact. Browsing it is free.
Run a recipe — or edit a post by hand. Be specific about scope: one post or the whole archive, and what you do and don’t want touched. Because the workspace holds your whole site, a recipe runs with the full archive as context, not one post at a time.
Review the changes as a diff. Read exactly what would change in each post. Tweak anything the AI overcooked. This is the step that keeps your voice intact — and it’s free.
Publish back. Approve what’s right. If a post changed in the Ghost editor and in your workspace since the last sync, Specter prompts you about the conflict instead of silently overwriting; every publish keeps a snapshot behind it.

Example recipes that actually earn their keep

These are the kinds of jobs that take an afternoon by hand and minutes as a recipe across the archive:

Rewrite the intro paragraph of every post to be punchier and lead with the reader’s problem. Keep the same facts, keep my voice, and don’t touch anything below the first heading.

For any post missing an excerpt, write a 150-character meta description based on the post body. Don’t change posts that already have one.

In this single post, fix passive voice and cut filler words. Show me the changes — don’t rewrite sentences that are already clear.

Start narrow. Run a recipe on one post, check the result, then scale it to the archive once you trust the output. Only the AI run spends credits, so you can see exactly what each recipe does before committing to a sweep.

You review the diff — that’s the whole point

The reason this workflow beats an auto-publishing AI button is the human in the loop. Nothing reaches your live blog until you’ve looked at it. You read the diff, keep the lines you like, throw out the ones that sound like a robot, and only then publish. You are never one click away from pushing AI slop to readers.

That matters most for posts that already rank or already get traffic. Most AI-and-Ghost tools are publish-only — they push new drafts and can’t touch what’s live. Because Specter syncs two ways, you can hand a recipe your three-year-old cornerstone post, improve it, review the change, and update it in place.

Where this fits

Editing one post for clarity is the everyday case. The same setup scales to bigger jobs — for example, bulk-editing Ghost posts for SEO, where a recipe generates or rewrites meta descriptions and titles across your whole archive in one pass, then you review and publish.

The mental model is worth holding onto: Ghost stays your publishing home, the webapp gives you the whole archive in one reviewable place, and AI does the actual writing work in between — with a diff that tells you the truth before you commit. Subscribe now →

Prefer your posts as plain .md files on disk, edited with Claude Code or your own scripts locally? The desktop and open-source edition runs the same sync, preview, and conflict handling on your Mac.