CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

analyze-performance-revenue-join

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.

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/marketing/analyze-performance-revenue-join/SKILL.md
SKILL.md
Quality
Evals
Security

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.

Repository

gooseworks-ai/goose-skills

Path

skills/marketing/analyze-performance-revenue-join/SKILL.md

Last updated
First committed

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.