agentleFS
athina-aiathina-ai/goose-skills/skills/marketing/analyze-performance-revenue-join/SKILL.md

analyze-performance-revenue-join

Skill1.3k starsChanged 23 days agoMITView on GitHub

Step of the analyze-performance playbook: joins cleaned store or CRM numbers with ad spend to build the business-truth table, MER, new-customer cost and the overclaim ratio. Run analyze-performance instead; not for direct use.

1 other project uses a version of this.

Trending

Quiet since March.thin dataabout the whole repository

Dec 2025: 0 mentionsJan 2026: 0 mentionsFeb 2026: 0 mentionsMar 2026: 1 mentionApr 2026: 0 mentionsMay 2026: 0 mentionsJun 2026: 0 mentionsJul 2026: 0 mentionsAug 2026: 0 mentionsSep 2026: 0 mentionsOct 2026: 0 mentionsNov 2026: 0 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the athina-ai/goose-skills repository that our weekly crawl found: only 1 in all, so this is a hint, not a trend. There is no adoption data for this file yet.

Most recently taken up by

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

The biggest 1 of 1 mention linking to the repository that our crawl found. Each line is their own headline.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are 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.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If the platform and blended stories point different ways: write both at the same grain, each ending "if true, you'd…", a recommendation, …

    line 21

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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

Revenue join (atom)

Load: ../analyze-performance/references/revenue-join.md.

Inputs: clean store/CRM numbers; total spend per platform; platform claims; break-even MER and allowable CAC (campaign brief economics box / measurement contract); last week's report (the story the marketer picked).

Do:

  1. Business-truth table: this week, last week, 4-week average, same week last year.
  2. MER, new-customer MER, nCAC, contribution after ads — each vs break-even / allowable / target.
  3. Overclaim ratio, like-for-like as in the reference (claimed purchases ÷ store orders, or claimed revenue ÷ store gross; a floor when a claimant is missing), with its 4-week trend.
  4. Marginal: Δ new-customer revenue ÷ Δ spend vs last week and vs the 4-week average.
  5. If the platform and blended stories point different ways: write both at the same grain, each ending "if true, you'd…", a recommendation, and the cheapest test that would settle it. Carry forward the story the marketer picked last time unless a test changed it.
  6. B2B: pipeline chain and cost per qualified lead / opportunity instead of revenue.

Output: the report's Business truth, overclaim line and Two stories 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.