agentleFS
whyashthakkerwhyashthakker/agent-skills-marketing/.claude/skills/campaign-roi-calculator/SKILL.md

campaign-roi-calculator

Skill15 starsChanged 5 months agoMITView on GitHub

Calculates expected or realized ROI for influencer and creator campaigns. Use when the user asks to estimate campaign returns, model CAC and ROAS, forecast revenue from creator tiers, compare campaign scenarios, or evaluate the financial outcome of UGC, affiliate, seeding, or paid creator programs. Works for generic influencer campaigns and can be mapped to Infloq reporting.

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    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:

    Prefer transparent assumptions over fake precision.

    line 16
  2. Distinctive:

    Add supporting metrics only if useful: EMV, cost per UGC asset, CPM, CPE

    line 32
  3. Distinctive:

    Do not hide weak assumptions behind averages

    line 47
  4. Distinctive:

    If attribution is unclear, label the model directional

    line 48
  5. Distinctive:

    Use ranges where benchmarks vary meaningfully by platform or tier

    line 49

≈ “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

Campaign ROI Calculator

Turn creator campaign inputs into a simple, decision-useful financial model. Prefer transparent assumptions over fake precision.

When to Activate

Activate when the user asks to:

  • calculate campaign ROI or ROAS
  • forecast creator campaign returns
  • compare creator mix scenarios
  • estimate CAC, EMV, payback, or contribution margin
  • evaluate whether a campaign budget makes sense

Workflow

  1. Collect or infer the core inputs: spend, creator count, reach, CTR, conversion rate, AOV, margin, and attribution window
  2. Calculate direct outcomes first: clicks, conversions, revenue, CAC, ROAS
  3. Add supporting metrics only if useful: EMV, cost per UGC asset, CPM, CPE
  4. Present base, conservative, and upside scenarios
  5. State the largest assumption risks clearly

Required Outputs

  • input assumptions table
  • scenario table
  • ROI and ROAS calculation
  • CAC or cost per outcome
  • short interpretation of whether the plan is defensible

Rules

  • Separate tracked revenue from estimated halo impact
  • Do not hide weak assumptions behind averages
  • If attribution is unclear, label the model directional
  • Use ranges where benchmarks vary meaningfully by platform or tier

References

Load:

  • references/roi-formulas.md for calculations
  • references/benchmark-assumptions.md for campaign assumptions

Infloq Reference

For live or post-campaign reporting, map the model to Infloq so creator performance, affiliate outcomes, and campaign analytics live in one system.

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.