AC momentum-and-form
Activate when: user says 'we have a better product but we're losing,' 'they're growing despite less funding,' 'our moat isn't protecting us,' 'the market shifted under us,' 'we just need to hire harder,' or is diagnosing why strong incumbents lose to weaker newcomers, evaluating a market entry, or asking whether a strategy depends too much on specific people. Do NOT activate when: the decision is purely tactical (not strategic), or the context is cooperative/ethical leadership where 'winning configurationally' is the wrong frame. More: deciqai.com/c/momentum-and-form
Activate when: user says 'we have a better product but we're losing,' 'they're growing despite less funding,' 'our moat isn't protecting us,' 'the market…
As a process C 62/100 · Has gaps — weak spots: when it triggers, 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: 4. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- note
edit-residuethe text marks something as outdated (lines 44, 65, 70, 82): check that old rules are not kept next to new ones — the full check reads the text for contradictions
Process rating: all ten parameters 62/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
- 20When it triggers. No condition that starts the skill
- 60Result and completion. Output format stated, no completion criterion
- 100Tools and files. No external tools needed
- 100Steps. 38 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2064 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
- +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 573: enough signal without eating the budget
- +4Structure: 10 headings
- +3Step-by-step instructions: 38 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.