Agent skill

Unit Economics

by ericrisco in ericrisco/rsc-harness

A skill your agent uses when computing or improving the per-customer economics of a business — CAC, LTV, CAC payback period and contribution margin — judging whether the ratios are healthy against…

MITAuto-check passedBusiness, Finance & HR

Install Unit Economics

skills CLI
$ npx skills add ericrisco/rsc-harness --skill unit-economics -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install ericrisco/rsc-harness unit-economics --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/ericrisco/rsc-harness.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/unit-economics .claude/skills/unit-economics && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
unit-economics
GitHub stars
174
Token cost
~3.2k tokens
SKILL.md length
1,548 words
Files
5 (incl. scripts, references)
Skills in repo
233
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses when computing or improving the per-customer economics of a business — CAC, LTV, CAC payback period and contribution margin — judging whether the ratios are healthy against…

  • Works in 7 steps: Gross margin first. Every downstream… → CAC, fully loaded. Include all sales +… → Contribution margin per customer. ARPA… → …
  • Improving the per-customer economics of a business — CAC
  • SKILL.md covers What this skill produces, The four numbers and the input…, Order of operations (the spine) and Get the inputs honest, plus 7 more sections
  • Runs Shell scripts from its folder

What it does

Unit Economics is an agent skill from ericrisco/rsc-harness. Use when computing or improving the per-customer economics of a business — CAC, LTV, CAC payback period and contribution margin — judging whether the ratios are healthy against current norms, and naming the one lever that fixes the worst number. Covers a blended CAC that hides a bleeding channel, and a model that shows profit while each customer loses money. NOT the multi-year P&L or scenario projection (that is financial-model).

Its SKILL.md is about 3.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 7 other files, including scripts and reference files (for example `evals/README.md`, `evals/cases.yaml` and `references/formulas.md`).

It sits in Business, Finance & HR, covering Financial modeling. The repository describes itself as: Your agent invents things because it has no memory, and can't touch your database because it has no arms. rsc is the meta-harness that gives it both, plus the trade to know the… The licence is MIT.

When your agent uses it

  • Improving the per-customer economics of a business — CAC
  • CAC payback period and contribution margin — judging whether the ratios are healthy against current norms
  • Naming the one lever that fixes the worst number

Example prompts

  • “/unit-economics”

Requirements

  • A Bash shell

Workflow steps

7 steps, taken from the first numbered list in SKILL.md.

  1. Gross margin first. Every downstream metric multiplies by it. If gross margin is unknown, the COGS per unit must be tracked first (route…
  2. CAC, fully loaded. Include all sales + marketing cost; exclude customer-success/retention spend and returning customers.
  3. Contribution margin per customer. ARPA minus variable cost to serve — the dollars that actually pay back CAC.
  4. LTV, capped. Gross-margin LTV with a lifetime cap (see conservatism), not 1/churn run to infinity.
  5. Payback period. CAC ÷ monthly contribution margin.
  6. Ratios. LTV:CAC and NRR/GRR for context.
  7. Diagnose & prescribe. Find the worst number, name its cause, name the lever.

What it can do on your machine

Read from SKILL.md and the folder at commit e3d5b33. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 1 file in scripts/ (Shell), which the agent can run.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Unit Economics loads about 3.2k tokens when it runs, and up to ~4.6k if it reads all its reference files. Until then it costs about 113 tokens; SKILL.md has 1,548 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~113
When it runs · the whole SKILL.md, loaded when a task matches
~3.2k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~4.6k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from ericrisco/rsc-harness at commit e3d5b33, republished under its MIT licence (© ericrisco). 1,548 words, ~3,210 tokens.

Download SKILL.mdSave it as .claude/skills/unit-economics/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.
name
unit-economics
description
Use when computing or improving the per-customer economics of a business — CAC, LTV, CAC payback period and contribution margin — judging whether the ratios are healthy against current norms, and naming the one lever that fixes the worst number. Covers a blended CAC that hides a bleeding channel, and a model that shows profit while each customer loses money. NOT the multi-year P&L or scenario projection (that is `financial-model`).
tags
cac, ltv, payback-period, contribution-margin, unit-economics, ltv-cac-ratio, nrr, saas-metrics
recommends
financial-model, pricing, retention, cost-tracking, forecasting, investor-materials, dashboard
origin
risco

Unit economics

Answer one question honestly: does one customer pay back more than it cost to win and serve them, and how fast? You compute four load-bearing numbers — CAC, contribution margin, LTV, CAC payback period — plus the two ratios operators and investors actually argue about (LTV:CAC, NRR). Then you diagnose why a number is where it is and name the single lever that moves it.

This is a measurement-and-diagnosis skill, not a projection skill. You do not build the multi-year model here (that is the financial-model sibling); you build the per-customer truth that the model's growth assumptions have to rest on.

What this skill produces

A unit-economics worksheet (unit-economics.{yaml,csv,md}) where:

  • a block of named inputs — period S&M spend, new customers, monthly ARPA, gross margin %, monthly churn, optional segment rows — is stated explicitly;
  • every derived figure (CAC, contribution margin, LTV, payback, LTV:CAC) is recomputed from those inputs so the relationships are self-consistent;
  • the worst number is diagnosed and one concrete lever is prescribed.

scripts/verify.sh re-derives the figures and fails if the arithmetic lies (see the last section). If you only hand back prose, you have not finished — emit the worksheet.

The four numbers and the input people get wrong

Each formula has one input that, done sloppily, silently invalidates everything downstream. Tag the input, not just the result.

NumberFormulaThe input people get wrong
CACfully-loaded S&M spend ÷ new customers (same period)the numerator — ad-spend-only CAC understates true CAC ~3.5×
Contribution margin / customerARPA − variable cost to serve (COGS + variable support + payment fees)confusing it with company-wide gross margin %
LTV(ARPA × Gross Margin %) ÷ churn rateusing revenue instead of gross-margin dollars
CAC payback (months)CAC ÷ (monthly ARPA × Gross Margin %)leaving gross margin out of the denominator

Worked Bad → Good — the revenue-LTV inflation. Same inputs: ARPA $400/mo, gross margin 75%, monthly churn 3%.

text
Bad  (revenue LTV):       400 / 0.03          = $13,333   <- overstates by 33%
Good (gross-margin LTV): (400 * 0.75) / 0.03  = $10,000   <- what a customer is actually worth

LTV must use gross-margin dollars because not all revenue is profit — hosting, support, and payment fees come out first. The revenue version flatters the LTV:CAC ratio and is the single most common dishonesty in a deck. (Beancount.io "2026 SaaS Metrics Stack" 2026-05-10; ChartMogul LTV guide; both accessed 2026-06-02.)

Full derivations, cohort-LTV vs formula-LTV, the Skok discounted model, and segment roll-up math live in references/formulas.md. Read it before you defend a number to an investor.

Order of operations (the spine)

Run these in order — each step is an input to the next, so skipping one makes everything after it fiction.

  1. Gross margin first. Every downstream metric multiplies by it. If gross margin is unknown, the COGS per unit must be tracked first (route to cost-tracking) — you cannot compute LTV or payback on a guessed margin.
  2. CAC, fully loaded. Include all sales + marketing cost; exclude customer-success/retention spend and returning customers.
  3. Contribution margin per customer. ARPA minus variable cost to serve — the dollars that actually pay back CAC.
  4. LTV, capped. Gross-margin LTV with a lifetime cap (see conservatism), not 1/churn run to infinity.
  5. Payback period. CAC ÷ monthly contribution margin.
  6. Ratios. LTV:CAC and NRR/GRR for context.
  7. Diagnose & prescribe. Find the worst number, name its cause, name the lever.

Get the inputs honest

CAC is fully loaded or it is a lie. Decide what goes in the numerator before you divide.

In the CAC numeratorOut of the CAC numerator
Sales + marketing salaries & benefitsCustomer-success / retention spend (that protects LTV, it doesn't acquire)
Sales commissions & SDR/AE compR&D / product engineering
Ad spend, content, events, agenciesOverhead/G&A not tied to acquisition
Marketing & sales tooling(Denominator) returning / reactivated customers — only count new logos
Founder selling time (impute a salary)

Three rules that catch most errors:

  • Gross margin, not opex margin. Gross margin reflects COGS (hosting, support, payment fees), not salaries/rent. Mixing in opex understates margin and quietly tanks LTV. (Beancount.io 2026-05-10, accessed 2026-06-02.)
  • Match time units. Monthly ARPA pairs with monthly churn; annual with annual. Mixing them silently 12×'s or ÷12's the LTV — the most common arithmetic error in the whole exercise. (ChartMogul; metrickit LTV guide; accessed 2026-06-02.)
  • Right period, right denominator. Spend in period P ÷ customers acquired in period P. Don't divide this quarter's spend by all-time customers.

Segment before you optimize

A single blended number hides the only insight that matters. Reporting one blended CAC of $1,200 when self-serve is $80 and field sales is $40,000 tells you nothing actionable — the channels have wildly different CAC, ARPA, and churn. (lucid.now LTV/CAC errors; andrewchen; accessed 2026-06-02.)

text
Blended CAC $1,200  =  self-serve $80  +  inside sales $900  +  field $40,000
                       (lever: scale)   (lever: AE ramp)      (lever: ACV / cycle)

Two more separations to keep clean:

  • Paid CAC vs blended CAC. Blended includes free/organic; paid isolates the channels you can actually scale with money. Optimize paid; report both.
  • Self-serve / inside sales / field sales. Split on go-to-motion, because the lever for each is different. If one segment is bleeding while blended "looks fine," that's exactly the non-obvious failure this skill exists to surface.

Benchmarks (2025-2026)

A ratio is a conversation-starter, not a pass/fail grade. Read the whole row before you celebrate or panic.

MetricElite / top quartileHealthy / medianConcern
CAC payback< 12 monthsB2B SaaS median 12-18 mo24+ months = sustainability concern
Payback by ACV~9 mo at ACV ≤ $5K—~24 mo at ACV > $100K (expected, not bad)
LTV:CAC3:1 to 5:1median B2B ≈ 3.2:1< 3:1 overspending; > 5:1 under-investing in growth
NRRtop quartile 115-125%healthy 105-115%< 100% net contraction
GRR——high NRR + low GRR = expansion masking churn

(Beancount.io 2026-05-10; First Page Sage CAC Payback Benchmarks 2025; Optifai B2B LTV benchmark, 939 companies; cast.app NRR; all accessed 2026-06-02.)

The honest framing: a 2.5:1 with 9-month payback and 120% NRR beats a 4:1 with 36-month payback and 95% NRR. Payback and NRR decide whether you can survive the gap between spend and return; the ratio alone can't. Rule of 40 (ARR growth % + profit margin % ≥ 40%) is the company-level destination these feed — cite it, but compute it in financial-model, not here.

Show full SKILL.md (590 more words)Show less

Diagnose & prescribe (this is where the flow branches)

Find the worst number, then route to the lever — and to the sibling skill that owns that lever.

Bad numberLikely causeLever (and owner)
CAC too highwrong channel mix / paid-heavyshift to founder-led & organic; cut the bleeding channel — diagnose by segment here, then pricing if the fix is monetization
Payback too longlow margin-dollar capture per monthmove to annual prepay; shorten free trial; lift gross margin (cost-tracking for COGS)
LTV too lowdominant churn termattack the biggest churn driver → retention; lift expansion to push NRR > 100%
Margin too lowCOGS per unit too highinstrument per-unit COGS / inference cost → cost-tracking
LTV:CAC > 5:1under-investing in growthspend more on acquisition — you're leaving money on the table, not winning
NRR ≫ GRRexpansion masking a churn problemfix gross retention first → retention; don't let expansion hide the leak

The skill stops at "here is the worst number and the lever." Executing the lever (set the price, design the save-play, project the new curve) belongs to the sibling, not here.

Conservatism rules (so LTV isn't fantasy)

Small churn errors explode LTV because of the 1/churn term — at 1% monthly churn the formula implies a ~100-month (8+ year) lifetime, which no early-stage company has data to claim.

  • Cap assumed lifetime at 3-4 years for early-stage (≤ 48 months), or apply a ×0.7 conservatism multiplier to formula LTV.
  • Cohort beats formula. Once you have multi-year retention data, compute cohort LTV from observed retention — the formula is a placeholder until then.
  • Discount future value in the advanced (Skok) model: ~20-25% discount rate pre-scale, ~10% at scale, because a dollar of contribution margin three years out is worth less than one today.
  • NRR > 100% means the simple churn-only LTV understates the cohort — note it rather than silently leaving value on the table.

(Beancount.io 2026-05-10; metrickit LTV guide; forEntrepreneurs SaaS Metrics 2.0; all accessed 2026-06-02.) Worked discounted and cohort examples are in references/formulas.md.

Anti-patterns

Anti-patternWhy it's wrongDo instead
Revenue LTV (ARPA ÷ churn)overstates value; not all revenue is profitgross-margin LTV: (ARPA × GM%) ÷ churn
Ad-spend-only CACunderstates true CAC ~3.5×fully-loaded S&M ÷ new customers
Monthly ARPA with annual churnsilently 12×'s or ÷12's the LTVmatch time units before dividing
Near-zero churn → 30-year lifetimefantasy LTV no one can back with datacap lifetime ≤ 48 mo or ×0.7 multiplier
One blended CAC/LTVhides self-serve vs field; nothing actionablesegment by go-to-motion first
Counting CS/retention spend in CACinflates CAC; that spend protects LTV, doesn't acquirekeep CS out of the numerator
Reading only the LTV:CAC ratioignores payback & NRR that decide survivabilityread payback + NRR alongside the ratio
Quoting NRR while GRR is weakexpansion masks a churn leakreport GRR floor too; fix retention first

The worksheet format

Emit this so the numbers are checkable, not just asserted:

yaml
# unit-economics.yaml
inputs:
  period_sm_spend: 120000      # fully-loaded S&M, this period
  new_customers: 80            # new logos only, same period
  monthly_arpa: 400
  gross_margin_pct: 0.75
  monthly_churn: 0.03          # monthly, to match monthly_arpa
  # lifetime_cap_override: 60  # only if you justify > 48 months
outputs:
  cac: 1500                    # 120000 / 80
  contribution_margin: 300     # 400 * 0.75
  ltv: 10000                   # (400 * 0.75) / 0.03   (NOT 13333)
  payback_months: 5            # 1500 / (400 * 0.75)
  ltv_cac: 6.67                # 10000 / 1500  -> >5: under-investing
segments:                      # split when blended hides the truth
  - name: self-serve
    cac: 80
  - name: field-sales
    cac: 40000

scripts/verify.sh parses this file and fails if: CAC ≠ spend ÷ new_customers; contribution_margin ≠ ARPA × GM%; payback ≠ CAC ÷ (ARPA × GM%); the stated LTV matches the revenue form instead of the gross-margin form; ltv_cac ≠ LTV ÷ CAC within 0.05; or implied lifetime (1/churn) > 48 months with no lifetime_cap_override. It is read-only and exits 0 on a clean worksheet (and on no worksheet at all).

Where this hands off

  • Multi-year P&L / scenario / cap-table model → financial-model.
  • Setting the actual price, tiers, discount floor → pricing.
  • Churn-prevention program (health scores, save-plays, win-back) → retention.
  • Per-unit COGS / infra / AI inference cost so gross margin is even knowable → cost-tracking.
  • Forecasting future MRR / cohort projection → forecasting.
  • Writing the investor unit-economics narrative / data-room exhibit → investor-materials.
  • Generic KPI chart / dashboard surface → dashboard.

© ericrisco, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 4 other files (scripts, references) in skills/unit-economics of ericrisco/rsc-harness.

  • SKILL.md
  • evals/README.md
  • evals/cases.yaml
  • references/formulas.md
  • scripts/verify.sh

Open the folder on GitHubat commit e3d5b33

Compare with similar skills

Unit Economics next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Unit Economics compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Unit Economics this skillericrisco/rsc-harness174—~3.2kAutomated safety check: PassMIT
Creating Financial ModelsChen-zexi/open-ptc-agent7293 repos~1.3kAutomated safety check: PassMIT
Equity ResearchrollingSirius/equity-research-skill453—~1.5kAutomated safety check: PassMIT
SaaS Metrics Coachrongxinzy/RongxinAI1542 repos~1.3kAutomated safety check: PassMIT
Startup Financial Modelingnicepkg/auto-company19411 repos~2.8kAutomated safety check: PassNone
Stock Value AnalyzerFunnyKun/stock-value-analyzer140—~3.3kAutomated safety check: PassNone

Similar skills

  • Creating Financial Models

    Chen-zexi/open-ptc-agent

    This skill provides an advanced financial modeling suite with DCF analysis, sensitivity testing, Monte Carlo simulations, and scenario planning for investment decisions

    729 GitHub starsUsed in 3 repos~1.3k tokens
    Business, Finance & HRAuto-check passed
  • Equity Research

    rollingSirius/equity-research-skill

    撰写机构级个股投资研究报告(二级市场深度研究)。Use whenever the user wants to research, analyze, or value a specific publicly-traded stock — e.g.

    453 GitHub stars~1.5k tokensUpdated 1 mo ago
    Business, Finance & HRAuto-check passed
  • SaaS Metrics Coach

    rongxinzy/RongxinAI

    SaaS financial health advisor. An agent skill from rongxinzy/RongxinAI.

    154 GitHub starsUsed in 2 repos~1.3k tokens
    Business, Finance & HRAuto-check passed
  • Startup Financial Modeling

    nicepkg/auto-company

    This skill should be used when the user asks to "create financial projections", "build a financial model", "forecast revenue", "calculate burn rate", "estimate runway", "model cash flow", or…

    194 GitHub starsUsed in 11 repos~2.8k tokens
    Business, Finance & HRAuto-check passed
  • Stock Value Analyzer

    FunnyKun/stock-value-analyzer

    基于邱国鹭《投资中最简单的事》方法论的股票价值分析器(v2.0 双层架构)。通过"三好原则"(好行业、好公司、好价格)系统评估一只股票是否值得投资。v2.0 在原定性框架之上注入一套可量化、可复现的硬模型层——反向 DCF 反解市场隐含增速、情景概率加权估值、EPV 盈利能力价值、分行业估值路由、杜邦三/五因子分解、ROIC vs WACC、Piotroski F-Score、Beneish…

    140 GitHub stars~3.3k tokensUpdated 3 mo ago
    Business, Finance & HRAuto-check passed
  • Dcf Valuation

    edinetdb/dexter-jp

    Performs discounted cash flow (DCF) valuation analysis to estimate intrinsic value per share for Japanese listed companies.

    311 GitHub stars~1.1k tokensUpdated today
    Business, Finance & HRAuto-check passed

More from ericrisco/rsc-harness

All 233 skills in this repo
  • Ab Testing

    ericrisco/rsc-harness

    A skill your agent uses when designing or analyzing a controlled experiment — falsifiable hypothesis, sample size from an MDE, reading significance/CI/power, CUPED, or rescuing tests that won't go…

    174 GitHub stars~2.4k tokensUpdated yesterday
    Auto-check passed
  • Accessibility

    ericrisco/rsc-harness

    A skill your agent uses when making a web UI conform to WCAG 2.2 Level AA — axe-core or Lighthouse a11y violations, keyboard operability, focus management, ARIA roles/names/live regions, contrast…

    174 GitHub stars~3.4k tokensUpdated yesterday
    Auto-check passed
  • Ads

    ericrisco/rsc-harness

    A skill your agent uses when running or fixing paid acquisition on Google or Meta — campaign structure (Performance Max, Demand Gen, Search, Advantage+), platform-fit creative, budget/scaling rules…

    174 GitHub stars~2.2k tokensUpdated yesterday
    Auto-check passed
  • Agent Eval

    ericrisco/rsc-harness

    A skill your agent uses when measuring whether an LLM or agent system actually got better and gating merges on it: golden sets, fixing an inflated LLM-as-judge, scoring RAG (faithfulness, contextual…

    174 GitHub stars~3.2k tokensUpdated yesterday
    Auto-check passed
  • AI Media

    ericrisco/rsc-harness

    A skill your agent uses when a creative goal must become a finished media file: pick and order generative-media models per modality — AI voiceover, image-to-video clips, score — then glue them with…

    174 GitHub stars~3.3k tokensUpdated yesterday
    Auto-check passed
  • Analytics

    ericrisco/rsc-harness

    A skill your agent uses when instrumenting product or web analytics — GA4/PostHog SDK wiring, event taxonomy, funnels, double-counted events, consent gating, PII scrubbing.

    174 GitHub stars~2.8k tokensUpdated yesterday
    Auto-check passed

Questions about Unit Economics

What does Unit Economics do?

A skill your agent uses when computing or improving the per-customer economics of a business — CAC, LTV, CAC payback period and contribution margin — judging whether the ratios are healthy against…. Unit Economics is an agent skill from ericrisco/rsc-harness. Use when computing or improving the per-customer economics of a business — CAC, LTV, CAC payback period and contribution margin — judging whether the ratios are healthy against current norms, and naming the one lever that fixes the worst number.

When should I use Unit Economics?

Unit Economics fits situations like: improving the per-customer economics of a business — CAC; CAC payback period and contribution margin — judging whether the ratios are healthy against current norms; naming the one lever that fixes the worst number.

How do I install Unit Economics in Claude Code?

Run `npx skills add ericrisco/rsc-harness --skill unit-economics -a claude-code`. Or copy the skill folder (skills/unit-economics in ericrisco/rsc-harness) into .claude/skills/unit-economics in your project. Claude Code loads it when a task matches its description.

How do I install Unit Economics in Codex?

Run `npx skills add ericrisco/rsc-harness --skill unit-economics -a codex`. Or copy the skill folder (skills/unit-economics in ericrisco/rsc-harness) into .agents/skills/unit-economics in your project. Codex loads it when a task matches its description.

Can I use Unit Economics in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add ericrisco/rsc-harness --skill unit-economics -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/unit-economics, .gemini/skills/unit-economics, .github/skills/unit-economics and .opencode/skills/unit-economics in your project.

What does Unit Economics need to run?

Going by SKILL.md and its folder, Unit Economics needs a shell for the scripts in its folder. Our summary lists: A Bash shell.

Does Unit Economics access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Unit Economics safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Unit Economics use?

Unit Economics is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Unit Economics use?

About 3.2k tokens (SKILL.md is roughly 13k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.4k tokens, read only when the agent opens those files.

What are the alternatives to Unit Economics?

Skills that share tags, products or a category with Unit Economics: Creating Financial Models (Chen-zexi/open-ptc-agent, 729 stars), Equity Research (rollingSirius/equity-research-skill, 453 stars), SaaS Metrics Coach (rongxinzy/RongxinAI, 154 stars) and Startup Financial Modeling (nicepkg/auto-company, 194 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Unit Economics?

ericrisco (a GitHub user) maintains it in ericrisco/rsc-harness, which has 174 GitHub stars. The repository holds 233 skills in this directory. The repository was last updated on October 7, 2026.

Source: ericrisco/rsc-harness on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.