AB anchoring
Activate when: user says 'what's a fair price / starting number / ballpark'; counterparty just opened with a number; user is about to negotiate salary, valuation, or deal terms; user is making a forecast and a number has already been floated; user asks about 'first offer', 'framing effect', or 'being anchored'. Do NOT activate when: the number in question is a verifiable data point (audited financials, confirmed comparable) and is genuinely informative; or the decision is so trivial that the economic impact of anchoring is negligible. More: deciqai.com/c/anchoring
Activate when: user says 'what's a fair price / starting number / ballpark'; counterparty just opened with a number; user is about to negotiate salary…
As a process B 68/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: 6. 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 68/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
- 70When it triggers. States when to use, but not when not to
- 100Tools and files. No external tools needed
- 100Steps. 44 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2255 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 570: enough signal without eating the budget
- +4Structure: 11 headings
- +3Step-by-step instructions: 44 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.