financial-modeling
Skill1 starsChanged 9 months agoMITView on GitHub
Use after market-research to build a financial model with unit economics, revenue forecasts, and break-even analysis — requires run_id from idea-intake
8 other projects use a version of this.
Adopted by
Most recently taken up by
- nisarth/claude-skills-storetheir own version, first seen Nov 8, 2026
- anotb/management-consulting-plugintheir own version, first seen Nov 1, 2026
- KMaruthi2002/universal-llm-skillstheir own version, first seen Oct 25, 2026
- poorvith-mp/skills-financetheir own version, first seen Oct 11, 2026
- ZeroTokenClaw/agents-skillstheir own version, first seen Sep 21, 2026
- magnus919/agent-skillstheir own version, first seen Jul 21, 2026
Other versions8 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 8
- claude-office-skills/skills★ 433same name
- magnus919/agent-skills★ 172same name
- anotb/management-consulting-plugin★ 62same name
- claude-office-skills/claude-office-plugin★ 9same name
- KMaruthi2002/universal-llm-skills★ 1same name
- nisarth/claude-skills-store★ 1same name
- poorvith-mp/skills-finance★ 1same name
- ZeroTokenClaw/agents-skills★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository7 other files it gives its agents.
- brainstormingSkill
- competitor-analysisSkill
- idea-intakeSkill
- market-researchSkill
- report-generationSkill
- risk-assessmentSkill
- using-business-validatorSkill
The file
We split this skill into the rules it gives an agent
6 rules. 0 are common, 4 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 7 edited versions we read keep these.
4
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 53
Read all three input files using the exact run_id.
- Very specific: line 60
If the brief lacks detail, ask the user via AskUserQuestion:
- Distinctive: line 72
LTV/CAC ratio: Must be greater than 3 for viability
- Very specific: line 90
Ensure the output directory exists: mkdir -p docs/reports/<run_id>
- Distinctive: line 150
All numbers must show their assumptions
- Distinctive: line 151
Use industry benchmarks where available, cite sources
“Common” is measured: kept by at least 6 in 10 of the 7 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Financial Modeling
Overview
Build a basic financial model for a business idea based on the business brief and market research data. Includes unit economics, 3-scenario revenue forecast, cost structure, and break-even analysis.
<HARD-GATE>
You MUST have the run_id and read both the business brief AND the market research section before building the model. Financial projections without market data are guesswork. Required files:
- `docs/business-briefs/<run_id>.md`
- `docs/reports/<run_id>/01-market-research.md`
- `docs/reports/<run_id>/02-competitor-analysis.md` (for pricing benchmarks)
</HARD-GATE>Inputs
- run_id: From idea-intake (format:
YYYY-MM-DD-<slug>-<hhmm>) - Business brief:
docs/business-briefs/<run_id>.md - Market research:
docs/reports/<run_id>/01-market-research.md - Competitor analysis:
docs/reports/<run_id>/02-competitor-analysis.md
Output
- File:
docs/reports/<run_id>/03-financial-model.md
Process
digraph financial_modeling {
"Verify run_id and read inputs" [shape=box];
"Ask clarifying questions if needed" [shape=box];
"Calculate unit economics" [shape=box];
"Build cost structure" [shape=box];
"Create 3-scenario forecast" [shape=box];
"Calculate break-even" [shape=box];
"Write 03-financial-model.md" [shape=box, style=filled, fillcolor="#e8f5e9"];
"Verify run_id and read inputs" -> "Ask clarifying questions if needed";
"Ask clarifying questions if needed" -> "Calculate unit economics";
"Calculate unit economics" -> "Build cost structure";
"Build cost structure" -> "Create 3-scenario forecast";
"Create 3-scenario forecast" -> "Calculate break-even";
"Calculate break-even" -> "Write 03-financial-model.md";
}Step 1: Read Inputs
Read all three input files using the exact run_id. Extract:
- Target audience and willingness to pay (from brief)
- Market size and growth (from market research)
- Competitor pricing (from competitor analysis)
Step 2: Ask Clarifying Questions (if needed)
If the brief lacks detail, ask the user via AskUserQuestion:
- Expected average price point
- Main cost categories
- Team size at launch
- Customer acquisition channels
Step 3: Build the Model
Unit Economics
- CAC (Customer Acquisition Cost): Based on industry benchmarks + stated channels
- ARPU (Average Revenue Per User): Based on pricing model
- LTV (Lifetime Value): ARPU multiplied by average customer lifespan
- LTV/CAC ratio: Must be greater than 3 for viability
Cost Structure
- Fixed costs (team, infrastructure, tools)
- Variable costs (per-customer costs)
- One-time costs (development, legal, launch)
Revenue Forecast (3 scenarios, months 1-36)
- Pessimistic: Low acquisition, high churn
- Base: Industry-average metrics
- Optimistic: Strong product-market fit
Break-even Analysis
- Monthly fixed costs divided by (ARPU minus variable cost per customer)
- Months to break-even in each scenario
Step 4: Write Output
Ensure the output directory exists: mkdir -p docs/reports/<run_id>
Save to docs/reports/<run_id>/03-financial-model.md:
## Financial Model
**Run ID:** <run_id>
### Unit Economics
| Metric | Value | Assumption |
|--------|-------|------------|
| ARPU (Monthly) | $X | [basis] |
| CAC | $X | [basis] |
| LTV | $X | [calculation] |
| LTV/CAC | X.X | [interpretation] |
| Gross Margin | X% | [basis] |
### Cost Structure
| Category | Monthly Cost | Type |
|----------|-------------|------|
| Team | $X | Fixed |
| Infrastructure | $X | Fixed |
| Marketing | $X | Variable |
| [Other] | $X | [type] |
| **Total Fixed** | **$X** | |
| **Variable per Customer** | **$X** | |
### Revenue Forecast (36 months)
| Month | Pessimistic | Base | Optimistic |
|-------|-------------|------|------------|
| 3 | $X | $X | $X |
| 6 | $X | $X | $X |
| 12 | $X | $X | $X |
| 24 | $X | $X | $X |
| 36 | $X | $X | $X |
### Break-Even Analysis
| Scenario | Customers Needed | Months to Break-Even |
|----------|-----------------|---------------------|
| Pessimistic | X | X |
| Base | X | X |
| Optimistic | X | X |
### Key Assumptions
- [Assumption 1]
- [Assumption 2]
### Financial Health Indicators
- Burn rate: $X/month
- Runway (with stated budget): X months
- Funding gap (if any): $XQuality Standards
- All numbers must show their assumptions
- Use industry benchmarks where available, cite sources
- State uncertainty ranges for key assumptions
- Flag any metrics below healthy thresholds (e.g. LTV/CAC less than 3)
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
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.

