Content Spy pulls the top short-form posts in your space, breaks down why they land, watches what is trending across the open web, and hands you scripts you can film today. The whole thing runs on your machine.
Run these inside Claude Code.
Open Claude Code in the folder you want it to live in, paste each step, hit enter.
By the third command it is already pulling posts.
A reel goes off, you copy the format, and the version you film flops. The reason is almost never the part you noticed. The post that worked had a specific hook structure, a pattern interrupt at 0:03, a retention beat at the 8-second mark, and the surface you copied sat above all of it. You were studying the paint, not the frame.
Content Spy automates the research-to-script loop that runs every week for EDGE and becomingscott. It scrapes the top creators in your niche, transcribes the videos, breaks down what is actually doing the work, scans the open web for what is trending right now, and writes you scripts in your own voice that are grounded in what it found.
The whole loop runs on your laptop, sharpens itself every week, and the output is plain markdown that lives in a folder you own.
Every stage reads and writes to the same output/ folder, so the next stage picks up exactly where the last one stopped. Run them one at a time when you want to poke at the middle, or chain the whole thing with /run-all and walk away.
A small local app handles the mechanical work, an AI prompt layer handles the thinking, and they meet in the output/ folder on your disk. Markdown is the source of truth in the middle, and both sides read and write to it freely.
A light Express server with a vanilla-JS dashboard sitting on top. No framework, no database, just JSON indexes derived from the markdown files themselves so everything stays inspectable.
localhost:3000A set of markdown prompts you run on demand inside Claude Code. This is where the thinking happens, and every prompt is plain text you can open, read and rewrite.
/setup/run-allLocal-first on purpose. Everything runs on your machine, your data sits in your own output/ folder, no API keys are baked into a server somewhere, no telemetry pings home, and nothing leaves your laptop unless you decide to send it.
The first batch of scripts the tool writes is good enough to film, but the real unlock is the second loop. Take three scripts from one week, rewrite the hooks in three different directions, post them spread across the calendar, then let the dashboard tell you which one actually moved when the numbers refresh.
That signal goes straight back into the insights memory underneath the prompts. By the third cycle the writing is no longer aimed at the niche average, it is aimed at the specific audience you have been training it on through your own posts. That is the point where most people drift away from the tool, and it is also the point where the tool finally starts to earn its keep.
Run /run-all daily, film three from the queue every week, and read the dashboard on a Sunday afternoon. Two cycles in, the scripts will sound more like you than anything you have written by hand in months.
Book a call and we will work out the shortest path. Sometimes that is me doing the build, sometimes it is advising you through it, sometimes it is handing you to the right person in the network.
Book a call →