Content
93%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.
Excellent CLI skill content: entirely executable commands organized into clean sections (setup, read, write, add examples, modify examples, limitations), with dry-run previews and an auth-token workflow making write operations safe. The only gap is the absence of an explicit post-update verification step in the modify workflow.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is command-list style with zero concept explanation — it never explains what Things 3 or a URL scheme is, jumps straight to executable commands (e.g., "`things add "Buy milk" --notes "2% + bananas"`"). Every line is a command, flag, or operational note, matching the 'lean and efficient; every token earns its place' anchor. | 5 / 5 |
Actionability | All guidance is copy-paste-ready: read commands ("`things inbox --limit 50`", "`things search "query"`"), write examples covering notes, when/deadline, list, heading, tags, checklist items, and a full update workflow with concrete flag combinations ("`things update --id <UUID> --auth-token <TOKEN> --completed`"). Specific examples cover the common cases, matching the top anchor. | 5 / 5 |
Workflow Clarity | The modify workflow is well sequenced with an explicit safety checkpoint ("Prefer safe preview: `things --dry-run add`"; "First: get the ID (UUID column): `things search "milk" --limit 5`") plus error-recovery guidance ("If DB reads fail: grant Full Disk Access"), but there is no post-write verification step (e.g., re-running search to confirm the change), so it fits 'clear sequence with most checkpoints' rather than the full validate-feedback-loop anchor at 5. | 4 / 5 |
Progressive Disclosure | This is a single-purpose, ~60-line skill with no bundle files; all content (setup, read ops, write ops, examples, limitations) appropriately lives inline under clear section headers with nothing that belongs in a separate file, and navigation is trivial. It matches the simple-skill pattern where well-organized sections in one file score full marks; the 4 anchor would require misplaced or poorly-split content, which is absent. | 5 / 5 |
Total | 19 / 20 Passed |