agentleFS
gooseworks-aigooseworks-ai/goose-skills/skills/marketing/plan-campaign-budget-and-tests/SKILL.md

plan-campaign-budget-and-tests

Skill1.3k starsChanged 23 days agoMITView on GitHub

Step of the plan-campaign playbook: splits the budget across chosen channels, checks per-channel minimums, and writes the test plan and paid structure. Run plan-campaign instead; not for direct use.

1 other project uses a version of this.

Trending

More talk lately.about the whole repository

Dec 2025: 0 mentionsJan 2026: 0 mentionsFeb 2026: 0 mentionsMar 2026: 0 mentionsApr 2026: 0 mentionsMay 2026: 1 mentionJun 2026: 0 mentionsJul 2026: 2 mentionsAug 2026: 1 mentionSep 2026: 0 mentionsOct 2026: 15 mentionsNov 2026: 1 mention
Dec 2025Jun 2026Nov 2026
Mentions a month of the gooseworks-ai/goose-skills repository that our weekly crawl found. There is no adoption data for this file yet.

Most recently taken up by

Who's talking about gooseworks-ai/goose-skills

The biggest 5 of 20 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 20

Talked about on GitHub (20 times).

On GitHub · 20

15 more on GitHub

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Inputs: Run/Test legs and their minimums.

    line 14
  2. Distinctive:

    Write tests: one variable, cells, $/cell, readable threshold, end date, primary business metric, Win / Lose / Unclear actions.

    line 20

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Budget split, test plan, paid structure (atom)

Load: ../plan-campaign/references/budget-and-tests.md.

Inputs: Run/Test legs and their minimums; economics box; per-leg targets; the learnings log (knowledge_search source_types: ["learning"]) so no paid-for test is re-bought; the brief's calendar phases.

Do:

  1. Lay out every budget line; ~70/20/10 proven/promising/experiments as the default shape (rule of thumb), 10–20% held reserve with its release rule. No proven channel → say the plan is mostly tests.
  2. For each paid leg: $ and %, its learning minimum, clears yes/no. A leg that does not clear is cut, merged, moved to a higher-funnel event, or labelled directional.
  3. Phase the spend (pre-launch / launch week / sustain, or by week).
  4. Write tests: one variable, cells, $/cell, readable threshold, end date, primary business metric, Win / Lose / Unclear actions. Small budgets test big swings.
  5. One paid-structure line per paid leg (objective/event, campaigns/ad sets, audience approach, budget type and amount, creative count, destination with UTMs, applied by GooseWorks levers or written instructions).
  6. Reconcile: lines sum to the budget; leg spend ÷ expected CPA = leg target in the goal chain.

Output: the brief's ### Budget split, ### Paid structure, ### Test plan sections.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.