AC atomic-habits
James Clear's "Atomic Habits" — an executable toolkit for building good habits, breaking bad ones, and mastering the tiny behaviors that lead to remarkable results. Covers 5 use cases: ① Habit Building — ("How do I start a new habit" "How to make exercise a daily routine") ② Habit Breaking — ("How to stop procrastinating" "How to quit bad habits for good") ③ Identity Change — ("How to become a different person" "How to change my self-image") ④ Environment Design — ("How to make good habits easy" "How to design my home for success") ⑤ System Thinking — ("How to stop relying on motivation" "How to build systems that work") Trigger when users say: "How to build a habit" "How to break a bad habit" "Atomic Habits" "James Clear" "Tiny changes" "1% improvement" "Habit stacking" "Identity-based habits" or mention: habits / behavior change / habit loop / cue-craving-response-reward / four laws of behavior change / make it obvious / make it attractive / make it easy / make it satisfying.
James Clear's "Atomic Habits" — an executable toolkit for building good habits, breaking bad ones, and mastering the tiny behaviors that lead to remarkable…
As a process C 58/100 · Has gaps — weak spots: result and completion, inputs and preconditions, consistency
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 58/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 1 mutating operations with no state check
- 40Consistency. Frontmatter name (atomic-habits) differs from the folder (atomic-habits-james-clear)
- 60Failures and branches. 2 branches
- 70When it triggers. States when to use, but not when not to
- 100Tools and files. No external tools needed
- 100Steps. 32 steps
- 100Execution cost. Instruction body is 2248 tokens
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
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 992: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +2Single-language instructions
- +5Description quotes 19 example trigger phrases
- +4Structure: 10 headings
- +3Step-by-step instructions: 32 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.