AB unit-economics
Calculate, understand, and improve the unit economics of a solopreneur business. Use when figuring out if the business is actually profitable per customer, when CAC or LTV numbers are needed, when evaluating whether a pricing or acquisition strategy is sustainable, or when making data-driven decisions about marketing spend and pricing. Covers CAC, LTV, payback period, contribution margin, and the feedback loops between them. Trigger on "unit economics", "CAC", "customer acquisition cost", "LTV", "lifetime value", "payback period", "is my business profitable", "contribution margin", "am I making money per customer", "should I spend more on marketing".
As a process B 66/100 · Nearly there — weak spots: result and completion, inputs and preconditions, progress reporting
How to improve
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 1. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 66/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 70When it triggers. States when to use, but not when not to
- 70Failures and branches. 7 branches
- 100Tools and files. No external tools needed
- 100Steps. 28 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2033 tokens
- 100Running it twice. No mutating operations
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +5Description quotes 8 example trigger phrases
- +3Description length 658: enough signal without eating the budget
- +4Structure: 16 headings
- +3Step-by-step instructions: 28 items
- +4Has examples (10 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 89.