Content
86%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.
A tight, highly actionable skill body for a single-command workflow, with exact report templates and genuinely useful gotchas. The main defects are an internal contradiction on the staleness default (14 in the example vs 7 stated as default) and missing failure handling for the primary consistency command.
Suggestions
Resolve the staleness-default contradiction: the example command uses `--stale-after-days 14` while the filter description says "(default: 7)" — either drop the flag from the example or correct the stated default.
Add explicit handling for the main `minutes consistency` command failing or returning empty output, parallel to the existing nonzero-exit guidance for `minutes commitments --json`.
Clarify in step 1 or step 2 what to do when the JSON output is empty or the command errors, so the report-formatting workflow has a complete feedback loop.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean throughout — a single command, exact output templates, and a gotchas section containing only non-obvious operational knowledge ("it uses stable source snapshots, not a durable graph cache ... it does not exist"). Nothing explains concepts Claude already knows, and every section earns its place. | 5 / 5 |
Actionability | The command `minutes consistency --stale-after-days 14` is copy-paste ready and the report templates are exact, covering conflicts, resolved supersessions, stale items, and the clean case. However the example uses `--stale-after-days 14` while the filter list says "(default: 7)", an internal inconsistency that leaves a concrete detail ambiguous — a minor gap that keeps it below fully executable. | 4 / 5 |
Workflow Clarity | The sequence (run check → parse JSON → format report → suggest next steps) is clear, and the note "treat a nonzero exit as unavailable, never empty" provides an error checkpoint for the commitments source. It falls short of 5 because the main `minutes consistency` command has no stated failure or empty-output handling, and the default-value contradiction between step 1 and the filter list leaves a checkpoint ambiguous. | 4 / 5 |
Progressive Disclosure | This is a single-command skill with no bundle files (no references/, scripts/, or assets/ exist) and no need for external references; the body is well-organized into clearly labeled sections with all content appropriately inline, which merits a 5 under the simple-skill provision. | 5 / 5 |
Total | 18 / 20 Passed |