Content
82%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 highly actionable, well-organized CLI skill guide with executable commands, a flags reference, and an explicit result-verification step. It falls just short of top marks on conciseness (coaching dialogue padding), workflow clarity (no recovery path for failed `minutes get`), and progressive disclosure (all content inline at ~85 lines).
Suggestions
Trim the scripted dialogue quotes in "Search coaching" to one-line directives and merge overlapping advice from "Tips for good searches" to reduce token spend.
Add an error-recovery branch for the `minutes get` step (e.g., what to do on non-zero exit or a stale path, such as re-running `minutes list` or the search to confirm the path).
Move the "Search coaching" heuristics and "Gotchas" into a single reference file (e.g., `references/search-strategies.md`) to keep SKILL.md closer to a lean overview.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is largely lean and command-first, but the "Search coaching" section carries several scripted dialogue responses (e.g., "That'll return hundreds of results. What specifically are you looking for?") and "Tips for good searches" partially reiterates coaching content, so it is not anchor-5 tight. | 4 / 5 |
Actionability | Fully executable, copy-paste-ready commands cover the common cases: `minutes search "pricing strategy"`, `-t memo`, `--since 2026-03-01 --limit 5`, `minutes get "<exact path>" --json`, plus concrete auxiliary commands like `date -v-7d +%Y-%m-%d` and `qmd update && qmd embed`, with a flags table and output-field list. | 5 / 5 |
Workflow Clarity | The sequence — narrow the query (coaching), run `minutes search`, then reauthorize with `minutes get "<exact path>" --json` while requiring "exit status 0" — includes an explicit validation checkpoint, but there is no error-recovery guidance for what to do when `minutes get` fails or the path is stale. | 4 / 5 |
Progressive Disclosure | Sections (Usage, Flags, Output, How search works, Search coaching, Tips, Gotchas) are well-labeled and easy to navigate, but at ~85 lines with everything inline — including a coaching section that could live in a separate reference file — it doesn't meet the under-50-lines condition for a 5, and there is minor content that would fit better split out. | 4 / 5 |
Total | 17 / 20 Passed |