Operations & admin · Claude Code

Build an agency knowledge base that drafts copy, reports and onboarding

Idea + starter prompt, not run by us yet

For: Small agency owners who repeat the same client setup and reporting work

Victor Chazarra used plain-language prompts in Claude Code to turn a git repository into his agency's working brain. It has a CLAUDE.md file that routes requests, a template for each client, skills for ad copy, reporting and onboarding, and a bulk ad publisher fed by a Google Sheet. The build took three days. A trial pass, then a real run, made 48 paused ads in roughly two minutes.

Steps

1. Build the routing file and the client onboarding template first, as the author advises.
2. Connect git syncing from the very first day so work is saved and shared.
3. Create one skill at a time: copywriting, then reporting, then onboarding.
4. Test every piece on real client data and check the output files yourself.
5. For the ad publisher, start with a dry run and create ads as paused so you can review them before they go live.

Starter prompt

Trial first: use a made-up client called [Example Client] with invented numbers, in a new folder called [agency-trial]. Test every skill on that client only.

Set up this folder as a git repository for our client work. Create a CLAUDE.md file that routes requests, a template folder for a new client, and three skills: ad copywriting, monthly reporting and client onboarding. For each skill, ask me what inputs it needs. Show me the folder structure first.

Stop and wait for my yes before anything is published, sent or pushed. A finished skill is not permission. Any ad tool you write must have a dry-run mode and must create ads in a paused state, and I will switch on the first live ad myself. Do not ask me to paste account passwords.

Original post: sucana.ai · found via agentusecases.ai. Written up in our own words. We haven't run it, so test it on made-up data first.