AB point-line-plane-solid
Activate when: user says 'we're good at X but not growing,' 'we need a moat,' 'we're just a feature not a platform,' 'competition keeps copying us,' 'we want to build something hard to replicate,' or asks how to move from product to platform to ecosystem. Do NOT activate when: the user is still searching for product-market fit (the point-level value hasn't been validated yet); or when the question is purely about execution speed or cost within an existing market (a line-level optimization, not a dimension problem). More: deciqai.com/c/point-line-plane-solid
Activate when: user says 'we're good at X but not growing,' 'we need a moat,' 'we're just a feature not a platform,' 'competition keeps copying us,' 'we want…
As a process B 67/100 · Nearly there — weak spots: when it triggers, failures and branches, running it twice
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: 4. 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 67/100
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 5 mutating operations with no state check
- 60Result and completion. Output format stated, no completion criterion
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Tools and files. No external tools needed
- 100Steps. 39 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2503 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
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +1No license
- +2Single-language instructions
- +3Description length 563: enough signal without eating the budget
- +4Structure: 11 headings
- +3Step-by-step instructions: 39 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: 91.