Content
63%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 well-structured as a facade skill: a clear triage matrix, explicit invariants, and a closing verification checklist. Its weaknesses are an overloaded path-resolution/telemetry invariant that should be extracted to a reference file, and referenced workflow/src files that are absent from the bundle, leaving the progressive-disclosure chain broken.
Suggestions
Extract the runtime-root 4-step precedence contract and telemetry policy from Invariant 1 into a reference file (e.g. references/path-resolution.md), keeping only the repository-path authority rule inline.
Ensure the referenced `workflows/*.md` runbooks and `src/init/init.mjs`, `src/migration/migrate.mjs`, `src/validation/validate.mjs` actually ship in the skill bundle so the dispatch table's links resolve.
Move the per-segment definitions of the canonical numbering table into a reference document, keeping the ID pattern, canonical name, and path columns inline for quick triage.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body avoids explaining known concepts, but Invariant 1 packs path precedence, a 4-step runtime-root resolution contract, and telemetry policy into one ~200-word paragraph, and the numbering table inlines dense segment definitions — material that could be tightened or moved to a reference file. This is 'mostly efficient but could be tightened' rather than clearly verbose. | 3 / 5 |
Actionability | Concrete executable commands are present (`node "${PLUGIN_ROOT}/src/init/init.mjs"`, `src/migration/migrate.mjs`), with exact paths, env-var precedence, and an intent-to-runbook dispatch table. It stops short of 5 because the detailed per-workflow procedures live in external workflow files rather than being demonstrated inline. | 4 / 5 |
Workflow Clarity | Dispatch sequencing is clear (triage matrix, bootstrap-before-interview ordering, explicit stop-and-migrate condition on legacy detection) and a Verification checklist closes every workflow. Not 5 because the per-workflow step sequences and error-recovery feedback loops are delegated to external runbooks not shown in the body. | 4 / 5 |
Progressive Disclosure | References to `workflows/product.md` through `workflows/maintain.md` and `src/*.mjs` are clearly signaled and one level deep, but scoring against the actual bundle (only `assets/` with config.json, schema.json, and templates/ exists), none of the referenced workflow or src files are present — the navigation chain cannot be completed. Structure and signaling are good, but the referenced content is not verifiable in the bundle. | 3 / 5 |
Total | 14 / 20 Passed |