Lesson 5 · 18 min
Agents do the repetitive work: run the X-ray, build the report, suggest titles, write the draft. What gives the client confidence is that nothing goes live without a human approving it, and that their password is never in your repository. One folder per client, always with the same structure.
Start the lesson
Goal: set up a client's folder with a fixed structure, human gates and secrets kept out of the repository, so you can deliver with agents without losing control.
Tap each block.
The agent speeds up the work; the gates protect the client's trust.
Tap each step.
Create the folder with the fixed structure and an instructions file for the agent (AGENTS.md or CLAUDE.md) with the client's rules: tone, what not to publish, who approves.
Versioned in git: every change has a date and an author, and can be undone.
Keys and credentials live in environment variables, never in the repository or in the prompt.
Access to the client's dashboards is read-only, authorized in writing (lesson 7).
If the client doesn't have time to review, the cadence slows down. The gate is not skipped.
Help: the agent delivers the summary of what changed and the 3 things for the client to confirm.
A links script picked up the wrong course name in a subfolder. It was caught in the pilot, before the push. That's what running small and checking beforehand is for.
Every number the agent produces goes through a cross-check: the part can't be bigger than the whole.
At INEMA, an export summed branded impressions by query and page and came out higher than the week's total. The fix was to sum by query only.
Copy it and swap out what's between < >.
mkdir -p <client>/{docs,briefings,reports,scripts,data/gsc}
cd <client> && git init -b main
printf '.env\n*.key\ncredenciais/\n' > .gitignore
touch .env AGENTS.md data/urls-chave.txt data/consultas-alvo.txtdocs/ diagnosis, plan, proposal, authorization briefings/ <slug>.md, one per page data/gsc/ weekly export (append-only) reports/ semana-<data>.md, mensal-<mês>.md scripts/ X-ray, export, report AGENTS.md client rules for the agent .env secret (kept out of git)
# Rules — <client> - Tone: <how the client speaks>. Audience: <who>. - Every number or quote comes from a client source; with no source, mark it PENDING and do not publish. - Before publishing: complete quality checklist. - Gate 1: <name> approves the month's list. Gate 2: <name> approves each page. - Never: publish without approval, a big batch all at once, a page per keyword variation. - Model through the subscription. Paid API only with written authorization for the purpose. - Secrets only in .env. Never print a key in a log or report.
It can be your own site as client zero.
Create the folder with the structure, the .gitignore and the filled-in AGENTS.md. Make the first commit.
Done when: the git status command does not show the .env, the AGENTS.md has the tone, the source rule, both gates with a name and the API rule, and the first commit exists.
Write down who approves each gate, how long it takes, and what happens if that person has no time that week.
Done when: the list has both gates with a name, time in minutes, and the sentence "if there is no review, the cadence drops; the gate is not skipped".
The explanation appears after your answer.
Question 1 of 4
The client disappeared on vacation and didn't review the week's pages. What do you do?skill
Question 2 of 4
Where does the client's Search Console read credential live?
Question 3 of 4
The agent says the week's branded impressions were higher than the total. What does that indicate?
Question 4 of 4
Where can the agent work without human approval?
Choose an option. The explanation appears after your attempt.