AF habit-flow
AI-powered atomic habit tracker with natural language logging, streak tracking, smart reminders, and coaching. Use for creating habits, logging completions naturally ("I meditated today"), viewing progress, and getting personalized coaching.
AI-powered atomic habit tracker with natural language logging, streak tracking, smart reminders, and coaching.
As a process F 39/100 · Will not run — References files that are not bundled: references/personas/{activePersona}.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: 62. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: references/personas/{activePersona}.md - note
frontmatter-keyunknown frontmatter key "homepage"
Process rating: all ten parameters 39/100
- 0Tools and files. 1 referenced file(s) missing: references/personas/{activePersona}.md
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 30Running it twice. 11 mutating operations with no state check
- 40Consistency. Frontmatter name (habit-flow) differs from the folder (habit-flow-skill)
- 50Failures and branches. 0 branches, has a failure section
- 70When it triggers. States when to use, but not when not to
- 85Steps. 96 steps, 1 vague phrases
- 100Execution cost. Instruction body is 3199 tokens
- 100Progress reporting. Reports progress
- low 10 top-level sections: this looks like several domains in one skill
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)
- +3Output format is not stated: the model decides each time
- -213 emoji in the instructions: noise for the model
- -33 of 12 scripts are never mentioned in SKILL.md
- +2Single-language instructions
- +3Description length 241: enough signal without eating the budget
- +4Structure: 22 headings
- +3Step-by-step instructions: 96 items
- +4Has examples (26 code blocks)
- +4Reference files are cited in the instructions (8 of 15)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 77.