The $100K Organic Content Team

This department is built for the Head of Growth and the Social Lead running organic short-form for a consumer brand, who ship four or five videos a week and still cannot say which of last month's posts should decide what gets made next month.

Ten specialist agents, one join key, and a week that runs Monday to Friday on a named rhythm. The part most content systems skip is the last one: what happens to a finished post after it stops getting views. Here it becomes a number in a column, that column becomes a median, that median becomes a slot allocation, and that allocation is what the strategist is allowed to plan against next month. The loop is mechanical and every field in it is named.

Every number on this page describes the structure of the system itself, not a client's measured results.

<aside> ⚠️

Before using these prompts you should omit any PII (personal identifiable information) and check with your compliance team and/or your AI policy.

</aside>

Download the pack

<aside> 📦

Ten files. Take them one at a time, or grab the zip.

agent-prompts.md · all ten system prompts, copy and paste

creative-performance-dashboard.xlsx · the input template every agent reads from

hook-library.xlsx · 84 hooks in 7 families

repurposing-matrix.csv · 30 gated repurposing rules

content-brief.md · the brief a creator shoots from

script-templates.md · eight beat structures, one per format

distribution-checklist.md · 32 pre-flight items in six groups

weekly-content-review.md · the Monday agenda and the five flag rules

worked-example-saltwren.xlsx · 26 rows of fictional data and the read built from them

100k-organic-content-team.zip · everything above, foldered

</aside>

File	What it is	What you do with it
`agent-prompts.md`	All ten system prompts in full, with each agent's inputs, output contract, failure modes and handoff	Copy one prompt at a time into a Claude project. Start with agent 10
`creative-performance-dashboard.xlsx`	Eight sheets. Post Performance carries 31 columns, and every field any prompt reads is on one of the eight sheets	Fill Creator Roster once, then paste your post numbers 14 days after each publish
`hook-library.xlsx`	84 hooks across 7 families, 12 per family, plus a family sheet naming each one's failure mode	Give it to the Hook Writer as its pattern library. Number your own hooks from H-101 up
`repurposing-matrix.csv`	30 rules, each with a source format, a performance gate, a target surface and an exact cut rule	Give it to the Repurposing Editor on Friday. Two of the rules are blocking rules
`content-brief.md`	The ten section brief structure, plus a filled example with the non negotiable and creator's call split	Hand to the Creator Manager. One brief, one content id
`script-templates.md`	Eight beat structures with runtime bands and timing, one per controlled format	The Scriptwriter picks by format and does not add beats
`distribution-checklist.md`	32 items in six groups, run against every asset before anything gets a posting slot	Any single fail holds the asset. There are no optional items
`weekly-content-review.md`	The 40 minute Monday agenda, who is in the room, and the five flag rules with their thresholds	Run it before any new work starts on Monday
`worked-example-saltwren.xlsx`	The 26 fictional posts behind the worked example, the read produced from them, and the slot arithmetic	Check the numbers on this page against it. Then delete it and use your own
`100k-organic-content-team.zip`	All nine files in four folders, with a README	Unzip and work from the folder tree

<aside> 🥷

Want this running on your own content instead of a fictional electrolyte brand? Talk to UGC Ninja

</aside>

How the ten compose

Ten agents is only a department if the records chain. Each agent emits the same eight line header before anything else, and the next agent reads it. That header is the whole reason a Friday ship sheet can be traced back to a Monday signal.

RECORD: <record type>
ID: <record id>
ACTOR: <agent name>
DATE: <YYYY-MM-DD>
STATE: draft | approved | shipped | killed
OUTCOME: <one sentence, what this record decides>
JOIN: content_id=<id, or n/a>
UPSTREAM: <the record ids this was built from, or none>

JOIN is the load bearing line. Everything in this system hangs off one content_id, assigned at slate and never reused. It goes on the idea, the hook set, the script, the brief, the ship sheet, the performance row and every repurposed cut, which carries its own new id plus a parent_content_id pointing home. Drop the join key and you have ten prompts. Keep it and you have a department.

flowchart TD
  A1[Trend Researcher] --> S[Content Strategist]
  A2[Audience Researcher] --> S
  A3[Competitive Intelligence Analyst] --> S
  S --> H[Hook Writer]
  H --> W[Scriptwriter]
  W --> C[Creator Manager]
  C --> D[Distribution Manager]
  R[Repurposing Editor] --> D
  D --> P[Performance Analyst]
  P -->|Monthly Creative Read| S
  P -->|Monthly Creative Read| H
  P -->|weekly flags| R
  P -->|boost flags| D
  A2 -.phrase bank.-> H

The two arrows back from the Performance Analyst are the point of the whole thing. Everything else is a content calendar.

The eight coverage areas and the two we added

The brief named eight jobs. Trend research, audience research, competitive intelligence, strategy, hooks, scripts, repurposing, distribution. Two more make it an operation rather than a workflow.

Creator Manager, because this is a creator operation and a script is not a brief. Somebody has to pick which creator shoots it, check they have capacity left this month, split the brief into what is fixed and what is theirs, and confirm the usage rights window before a single frame is shot. That job exists at every agency that has ever had to explain why a video it paid for cannot be run in paid.

Performance Analyst, because without it the other nine have opinions. It is the only agent allowed to assign a verdict, and the only one that turns last quarter's numbers into next month's slot counts.

Download the pack

How the ten compose

The eight coverage areas and the two we added

The ten specialists