Substack said my writing was 100% AI. Here's my escape plan.
Part 1 of 3: how a post went from 2.5 days to half a day, and how to set up the same interview workflow in Claude Code.
The 100% score
When I started also posting my blogs on Substack, their AI detector claimed that my text was 100% written by AI. I was surprised when Substack said that, because it wasn’t. I always manually changed some of the wording here and there, so I felt mistreated by the Substack algorithm.
That pushed me to change my workflow a bit to let Claude interview me, and then Claude essentially just assembles my own words that it noted down into a blog and ensures that the flow is nice and easy to read. By doing so, the AI text got cut down to between 50 to 70 percent.
This manual shows you how to set up the same thing. You don’t need to be technical.
What a post used to cost me
Well, before automation, I would say a post took roughly 2 days or 2.5 days, with lots of back and forth using Claude to improve the writing, and then more back and forth to create the LinkedIn post and the Twitter post.
For me, the toughest part was always creating the first draft. Once I have the first draft, it’s much easier for me to improve the flow and the way the text comes across.
These days, it usually takes about half a day to get to a pretty decent level where I can say, “Okay, if I don’t have more time, I can actually already post it.” However, most of the time, I take another hour or so in order to do the final polish on top of it.
What gave my first drafts away
What went wrong along the way is that the first few drafts felt really LLM-generated. I think what actually gave it away as AI text is that probably the grammar was too perfect and too regular, in the sense that no human has that consistency of writing. At least, the way I speak is that I sometimes have longer sentences or shorter sentences, but there’s a sort of random pattern, I guess.
I had to teach Claude, essentially, how to use my own language by starting a voice skill. A skill is a file of instructions that Claude reads before it starts a task. I actually don’t know exactly what it was in the background. It notes down what my voice is, the way I usually speak, the way I usually write, and so forth. Over time, it improved quite a lot.
Claude essentially just assembles my own words.
What you need
- A paid Claude plan. Claude Code is the tool we’ll use, and the free plan doesn’t include it. Pro is the cheapest option, at $20 a month, or $17 a month if you pay for a year.
- A Mac or Windows computer.
- Three things you’ve written. Emails or old posts both work.
You don’t really need a website if you just want to post on socials. If you don’t have your own website, I would recommend you go with Substack, which is pretty much the same, I’d say. On there, you have an easy option to also monetise it if you want to.
Set it up in six steps
This is how I would start off if I was redoing the entire thing again today.
1. Open the terminal. The terminal is a window where you type commands. On a Mac, press Cmd and Space, type Terminal, then press Return. On Windows, open the Start menu, type PowerShell, then press Enter. If you get stuck, Anthropic has a beginner terminal guide.
2. Install Claude Code. Paste the line for your computer, then press Return. Nothing appears while it downloads, so give it a moment.
On a Mac:
curl -fsSL https://claude.ai/install.sh | bash
On Windows:
irm https://claude.ai/install.ps1 | iex
3. Check it worked. Close the window, open a new one, and run this line. You should see a version number.
claude --version
4. Make a folder and start Claude Code. Run these three lines, one at a time. The first time, your browser opens so you can log in.
mkdir my-posts
cd my-posts
claude
5. Paste this prompt. Claude asks for your three writing samples, then asks permission to create the skill. Say yes.
Create a personal Claude Code skill called post-writer at ~/.claude/skills/post-writer/SKILL.md. It helps me write blog posts in my own words.
The skill must do these steps, in this order:
1. Ask what I want to write about and who will read it.
2. Interview me with 10 to 15 questions, three or four at a time. Ask what surprised me, what went wrong and what I would tell a friend. Ask me to answer in full sentences. Follow up on anything emotional or unclear.
3. Save my answers word for word in a file called answers.md.
4. Build the post from my sentences. You may cut, reorder and fix grammar. Do not rewrite my sentences to sound better. Do not invent facts, numbers or stories. If a section has no answer behind it, ask me another question.
5. Suggest five titles and let me pick one.
6. Save the draft as post.md and list any sentence that is not mine.
Before you create the skill, ask me to paste three things I have written. Study how I write, then add a short "My voice" section to the skill with examples of my words, my sentence length and phrases I never use.
When you finish, tell me how to start the skill. Assume I have never done this before.
6. Start your first interview. Type /post-writer and press Return. If nothing happens, type /exit, run claude again, and retry.
The interview feels weird
I’m not going to lie, the first interview felt a bit weird, and I’m still not really used to being interviewed by Claude. Also, I’m using Wispr Flow in order to talk into my computer, so that also doesn’t make it more comfortable for me to just speak out loud in front of everyone in the same coworking space. But I’ll do it anyway. And I’m pretty happy with the results ever since we started this interview-type workflow.
Wispr Flow is an app that turns your speech into text. Typing your answers works too.
Update the skill after every post
After posting everything, I have a long history of changes that I requested Claude to do, and then I usually say, “Okay, given the conversation that we had, update my skill that I use to generate and work out my posts.”
Use that sentence at the end of your session. It’s how your skill gets better.
The Takeaways
- It’s much easier to get started than you think. The final product doesn’t have to be perfect, because over time, with every post, you’ll be improving the quality of your content, writing style, and so on.
- Your early posts will look fine to you. Honestly, if I go back in time and read my first posts, I can actually tell that it was generated. It’s just a different style of writing compared to what I do these days, but when I posted it, to me, it looked pretty much alright.
- Let Claude do the first draft. That was always the toughest part for me.
Next, Part 2 turns your post into a LinkedIn post.
Get the next episode first
Every week: the progress unfiltered, plus what I can't post publicly. The build, the number, green or red.