Guide
Turn one post into many outputs
A good blog post is raw material for a dozen other things — a newsletter issue, a social thread, a LinkedIn write-up, a short summary for a roundup. The work of repurposing is rarely the hard thinking; you already did that when you wrote the post. It is the mechanical lift of getting the text in front of a tool that can reshape it, one post at a time, over and over. When your whole archive lives in one workspace an AI can read, that lift disappears.
Why the whole archive in one place changes the math
Inside Ghost, your posts are locked behind the web editor — you can’t easily feed them to an AI in bulk, so repurposing stays a copy-paste-per-post ritual. Specter connects to your Ghost blog in the browser and brings every post into one workspace, so the entire back catalog becomes source material an AI recipe can work through at once. Specter isn’t an AI itself; it’s the workflow layer that runs the model across your archive. There’s nothing to install — set it up with the first-sync guide if you haven’t. Subscribe now and your workspace opens with 500 free credits.
What a repurposing recipe looks like
Because the outputs usually live somewhere other than your blog — your email tool, a social scheduler — this is mostly a read-and-generate job rather than a publish-back-to-Ghost one. You ask the recipe to read posts and produce new artifacts:
Read this post and draft a newsletter issue from it: a subject line, a short personal intro, the key points in my voice, and a link back to the full article. Keep it tighter than the original.
Or work across the archive to find what’s worth resurfacing:
Look through every post. Suggest ten that would make strong standalone social threads, and for the top three, draft a thread of 5–7 posts each, faithful to the original argument.
The posts stay exactly as they are on Ghost — you’re spinning out derivatives, not editing the source. If a repurposing pass does inspire an edit to the original (a clearer intro, a fixed fact), that change publishes back through Specter the normal way, with a diff to review before it goes live. Browsing your archive and reviewing are free; only the AI run spends credits.
Keep your voice in it
The reason to do this with your own posts and your own archive, rather than a generic content tool, is that the source is you — your argument, your phrasing, your evidence. Prompt for fidelity to the original and review what comes back, the same human-in-the-loop discipline as editing posts with Claude. Repurposing should amplify what you already said well, not flatten it into the same shape every other account is posting.
This is one of a family of AI jobs that open up once the whole blog is in one workspace: refreshing old posts, translating the whole blog, and more. The common thread is that your archive stops being a closed CMS and becomes a corpus your tools can actually use. Subscribe now →
Prefer your archive as plain .md files on disk, fed to your own AI locally? The desktop and open-source edition keeps everything on your Mac.