AC 12-rules-for-life
Jordan B. Peterson's "12 Rules for Life: An Antidote to Chaos" — an executable toolkit for finding meaning, confronting chaos, and living responsibly. Covers 5 use cases: ① Personal Responsibility — ("How to take control of my life" "How to stop blaming others") ② Meaning & Purpose — ("How to find meaning" "What should I do with my life") ③ Overcoming Chaos — ("How to handle uncertainty" "How to stay strong in difficult times") ④ Relationships — ("How to choose good friends" "How to be a better parent") ⑤ Truth & Honesty — ("How to tell the truth" "How to stop lying to myself") Trigger when users say: "12 Rules for Life" "Jordan Peterson" "Stand up straight" "Lobsters" "Meaningful vs expedient" "Tell the truth" "Set your house in order" "How to find meaning" "Antidote to chaos" or mention: Peterson / responsibility / meaning / chaos / truth / suffering / order / tyranny of the familiar / standing up straight / picking the right friends.
Jordan B. Peterson's "12 Rules for Life: An Antidote to Chaos" — an executable toolkit for finding meaning, confronting chaos, and living responsibly. Covers…
As a process C 57/100 · Has gaps — weak spots: result and completion, 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: 8. 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 57/100
- 0Result and completion. Does not say what the result is
- 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. 1 mutating operations with no state check
- 70When it triggers. States when to use, but not when not to
- 100Tools and files. No external tools needed
- 100Steps. 36 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1894 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
- +4Description does not say when NOT to use the skill (false activations)
- +3Description length 950: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +2Single-language instructions
- +5Description quotes 20 example trigger phrases
- +4Structure: 10 headings
- +3Step-by-step instructions: 36 items
- +4Has examples (1 code blocks)
- +4Reference files are cited in the instructions (5 of 5)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 91.