Content
71%Weight 40%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The body is a tight, well-organized pattern statement: a clear principle, concrete DO/DON'T directives, and identifiable provenance. Its main weakness is that the concrete directions (hook name, --file flag) never assemble into an executable command or example, leaving the 'how' to inference. The non-operational Source Sessions section is minor token overhead.
Suggestions
Add one executable example, e.g. the actual indexing command invoked in the PostToolUse Write hook (including the tool name behind `--file`), so the guidance is copy-paste ready.
Show a minimal hook configuration or command line demonstrating 'trigger indexing from the same event that creates the artifact'.
Drop or compress the Source Sessions section (session IDs a541f08a, 1c21e6c8 add no operational value), or move provenance out of the runtime body.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean and assumes competence — "Index artifacts when they're created, not at batch boundaries" plus terse DO/DON'T bullets with no concept explanations. It falls just short of anchor 5 because the "Source Sessions" section ("a541f08a", "1c21e6c8") is non-operational provenance padding that could be trimmed, matching anchor 4 ('minor instances... that could be trimmed'). | 4 / 5 |
Actionability | Guidance is directionally concrete — "Index handoffs in PostToolUse Write hook", "Use `--file` flag" — but never gives an executable command or hook configuration, so key details are missing (which indexer, what invocation). This matches anchor 3 ('Some concrete guidance but incomplete... missing key details'); not 4 because nothing here is copy-paste executable or spec-complete. | 3 / 5 |
Workflow Clarity | As a simple single-purpose skill, the single action is clearly stated from three reinforcing angles: index in the PostToolUse Write hook 'immediately after creation', 'Trigger indexing from the same event that creates the artifact', and the DON'T items fence off the wrong paths (SessionEnd batching, cron). It sits at anchor 4 rather than 5 because no example hook implementation or verification that indexing succeeded is shown — a minor gap, not an incoherent or unsequenced process. | 4 / 5 |
Progressive Disclosure | The skill is under 50 lines, self-contained, needs no external references (none exist in references/, scripts/, or assets/), and is organized into clear sections (Pattern, DO, DON'T, Source Sessions). Per the simple-skill guideline this matches anchor 5 — well-organized sections with nothing that should be split out. | 5 / 5 |
Total | 16 / 20 Passed |