unit-economics

Bottoms-up unit economics decomposition for any public company

Quality

63%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./plugins/daloopa/skills/unit-economics/SKILL.md

Quality

Content

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a strong, highly actionable multi-step skill with clear sequencing and concrete guidance throughout. Its main weakness is progressive disclosure: the large archetype tables and search-term appendices are inlined in SKILL.md rather than split into clearly signaled reference files.

Suggestions

Move the business-archetype table and the per-archetype qualitative search terms into a reference file (e.g., references/archetypes.md) and link to it one level deep, keeping SKILL.md as a concise overview.

Tighten the report HTML skeleton in Section 7 — the duplicate section listing (prose Sections 1-7 then the HTML block) adds length without new information.

Consider extracting the derived-metric formulas into a short reference so the main workflow stays lean.

Dimension	Reasoning	Score
Conciseness	The body is lean and avoids explaining concepts Claude already knows, but at ~200 lines it inlines large reference material (the archetype table, per-archetype qualitative search terms, and a full report skeleton) that could be tightened or split out.	2 / 3
Actionability	Guidance is concrete and executable throughout: specific series keyword sets, named functions (discover_companies), explicit derived-metric formulas (CAC payback = CAC / (ARPU x gross margin)), file paths, and citation formats.	3 / 3
Workflow Clarity	A clearly sequenced 7-step process with explicit fallbacks (chart_generator.py unavailable -> inline SVG; no unit KPIs -> margin bridge) and analytical standards; the task is non-destructive so the absence of a validation loop is not penalizing.	3 / 3
Progressive Disclosure	Well organized into numbered sections, but the skill is a single monolithic ~200-line file with no bundle references; the archetype table and per-archetype search-term lists are content that could be split into one-level-deep reference files.	2 / 3
	Total	10 / 12 Passed

Description

50%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description names a specific analytical domain and action but is too terse to fully answer 'when should Claude use this'. Adding an explicit 'Use when...' trigger clause and a few more concrete capability verbs would lift it across all dimensions.

Suggestions

Add an explicit trigger clause, e.g. 'Use when analyzing a public company's per-unit profitability, revenue build, or unit-level margins (e.g., ARPU, LTV/CAC, same-store sales, take rate).'

List 2-3 concrete actions beyond 'decomposition' — e.g., 'decomposes revenue into units x price, computes per-unit margins, and benchmarks operating leverage'.

Include natural user phrasings like 'per-unit economics', 'unit profitability', or 'revenue bridge' to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain ('unit economics') and one concrete action ('bottoms-up ... decomposition') for 'any public company', but it is a single action rather than a comprehensive list of specific capabilities.	2 / 3
Completeness	States what the skill does ('bottoms-up unit economics decomposition for any public company') but gives no explicit 'Use when...' guidance; per the guidelines a missing trigger clause caps completeness at 2.	2 / 3
Trigger Term Quality	Includes relevant terms like 'unit economics' and 'public company', but omits common phrasings a user would naturally say (e.g., 'per-unit margins', 'LTV/CAC', 'revenue decomposition') and has no natural trigger clause.	2 / 3
Distinctiveness Conflict Risk	The unit-economics framing is a fairly distinct niche, but 'decomposition for any public company' could still overlap with broader financial-analysis skills and lacks distinct triggers to disambiguate.	2 / 3
	Total	8 / 12 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: openai/plugins
Path: plugins/daloopa/skills/unit-economics/SKILL.md
Commit: 11c74d6

Reviewed: 6 days ago

Table of Contents

Discovery Implementation Validation

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.