AC revenue-model-design
Design a revenue model for a solopreneur business — how money flows in, from whom, and on what cadence. Use when deciding how to monetize a product or service, choosing between revenue streams, structuring recurring vs one-time income, or diversifying revenue. Covers all major revenue model types, selection criteria, revenue stream stacking, and the relationship between revenue model and product design. Trigger on "how will I make money", "revenue model", "monetization strategy", "revenue streams", "recurring revenue", "how to monetize", "business revenue model", "diversify income".
Design a revenue model for a solopreneur business — how money flows in, from whom, and on what cadence.
As a process C 57/100 · Has gaps — weak spots: result and completion, inputs and preconditions, failures and branches
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 57/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 3 mutating operations with no state check
- 70When it triggers. States when to use, but not when not to
- 100Tools and files. No external tools needed
- 100Steps. 42 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2255 tokens
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
- -5TODO / placeholder text left in the skill
- +1No license
- +2Single-language instructions
- +5Description quotes 8 example trigger phrases
- +3Description length 589: enough signal without eating the budget
- +4Structure: 13 headings
- +3Step-by-step instructions: 42 items
- +4Has examples (2 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 84.