# Skill · The agency in a folder

Install procedure the Grok Bot runs. Intake is already loaded. Drive the named tools. Stop only for login, 2FA, or pay. Write the File log. Do not hop on a call.

Human-first. The blueprint works with no agent. A desktop folder, four written SOPs, a Monday checklist, a Friday report. AI is a later rung. Paid installer is last.

## Fit gate

Fit: starting or running a small ads / demand / advisory shop. They repeat the same jobs. They want the shop to run if they are not in the chat.

Unfit: a local trades shop that needs jobs on the calendar (route to Ugly ads that book the town, or Recover the job they turn down). Someone who will not write anything down (stop).

If unfit, stop. Do not scaffold an agency tree for a trades calendar.

## The lock

Even without the AI agent, if they just follow the blueprint they can do it and achieve the result.

- No GitHub yet? Same folder tree on the desktop. Private repo when they are ready.
- No Claude Code? Open the SOP and do the steps. The result is the same.
- AI / terminal / cron is how it gets faster. Not how it becomes possible.

A chat is not the system of record. A folder is.

## Tools

1. Folder tree (desktop first, private GitHub when ready)
2. Client brief (voice, brand, offer, winners, losers, dos and donts)
3. Advertising SOPs (hooks, statics, budget pacing, campaign monitoring, Friday report)
4. Content SOPs (pull ideas, taste gate, brief, draft, publish)
5. Ads Manager (human opens it and follows the pacing / monitor SOP)
6. Claude or ChatGPT (optional: runs one skill against two files. Does not hold the system of record)
7. File log

No Cal.com. No GHL sales calendar. No funding. Do not invent a snapshot URL.

## Services

Two service folders. Write both if they sell both. Advertising is the month-one week loop. Content is the second loop. Same rule: the file is the job.

### Advertising
hooks · statics · hook-story-offer · campaign-monitoring · budget-pacing · friday-report

Month one cadence (checklist first, cron later):
- Monday: budget pacing
- Daily: campaign monitoring
- Friday: client reporting

### Content
pull-ideas · taste-gate · brief · draft · publish

Taste gate is human. That step never goes to an agent first.

## Run

### 1. Make the tree
- Human path: create the folder tree on the desktop from the exact names in the SOP. No GitHub required.
- Bot path: scaffold the same names. Stop for GitHub login / 2FA if they want the private repo today.
- Do not live in a ChatGPT project as the system of record.

### 2. First client folder
- Human writes: voice, brand, offer, 3 winners, 3 losers, dos and donts. Use the client brief template.
- Bot can interview and draft. Human signs the brief. A clone of this folder is how a new hire starts.

### 3. Write the SOPs
- Human writes the four Advertising SOPs from the templates on the File: hooks, statics, budget pacing, Friday report. Add campaign monitoring the same day.
- If they sell content, write brief + draft from the templates. Taste gate stays a human checklist.
- Bot can draft from how they already work. Human keeps the file.
- Do not skip writing because "the agent will know."

### 4. Pace spend
- Human path: Monday, open Ads Manager, follow the pacing SOP. Tick the checklist. Weekend rule is in the file.
- Bot / cron: later. Same SOP.

### 5. Monitor
- Human path: 15 minutes. What spent. What died. Kill or raise from the monitor SOP.
- Bot: later. Same SOP.

### 6. Friday report
- Human path: fill the report outline. Same sections every week.
- Bot: later. Same outline.

### 7. Human in the loop
- Strategist gets ideas (notebook, or later a transcript). Picks 3. That pick is never an agent's first move.
- Run the hook SOP with only the two files the task needs (voice + hooks), in ChatGPT / Claude or in a terminal.
- Content path: approved idea → brief SOP → draft SOP + voice file → human final pass → publish.
- You always pick.

### 8. File log
Write clients, SOPs written, paced, reported, ideas approved, drafts published.

## File log

Columns: date · client · job (pace / monitor / report / hooks / content) · files used · paced Y/N · reported Y/N · idea approved Y/N · status

## Done

Stop when a week has spend paced from a file, a report that went out from a file, and a new job added to an SOP. Not a smarter chat.

## Do not

- Do not live in ChatGPT projects as the system of record.
- Do not dump 12 files into one chat.
- Do not skip writing the SOP because "the agent will know."
- Do not put sales on a GHL calendar.
- Do not put this File on Cal.com.
- Do not talk funding.
- Do not promise a revenue figure.
- Do not send a taste-gate pick to an agent first.