How to edit Ghost posts with Claude, ChatGPT, or Gemini
Claude, ChatGPT, and Gemini are excellent at rewriting prose, fixing copy, and grinding through tedious edits. The problem is they can’t reach your Ghost blog. There’s no plugin that lets them into your Ghost web editor, and your CMS is a hosted admin panel behind a login — not something they can open. They work on the text and files you give them.
So the trick is simple: bring your Ghost blog to where the AI already works. Sync your posts down to a folder of plain markdown, edit them with Claude, ChatGPT, or Gemini like any other text file, then sync the changes back to Ghost. That round trip is exactly what Specter handles: a two-way sync between Ghost and local markdown — it can edit posts you’ve already published, not just new drafts.
This is the hands-on, tool-specific version. If you want the bigger-picture case for AI plus Ghost, read the overview first.
A note before we start: Specter has no built-in AI. It doesn’t bundle a model or charge for tokens. You bring Claude, ChatGPT, Gemini, Copilot — whatever you already pay for. Specter is the bridge; you bring the intelligence.
The workflow, step by step
- Sync your Ghost blog down to a local folder. Point Specter at your site (you’ll need a Ghost Admin API key) and choose a folder. Specter pulls every post down as a markdown file with its frontmatter — title, tags, status, feature image URL, excerpt — preserved. The folder can be an Obsidian vault or just a plain directory of
.mdfiles. - Point your AI at the folder. With Claude (Claude Code, or the desktop app with file access), give it the folder path and it can read and write your posts directly. Prefer ChatGPT or Gemini? Open a post in any editor and paste it in — or upload the file — then paste the revision back. Either way, the AI is now working on your actual posts.
- Give it an instruction. Be specific about scope — one post or the whole archive — and about what you do and don’t want touched.
- Review the changes. Read the diff. Tweak anything the AI overcooked. This is the step that keeps your voice intact.
- Run a dry-run preview in Specter. Before anything touches Ghost, Specter shows you exactly which posts would be created, updated, or flagged as a conflict. This is essential after a big AI edit — you see the blast radius first.
- Sync back. If the preview looks right, push the edits to Ghost. If there’s a conflict (you changed a post in the Ghost editor and locally), Specter prompts you instead of silently overwriting.
Example prompts that actually earn their keep
These are the kinds of jobs that take an afternoon by hand and minutes with AI. Run them against the synced folder.
Rewrite the intro paragraph of every post in this folder 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.
Look through the frontmatter of each .md file. For any post missing
an "excerpt" field, 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 prompt on one post, check the result, then scale it to the archive once you trust the output.
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 in your editor, you keep the lines you like, you throw out the ones that sound like a robot, and only then do you run the dry-run preview and sync. 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 Claude your three-year-old cornerstone post, improve it, preview 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 you have an AI generate or rewrite meta descriptions and titles across your whole archive in one pass, then preview and sync.
The mental model is worth holding onto: Ghost stays your publishing home, your Mac holds the source of truth as markdown, and your AI tool of choice does the actual writing work in between. Specter just keeps the two ends honest, so you can use the tools you already trust on the blog you already run.