AB pmf-crossing-the-chasm
Activate when: user says "PMF," "product-market fit," "crossing the chasm," "early adopter to mainstream," "whole product," "we're stuck after our beachhead," or "growth stalled after an initial good period"; startup has early traction but can't tell if it's real; team is debating which segment to target next after winning early fans. Do NOT activate when: the product has no users yet (use lean-startup instead); the business is already category-mature and the question is about scaling proven channels. More: deciqai.com/c/pmf-crossing-the-chasm
Activate when: user says "PMF," "product-market fit," "crossing the chasm," "early adopter to mainstream," "whole product," "we're stuck after our beachhead,"…
As a process B 71/100 · Nearly there — weak spots: inputs and preconditions, failures and branches, 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: 5. 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 71/100
- 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
- 60Result and completion. Output format stated, no completion criterion
- 100Tools and files. No external tools needed
- 100Steps. 22 steps
- 100When it triggers. States when to use and when not to
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1811 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
- +1No license
- +2Single-language instructions
- +5Description quotes 6 example trigger phrases
- +4Description says when NOT to use the skill
- +3Description length 549: enough signal without eating the budget
- +4Structure: 13 headings
- +3Step-by-step instructions: 22 items
- +3Output format is stated explicitly
- +4Has examples (1 code blocks)
- +4Reference files are cited in the instructions (1 of 1)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 100.