[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79GJJC3HTQXVXEWNVCNZEWV":3,"skill-same:01M79GJJC3HTQXVXEWNVCNZEWV":51},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":29,"updatedAt":30,"install":31,"resources":44},"01M79GJJC3HTQXVXEWNVCNZEWV","unit-economics",null,"Bottoms-up unit economics decomposition for any public company","zfifteen\u002Fskills-catalog","zfifteen","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F221906715?v=4","01M79CQFXDZM5J5CJTCECPFA66","Dionisio Alberto Lopez III","01M79CQFY4C62PN8A2T5KDAHGA",1,"MIT","https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Funit-economics\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: unit-economics\ndescription: Bottoms-up unit economics decomposition for any public company\n---\n\nPerform a bottoms-up unit economics decomposition for the company named in the user's request. If no ticker or company is provided, ask for one before proceeding.\n\n**Before starting, read `..\u002Fdata-access.md` for data access methods and `..\u002Fdesign-system.md` for formatting conventions.** Follow the data access detection logic and design system throughout this skill.\n\nFollow these steps:\n\n## 1. Company Lookup\nLook up the company by ticker using `discover_companies`. Capture:\n- `company_id`\n- `latest_calendar_quarter` — anchor for all period calculations below (see `..\u002Fdata-access.md` Section 1.5)\n- `latest_fiscal_quarter`\n- Firm name for report attribution (default: \"Daloopa\") — see `..\u002Fdata-access.md` Section 4.5\n\n## 2. Series Discovery & Business Archetype Detection\nCast a wide net to discover ALL available series for this company. Search with multiple keyword sets to maximize coverage:\n- Financial: \"revenue\", \"income\", \"profit\", \"margin\", \"eps\", \"cost\"\n- Operating KPIs: \"subscriber\", \"user\", \"customer\", \"unit\", \"arpu\", \"retention\", \"churn\"\n- Segment\u002FProduct: \"segment\", \"product\", \"service\", \"geographic\"\n- Business-specific: \"store\", \"gmv\", \"order\", \"booking\", \"backlog\", \"premium\", \"loan\", \"aum\", \"room\", \"seat\", \"bed\", \"acreage\"\n\nCollect all unique series IDs. Read every series name and description returned. **This is how you learn what kind of business this is and what unit-level KPIs Daloopa tracks for it.**\n\nBased on series availability, classify the business into one of these archetypes (or a hybrid). This classification drives the entire report structure:\n\n| If you find series like... | Archetype | Unit = |\n|---|---|---|\n| ARR, MRR, net dollar retention, customers, ACV, churn, CAC, LTV | **SaaS \u002F Subscription** | Customer or subscription |\n| Store count, same-store sales, AUV, restaurant-level margin, new openings | **Unit-based retail \u002F Restaurant** | Store or unit |\n| GMV, take rate, orders, AOV, active buyers\u002Fsellers | **Marketplace \u002F E-commerce** | Order or transaction |\n| Subscribers, ARPU, churn, content spend per sub | **Consumer subscription (media\u002Fstreaming)** | Subscriber |\n| Premiums written, loss ratio, combined ratio, policies in force | **Insurance** | Policy |\n| NIM, loans, deposits, provision for credit losses, NCOs | **Banking \u002F Lending** | Loan or account |\n| ASP, units shipped, cost per unit, gross margin per unit | **Hardware \u002F Manufacturing** | Unit shipped |\n| AUM, management fee rate, performance fees, fund flows | **Asset Management** | Dollar of AUM |\n| Revenue per available room (RevPAR), occupancy, ADR | **Hospitality \u002F Lodging** | Room night |\n| RPM, RASM, CASM, load factor, ASMs | **Airlines \u002F Transportation** | Available seat mile |\n| Revenue per user, DAU, MAU, ARPU, engagement | **Digital platform \u002F Advertising** | User |\n| Beds, admissions, revenue per admission, case mix | **Healthcare facilities** | Admission or bed |\n| Acreage, production per acre, realized price per unit | **Commodity \u002F E&P** | Unit of production |\n\nIf the business is a hybrid or doesn't fit neatly, construct a custom framework from the available series. The archetype is a starting guide, not a constraint.\n\n**Edge cases:**\n- **Diversified \u002F multi-segment companies**: Pick the largest or most analytically interesting segment for primary analysis. Note other segments briefly. If the user specifies a segment, focus there.\n- **Pre-revenue \u002F early-stage companies**: Focus on burn rate per unit of growth, cash efficiency, and path to unit profitability.\n- **Financial companies (banks, insurance, asset managers)**: These have specialized unit economics. For banks, the \"unit\" is a dollar of assets — focus on NIM, fee income\u002Fassets, efficiency ratio, credit costs. For insurance, focus on the combined ratio decomposition. Don't force a SaaS or retail framework onto financials.\n- **Companies with no obvious unit-level KPIs in Daloopa**: Fall back to a margin bridge \u002F operating leverage analysis using standard income statement data. Decompose revenue into whatever sub-components are available (segment, geography, product line) and analyze profitability at that level. Note the limitation.\n- **Companies that stopped disclosing unit data**: Some major companies (e.g., Apple post-2018) no longer report unit shipments or ASPs. If unit-level data is not available, adapt to the highest-resolution decomposition the data supports (e.g., segment revenue × segment margin). Clearly flag the data gap and explain what proxy you used. Do not fabricate unit estimates.\n\n## 3. Unit Economics Data Pull\nCalculate 10 quarters backward from `latest_calendar_quarter`. Pull all archetype-relevant series identified in Step 2 for those periods, plus standard financials:\n- Revenue (total and segment)\n- COGS \u002F cost of revenue\n- Gross profit\n- Operating income\n- Net income\n- All operating KPIs relevant to the detected archetype\n\n**Derived metrics** (calculate from pulled data, label each as \"(calc.)\" and show formulas):\n- Revenue per unit (Revenue \u002F units)\n- Gross margin per unit\n- Contribution margin per unit (if variable costs are available)\n- Unit growth rate (QoQ and YoY)\n- Revenue per unit growth rate (QoQ and YoY)\n- Any archetype-specific derived metrics (e.g., CAC payback = CAC \u002F (ARPU × gross margin), LTV\u002FCAC, 4-wall margin, take rate, combined ratio)\n\n## 4. Qualitative Research\nSearch SEC filings for context on the unit economics. Use archetype-specific search terms:\n- **SaaS**: Try \"net dollar retention\", \"customer acquisition cost\"; fallback to \"expansion\", \"churn\", \"upsell\"\n- **Restaurant\u002FRetail**: Try \"average unit volume\", \"restaurant-level margin\"; fallback to \"same-store\", \"new unit\", \"unit opening\"\n- **Marketplace**: Try \"take rate\", \"gross merchandise value\"; fallback to \"active buyers\", \"order volume\", \"monetization\"\n- **Hardware\u002FManufacturing**: Try \"average selling price\", \"units shipped\"; fallback to \"ASP\", \"volume\", \"mix\"\n- **Insurance**: Try \"combined ratio\", \"loss ratio\"; fallback to \"underwriting\", \"premium\", \"policy\"\n- **Banking**: Try \"net interest margin\", \"provision\"; fallback to \"loan growth\", \"credit quality\", \"efficiency\"\n- **Digital platform**: Try \"average revenue per user\", \"monthly active users\"; fallback to \"engagement\", \"monetization\", \"ARPU\"\n- **General (all archetypes)**: Try \"unit economics\", \"pricing\"; fallback to \"profitability\", \"margin\", \"per unit\"\n\nExtract management commentary on pricing, retention, expansion, new unit openings, margin levers, etc. with document citations.\n\n## 5. Analysis & Report Synthesis\n\n**Section 1: Business Model & Unit Definition (brief)**\n- 2-3 sentence description of what the \"unit\" is for this business\n- Why this decomposition matters for understanding the company's economics\n- What the revenue build-up looks like: units × revenue-per-unit, or equivalent\n\n**Section 2: Revenue Decomposition**\n- Show the bottoms-up revenue build: how units × price\u002Frate × utilization (or equivalent) bridges to reported revenue\n- Table: quarterly history (10 quarters) showing each component\n- Highlight which lever is driving growth: volume vs. price vs. mix\n- Include growth rates (YoY) as sub-rows beneath each metric\n\n**Section 3: Unit-Level Profitability**\nThe core of the report. Show margin\u002Fprofitability at the unit level over time:\n- For SaaS: gross margin per customer, CAC payback period, LTV\u002FCAC ratio\n- For restaurants: 4-wall EBITDA margin, new unit payback, cash-on-cash return\n- For marketplace: contribution margin per order, after accounting for fulfillment\u002Ftransaction costs\n- For insurance: loss ratio + expense ratio = combined ratio per policy\n- For hardware: gross margin per unit, cost per unit breakdown\n- Adapt to whatever the business actually is\n- Table: historical trend with period-over-period change\n- Explicitly call out whether unit economics are improving or deteriorating and by how much\n\n**Section 4: Cohort \u002F Vintage Analysis (if data supports it)**\n- For subscription businesses: net retention curves, expansion vs. contraction\n- For unit-based businesses: same-store vs. new-store contribution, unit maturation\n- For lending: vintage loss curves, seasoning\n- If insufficient data for true cohort analysis, note this and substitute with proxy analysis (e.g., new customer growth rate vs. retention rate implies cohort behavior)\n\n**Section 5: Scalability & Operating Leverage**\n- How do unit economics change as the business scales?\n- Fixed cost absorption: which costs are truly fixed vs. variable per unit?\n- Show operating leverage by plotting revenue growth vs. cost growth\n- Incremental margins: are they expanding or compressing as the business grows?\n\n**Section 6: Key Drivers & What to Watch**\nThis is the most analytically valuable section. Based on the data, identify:\n- **The 3-5 metrics that matter most** for this company's unit economics, ranked by sensitivity \u002F impact\n- For each metric: current level, historical range, direction of travel, and what would cause it to inflect\n- **Bull case drivers**: what would improve unit economics (e.g., pricing power, mix shift to higher-margin products, operating leverage kicking in, retention improving)\n- **Bear case risks**: what would deteriorate unit economics (e.g., competitive pricing pressure, rising CAC, input cost inflation, regulatory impact on take rates)\n- Connect each driver to its P&L impact: \"a 100bps improvement in net retention would add ~$X to ARR\" or \"each new store generates ~$Xm in 4-wall EBITDA in year 2\"\n\n**Section 7: Summary Assessment**\n- 3-4 sentence verdict on the health and trajectory of the company's unit economics\n- Is this a business with improving, stable, or deteriorating unit economics?\n- What is the single most important thing to monitor going forward?\n\n**Analytical standards:**\n- **Three-layer density**: every data point should have context (vs. prior period, vs. peers if known) and an implication (what it means for the investment case)\n- **Show your math**: when you derive a metric (e.g., implied CAC = S&M expense \u002F new customers added), show the calculation explicitly so the reader can verify\n- **Flag data gaps**: if a key metric for the archetype isn't available in Daloopa's data, say so explicitly and explain what proxy you used or why the analysis is limited\n- **No generic filler**: if you don't have data to support a section, skip it or shorten it. Never pad with boilerplate\n- **Source everything**: every number should be traceable. Use Daloopa source citations per the design system conventions\n- **Prefer rates and ratios over absolutes**: unit economics are about efficiency, not scale. Lead with margins, returns, and per-unit metrics. Include absolutes as context\n\n## 6. Charts\nUse `infra\u002Fchart_generator.py` for charts. Include at minimum:\n1. A **revenue decomposition chart** (waterfall or time-series showing units × price → revenue)\n2. A **unit profitability trend chart** (time-series showing the key unit margin metric over time)\n3. Additional charts as warranted by the archetype (e.g., net retention waterfall for SaaS, same-store sales trend for restaurants, take rate trend for marketplaces)\n\n**All charts must be embedded in the HTML as base64 data URIs** (e.g., `\u003Cimg src=\"data:image\u002Fpng;base64,...\">`) so the report is fully self-contained with no external file dependencies. After generating each chart PNG, read the file and convert to base64 for embedding. Do not use relative `\u003Cimg src=\"filename.png\">` paths.\n\nIf chart_generator.py is unavailable, embed simple inline SVG charts directly in the HTML.\n\n## 7. Save Report\nSave to `reports\u002F{TICKER}_unit_economics.html` using the HTML report template from `..\u002Fdesign-system.md`. Write the full analysis as styled HTML with the design system CSS inlined. This is the final deliverable — no intermediate markdown step needed.\n\nStructure the report with these sections:\n\n```\n\u003Ch1>{Company Name} ({TICKER}) — Unit Economics Analysis\u003C\u002Fh1>\n\u003Cp>Generated: {date}\u003C\u002Fp>\n\n\u003Ch2>Summary\u003C\u002Fh2>\n{2-3 sentences: What is the \"unit\"? Are unit economics improving or deteriorating? Key takeaway.}\n\n\u003Ch2>Business Model & Unit Definition\u003C\u002Fh2>\n{Section 1 content}\n\n\u003Ch2>Revenue Decomposition\u003C\u002Fh2>\n\u003Ctable>\n| Component | Q(-9) | Q(-8) | ... | Q(latest) |\n{Units, revenue per unit, revenue — with Daloopa citations and YoY growth sub-rows}\n\u003C\u002Ftable>\n{Commentary on volume vs. price drivers}\n\n\u003Ch2>Unit-Level Profitability\u003C\u002Fh2>\n\u003Ctable>\n| Metric | Q(-9) | Q(-8) | ... | Q(latest) |\n{Archetype-specific unit margins — with Daloopa citations}\n\u003C\u002Ftable>\n{Commentary on unit economics trajectory}\n\n\u003Ch2>Cohort \u002F Vintage Analysis\u003C\u002Fh2>\n{Section 4 content, or note if insufficient data}\n\n\u003Ch2>Scalability & Operating Leverage\u003C\u002Fh2>\n\u003Ctable>\n| Metric | Q(-9) | Q(-8) | ... | Q(latest) |\n{Revenue growth vs cost growth, incremental margins}\n\u003C\u002Ftable>\n{Operating leverage assessment}\n\n\u003Ch2>Key Drivers & What to Watch\u003C\u002Fh2>\n{Ranked drivers with sensitivity analysis and bull\u002Fbear scenarios}\n\n\u003Ch2>Summary Assessment\u003C\u002Fh2>\n{3-4 sentence verdict}\n```\n\nAll financial figures must use Daloopa citation format: `\u003Ca href=\"https:\u002F\u002Fdaloopa.com\u002Fsrc\u002F{fundamental_id}\">$X.XX million\u003C\u002Fa>`\n\nTell the user where the HTML report was saved.\n\nHighlight the 2-3 most important findings about the company's unit economics and what they signal for the investment case.\n","Perform a bottoms-up unit economics decomposition for the company named in the user's request. If no ticker or company is provided, ask for one before proceeding.\n\n**Before starting, read `..\u002Fdata-access.md` for data access methods and `..\u002Fdesign-system.md` for formatting conventions.** Follow the data access detection logic and design system throughout this skill.\n\nFollow these steps:\n\n## 1. Company Lookup\nLook up the company by ticker using `discover_companies`. Capture:\n- `company_id`\n- `latest_calendar_quarter` — anchor for all period calculations below (see `..\u002Fdata-access.md` Section 1.5)\n- `latest_fiscal_quarter`\n- Firm name for report attribution (default: \"Daloopa\") — see `..\u002Fdata-access.md` Section 4.5\n\n## 2. Series Discovery & Business Archetype Detection\nCast a wide net to discover ALL available series for this company. Search with multiple keyword sets to maximize coverage:\n- Financial: \"revenue\", \"income\", \"profit\", \"margin\", \"eps\", \"cost\"\n- Operating KPIs: \"subscriber\", \"user\", \"customer\", \"unit\", \"arpu\", \"retention\", \"churn\"\n- Segment\u002FProduct: \"segment\", \"product\", \"service\", \"geographic\"\n- Business-specific: \"store\", \"gmv\", \"order\", \"booking\", \"backlog\", \"premium\", \"loan\", \"aum\", \"room\", \"seat\", \"bed\", \"acreage\"\n\nCollect all unique series IDs. Read every series name and description returned. **This is how you learn what kind of business this is and what unit-level KPIs Daloopa tracks for it.**\n\nBased on series availability, classify the business into one of these archetypes (or a hybrid). This classification drives the entire report structure:\n\n| If you find series like... | Archetype | Unit = |\n|---|---|---|\n| ARR, MRR, net dollar retention, customers, ACV, churn, CAC, LTV | **SaaS \u002F Subscription** | Customer or subscription |\n| Store count, same-store sales, AUV, restaurant-level margin, new openings | **Unit-based retail \u002F Restaurant** | Store or unit |\n| GMV, take rate, orders, AOV, active buyers\u002Fsellers | **Marketplace \u002F E-commerce** | Order or transaction |\n| Subscribers, ARPU, churn, content spend per sub | **Consumer subscription (media\u002Fstreaming)** | Subscriber |\n| Premiums written, loss ratio, combined ratio, policies in force | **Insurance** | Policy |\n| NIM, loans, deposits, provision for credit losses, NCOs | **Banking \u002F Lending** | Loan or account |\n| ASP, units shipped, cost per unit, gross margin per unit | **Hardware \u002F Manufacturing** | Unit shipped |\n| AUM, management fee rate, performance fees, fund flows | **Asset Management** | Dollar of AUM |\n| Revenue per available room (RevPAR), occupancy, ADR | **Hospitality \u002F Lodging** | Room night |\n| RPM, RASM, CASM, load factor, ASMs | **Airlines \u002F Transportation** | Available seat mile |\n| Revenue per user, DAU, MAU, ARPU, engagement | **Digital platform \u002F Advertising** | User |\n| Beds, admissions, revenue per admission, case mix | **Healthcare facilities** | Admission or bed |\n| Acreage, production per acre, realized price per unit | **Commodity \u002F E&P** | Unit of production |\n\nIf the business is a hybrid or doesn't fit neatly, construct a custom framework from the available series. The archetype is a starting guide, not a constraint.\n\n**Edge cases:**\n- **Diversified \u002F multi-segment companies**: Pick the largest or most analytically interesting segment for primary analysis. Note other segments briefly. If the user specifies a segment, focus there.\n- **Pre-revenue \u002F early-stage companies**: Focus on burn rate per unit of growth, cash efficiency, and path to unit profitability.\n- **Financial companies (banks, insurance, asset managers)**: These have specialized unit economics. For banks, the \"unit\" is a dollar of assets — focus on NIM, fee income\u002Fassets, efficiency ratio, credit costs. For insurance, focus on the combined ratio decomposition. Don't force a SaaS or retail framework onto financials.\n- **Companies with no obvious unit-level KPIs in Daloopa**: Fall back to a margin bridge \u002F operating leverage analysis using standard income statement data. Decompose revenue into whatever sub-components are available (segment, geography, product line) and analyze profitability at that level. Note the limitation.\n- **Companies that stopped disclosing unit data**: Some major companies (e.g., Apple post-2018) no longer report unit shipments or ASPs. If unit-level data is not available, adapt to the highest-resolution decomposition the data supports (e.g., segment revenue × segment margin). Clearly flag the data gap and explain what proxy you used. Do not fabricate unit estimates.\n\n## 3. Unit Economics Data Pull\nCalculate 10 quarters backward from `latest_calendar_quarter`. Pull all archetype-relevant series identified in Step 2 for those periods, plus standard financials:\n- Revenue (total and segment)\n- COGS \u002F cost of revenue\n- Gross profit\n- Operating income\n- Net income\n- All operating KPIs relevant to the detected archetype\n\n**Derived metrics** (calculate from pulled data, label each as \"(calc.)\" and show formulas):\n- Revenue per unit (Revenue \u002F units)\n- Gross margin per unit\n- Contribution margin per unit (if variable costs are available)\n- Unit growth rate (QoQ and YoY)\n- Revenue per unit growth rate (QoQ and YoY)\n- Any archetype-specific derived metrics (e.g., CAC payback = CAC \u002F (ARPU × gross margin), LTV\u002FCAC, 4-wall margin, take rate, combined ratio)\n\n## 4. Qualitative Research\nSearch SEC filings for context on the unit economics. Use archetype-specific search terms:\n- **SaaS**: Try \"net dollar retention\", \"customer acquisition cost\"; fallback to \"expansion\", \"churn\", \"upsell\"\n- **Restaurant\u002FRetail**: Try \"average unit volume\", \"restaurant-level margin\"; fallback to \"same-store\", \"new unit\", \"unit opening\"\n- **Marketplace**: Try \"take rate\", \"gross merchandise value\"; fallback to \"active buyers\", \"order volume\", \"monetization\"\n- **Hardware\u002FManufacturing**: Try \"average selling price\", \"units shipped\"; fallback to \"ASP\", \"volume\", \"mix\"\n- **Insurance**: Try \"combined ratio\", \"loss ratio\"; fallback to \"underwriting\", \"premium\", \"policy\"\n- **Banking**: Try \"net interest margin\", \"provision\"; fallback to \"loan growth\", \"credit quality\", \"efficiency\"\n- **Digital platform**: Try \"average revenue per user\", \"monthly active users\"; fallback to \"engagement\", \"monetization\", \"ARPU\"\n- **General (all archetypes)**: Try \"unit economics\", \"pricing\"; fallback to \"profitability\", \"margin\", \"per unit\"\n\nExtract management commentary on pricing, retention, expansion, new unit openings, margin levers, etc. with document citations.\n\n## 5. Analysis & Report Synthesis\n\n**Section 1: Business Model & Unit Definition (brief)**\n- 2-3 sentence description of what the \"unit\" is for this business\n- Why this decomposition matters for understanding the company's economics\n- What the revenue build-up looks like: units × revenue-per-unit, or equivalent\n\n**Section 2: Revenue Decomposition**\n- Show the bottoms-up revenue build: how units × price\u002Frate × utilization (or equivalent) bridges to reported revenue\n- Table: quarterly history (10 quarters) showing each component\n- Highlight which lever is driving growth: volume vs. price vs. mix\n- Include growth rates (YoY) as sub-rows beneath each metric\n\n**Section 3: Unit-Level Profitability**\nThe core of the report. Show margin\u002Fprofitability at the unit level over time:\n- For SaaS: gross margin per customer, CAC payback period, LTV\u002FCAC ratio\n- For restaurants: 4-wall EBITDA margin, new unit payback, cash-on-cash return\n- For marketplace: contribution margin per order, after accounting for fulfillment\u002Ftransaction costs\n- For insurance: loss ratio + expense ratio = combined ratio per policy\n- For hardware: gross margin per unit, cost per unit breakdown\n- Adapt to whatever the business actually is\n- Table: historical trend with period-over-period change\n- Explicitly call out whether unit economics are improving or deteriorating and by how much\n\n**Section 4: Cohort \u002F Vintage Analysis (if data supports it)**\n- For subscription businesses: net retention curves, expansion vs. contraction\n- For unit-based businesses: same-store vs. new-store contribution, unit maturation\n- For lending: vintage loss curves, seasoning\n- If insufficient data for true cohort analysis, note this and substitute with proxy analysis (e.g., new customer growth rate vs. retention rate implies cohort behavior)\n\n**Section 5: Scalability & Operating Leverage**\n- How do unit economics change as the business scales?\n- Fixed cost absorption: which costs are truly fixed vs. variable per unit?\n- Show operating leverage by plotting revenue growth vs. cost growth\n- Incremental margins: are they expanding or compressing as the business grows?\n\n**Section 6: Key Drivers & What to Watch**\nThis is the most analytically valuable section. Based on the data, identify:\n- **The 3-5 metrics that matter most** for this company's unit economics, ranked by sensitivity \u002F impact\n- For each metric: current level, historical range, direction of travel, and what would cause it to inflect\n- **Bull case drivers**: what would improve unit economics (e.g., pricing power, mix shift to higher-margin products, operating leverage kicking in, retention improving)\n- **Bear case risks**: what would deteriorate unit economics (e.g., competitive pricing pressure, rising CAC, input cost inflation, regulatory impact on take rates)\n- Connect each driver to its P&L impact: \"a 100bps improvement in net retention would add ~$X to ARR\" or \"each new store generates ~$Xm in 4-wall EBITDA in year 2\"\n\n**Section 7: Summary Assessment**\n- 3-4 sentence verdict on the health and trajectory of the company's unit economics\n- Is this a business with improving, stable, or deteriorating unit economics?\n- What is the single most important thing to monitor going forward?\n\n**Analytical standards:**\n- **Three-layer density**: every data point should have context (vs. prior period, vs. peers if known) and an implication (what it means for the investment case)\n- **Show your math**: when you derive a metric (e.g., implied CAC = S&M expense \u002F new customers added), show the calculation explicitly so the reader can verify\n- **Flag data gaps**: if a key metric for the archetype isn't available in Daloopa's data, say so explicitly and explain what proxy you used or why the analysis is limited\n- **No generic filler**: if you don't have data to support a section, skip it or shorten it. Never pad with boilerplate\n- **Source everything**: every number should be traceable. Use Daloopa source citations per the design system conventions\n- **Prefer rates and ratios over absolutes**: unit economics are about efficiency, not scale. Lead with margins, returns, and per-unit metrics. Include absolutes as context\n\n## 6. Charts\nUse `infra\u002Fchart_generator.py` for charts. Include at minimum:\n1. A **revenue decomposition chart** (waterfall or time-series showing units × price → revenue)\n2. A **unit profitability trend chart** (time-series showing the key unit margin metric over time)\n3. Additional charts as warranted by the archetype (e.g., net retention waterfall for SaaS, same-store sales trend for restaurants, take rate trend for marketplaces)\n\n**All charts must be embedded in the HTML as base64 data URIs** (e.g., `\u003Cimg src=\"data:image\u002Fpng;base64,...\">`) so the report is fully self-contained with no external file dependencies. After generating each chart PNG, read the file and convert to base64 for embedding. Do not use relative `\u003Cimg src=\"filename.png\">` paths.\n\nIf chart_generator.py is unavailable, embed simple inline SVG charts directly in the HTML.\n\n## 7. Save Report\nSave to `reports\u002F{TICKER}_unit_economics.html` using the HTML report template from `..\u002Fdesign-system.md`. Write the full analysis as styled HTML with the design system CSS inlined. This is the final deliverable — no intermediate markdown step needed.\n\nStructure the report with these sections:\n\n```\n\u003Ch1>{Company Name} ({TICKER}) — Unit Economics Analysis\u003C\u002Fh1>\n\u003Cp>Generated: {date}\u003C\u002Fp>\n\n\u003Ch2>Summary\u003C\u002Fh2>\n{2-3 sentences: What is the \"unit\"? Are unit economics improving or deteriorating? Key takeaway.}\n\n\u003Ch2>Business Model & Unit Definition\u003C\u002Fh2>\n{Section 1 content}\n\n\u003Ch2>Revenue Decomposition\u003C\u002Fh2>\n\u003Ctable>\n| Component | Q(-9) | Q(-8) | ... | Q(latest) |\n{Units, revenue per unit, revenue — with Daloopa citations and YoY growth sub-rows}\n\u003C\u002Ftable>\n{Commentary on volume vs. price drivers}\n\n\u003Ch2>Unit-Level Profitability\u003C\u002Fh2>\n\u003Ctable>\n| Metric | Q(-9) | Q(-8) | ... | Q(latest) |\n{Archetype-specific unit margins — with Daloopa citations}\n\u003C\u002Ftable>\n{Commentary on unit economics trajectory}\n\n\u003Ch2>Cohort \u002F Vintage Analysis\u003C\u002Fh2>\n{Section 4 content, or note if insufficient data}\n\n\u003Ch2>Scalability & Operating Leverage\u003C\u002Fh2>\n\u003Ctable>\n| Metric | Q(-9) | Q(-8) | ... | Q(latest) |\n{Revenue growth vs cost growth, incremental margins}\n\u003C\u002Ftable>\n{Operating leverage assessment}\n\n\u003Ch2>Key Drivers & What to Watch\u003C\u002Fh2>\n{Ranked drivers with sensitivity analysis and bull\u002Fbear scenarios}\n\n\u003Ch2>Summary Assessment\u003C\u002Fh2>\n{3-4 sentence verdict}\n```\n\nAll financial figures must use Daloopa citation format: `\u003Ca href=\"https:\u002F\u002Fdaloopa.com\u002Fsrc\u002F{fundamental_id}\">$X.XX million\u003C\u002Fa>`\n\nTell the user where the HTML report was saved.\n\nHighlight the 2-3 most important findings about the company's unit economics and what they signal for the investment case.\n",{"name":5,"description":7},"main","d9535210da9af28aa76bca80de80355197e1b6d6","skills\u002Funit-economics","https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog","https:\u002F\u002Fgithub.com\u002Fzfifteen","I like to measure things.","2026-07-19 23:41:54",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add zfifteen\u002Fskills-catalog --skill unit-economics",{"tool":37,"command":38},"bunx","bunx skills add zfifteen\u002Fskills-catalog --skill unit-economics",{"tool":40,"command":41},"pnpm","pnpm dlx skills add zfifteen\u002Fskills-catalog --skill unit-economics","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Funit-economics\u002FSKILL.md",true,[45],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"agents\u002Fopenai.yaml","REFERENCE","参考文档",219,"https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Funit-economics\u002Fagents\u002Fopenai.yaml",[52,59,66,73,82,89],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":19},"01M79GXQ2PWPT2E4CJYHXVJ0YE","Zotero","Use Zotero Desktop from Codex to enable\u002Fprobe the local API, search a local Zotero library, list items\u002Fcollections\u002Ftags, export BibTeX, insert citation keys into LaTeX or Markdown drafts, read indexed full text when requested, and import BibTeX\u002FRIS records into Zotero through the connector server. Use when the user mentions Zotero, citations, references.bib, BibTeX export, local Zotero API, localhost:23119, or adding citations from a Zotero library.","https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fzotero\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":19},"01M79GXN85NETKBE06865CWK6Z","zoom-apps-sdk","Use when using Apps SDK.","https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fzoom-apps-sdk\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":19},"01M79GXCYD7FGYS932J9N9RFFY","youtube","Obtain accurate, timestamped YouTube video transcripts (preferring manual captions over auto-generated) as the primary deliverable, then derive summaries, key claims, or notes from that transcript.  Use when the user provides a YouTube URL (or video ID) and wants the transcript, a faithful summary, key claims with attribution, timestamped notes, or \"what does this video actually say\".  The skill is transcript-first: never substitute metadata, title, description, or search snippets for the spoken content.  Triggers: \"youtube transcript\", \"get the transcript of this video\", \"summarize this youtube video\", \"what did they say in https:\u002F\u002Fyoutube.com\u002F...\", \"key claims from this talk\".","https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fyoutube\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":77,"licenseFileUrl":78,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M79GX8EXHHYM566BKR7MS778","yeet","Publish local changes to GitHub by confirming scope, committing intentionally, pushing the branch, and opening a draft PR through the GitHub app from this plugin, with `gh` used only as a fallback where connector coverage is insufficient.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fyeet\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fyeet\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M79GX2HFJPX84NMRE5VBTYX9","x-post-creator","Create X-ready post threads and co-located story packages from the active conversation or referenced project material. Use when the user says turn this into an X-post, \u002Fx-post, make this into an X thread, or wants plain-language social posts with supporting images saved to docs\u002Fx-posts\u002F[story-name]\u002F.","https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fx-post-creator\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":19},"01M79GWXQT4HBT6QME6QSBZJFA","x-api","Search, read, and write X posts through the local X API MCP server (the same backend used by the Codex x-api skill). Use for searching X\u002Fx.com, reading threads and replies, creating lists, staging\u002Fpublishing posts for @alltheputs, finding high-visibility reply targets for research outreach, ingesting public context, or any request that mentions \u002Fx-api or \"search X\".","https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fx-api\u002FSKILL.md",[],[]]