AF commitment-consistency
Activate when: user says "foot in the door," "I already committed so I have to follow through," "how do I design onboarding / a sales sequence / a commitment ladder," "Cialdini," "would I do this fresh," or is evaluating whether past small steps are pulling them into a bigger decision. Do NOT activate when: the situation is genuinely single-shot with no prior commitment history; commitment framing would be used to pressure someone who already has limited choice. More: deciqai.com/c/commitment-consistency
Activate when: user says "foot in the door," "I already committed so I have to follow through," "how do I design onboarding / a sales sequence / a commitment…
As a process F 45/100 · Will not run — References files that are not bundled: references/sources.md
How to improve
- The text references files that are not there: add them or drop the references.
- 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: 0. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: references/sources.md
Process rating: all ten parameters 45/100
- 0Tools and files. 1 referenced file(s) missing: references/sources.md
- 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. 31 mutating operations with no state check
- 50When it triggers. No condition that starts the skill
- 60Result and completion. Output format stated, no completion criterion
- 100Steps. 21 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1831 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
- +1No license
- +2Single-language instructions
- +5Description quotes 5 example trigger phrases
- +4Description says when NOT to use the skill
- +3Description length 509: enough signal without eating the budget
- +4Structure: 10 headings
- +3Step-by-step instructions: 21 items
- +3Output format is stated explicitly
- +4Has examples (1 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 90.