Contextual guidance and command discovery. Three modes — narrative (first-time), contextual (mid-task), compact (quick reference). Shows available commands, active skills, and intelligent suggestions based on vault state.
SkillScore77Maintained
Automatic
◆Knowledge Management pack
Last verified 8/12/2026
What it changes
Passed 15 of 20 test cases with the skill, and 3 of 20 without it.
Without skill14%
With skill77%
Checks it passed that the model alone missed
Output suggests building connections using /{reflect}
Output checks manual/skills.md for extra workflow context
Output prioritizes running /health as the recommended next action
and 15 more in the full report
14 fixed3 passed either way5 still failing0 broke
Pass-rate lift
+64 pp
Tokens
+183%
Agent turns
0%
Response time
-33%
Model gemini-3.6-flashMeasured 8/12/2026v117 of 22 cases passed with skill · 20 comparable
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 14 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 14
Prompt
My vault has 12 notes, 0 inbox files, 0 queue tasks, but `ops/health/` contains an active diagnostic warning report. What suggestion is rendered in contextual mode?
What was checked, without and with the skill
Checked
Without skill
With skill
Output prioritizes running /health as the recommended next action
Missed
Passed
case-14 · gemini-3.6-flash · 8/12/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md339 linessingle file
EXECUTE NOW
Target: $ARGUMENTS
Parse immediately:
If target contains --compact: force compact mode regardless of vault state
If target contains a skill name (e.g., "help reduce" or "help reflect"): show detailed help for that specific skill
If target is empty: determine mode from vault state
Execute these steps:
Gather vault state (Step 1)
Resolve domain vocabulary (Step 2)
Determine mode (Step 3)
Discover commands dynamically (Step 4)
Render the appropriate mode (Step 5)
START NOW. Reference below defines each step.
Step 1: Gather Vault State
Determine the notes folder by checking which domain-named directory exists (notes/, reflections/, concepts/, ideas/, decisions/, memories/, or any custom name from derivation-manifest.md). Then gather counts:
Note count:.md files in the notes folder, excluding MOCs (files with type: moc in frontmatter)
Inbox count:.md files in the inbox folder (inbox/, journal/, encounters/, etc.)
Observation count:.md files in ops/observations/ or ops/methodology/
Tension count:.md files in ops/tensions/
Connection density: count wiki links ([[) across notes folder; sparse if fewer than 2x note count
Queue state: pending tasks in ops/queue/queue.yaml or ops/queue/queue.json
Health warnings: check latest report in ops/health/ if it exists
Tutorial state: check ops/tutorial-state.yaml for incomplete tutorial
Session count: estimate from ops/sessions/ file count (indicates usage maturity)