Content
78%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 well-structured, executable recipe: four sequenced git-inspection steps with real commands and a concrete output template, all appropriately contained in one file. Its weaknesses are minor — redundant framing text and advertised argument variants that the instructions never define.
Suggestions
Drop or merge the 'Purpose' section and the opening line, which restate the frontmatter description and add tokens without new information.
Either implement the advertised argument modes or remove them: '/catchup --brief', '/catchup auth', and the '[branch] [--since <date>]' hint have no corresponding instructions, so tell Claude exactly how to filter or summarize differently for each.
Harden the Step 3 TODO scan for filenames with spaces (e.g., use 'git grep -n -e TODO -e FIXME -- $(git diff --name-only HEAD~5)' or '-z' with xargs -0) so the flagship command is robust.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dominated by lean, commented bash blocks with no explanations of concepts Claude already knows, matching anchor 4 ('efficient; minor instances of over-explanation that could be trimmed'). It misses anchor 5 because the 'Purpose' section and opening line restate the frontmatter description, and the emoji-decorated output template carries some padding. | 4 / 5 |
Actionability | Steps 1-4 provide concrete, copy-paste-ready bash commands and the Output format is an explicit fill-in template, matching anchor 4 ('mostly executable guidance... with minor gaps'). Not anchor 5 because the Usage examples promise '/catchup --brief' and '/catchup auth' modes (and the argument-hint advertises '[branch] [--since <date>]') that no instruction actually implements, and the TODO-scan pipeline breaks on filenames with spaces. | 4 / 5 |
Workflow Clarity | The four steps are clearly sequenced (history analysis → recent changes → TODO scan → project state) and the operation is read-only, so the destructive/batch validation cap does not apply. It matches anchor 4 ('clear sequence with most checkpoints present; minor validation gaps') but not 5, since the advertised argument modes (--brief, branch filter, --since) are undefined in the instructions, leaving an execution gap. | 4 / 5 |
Progressive Disclosure | There are no bundle files and none are needed: this self-contained, single-task skill keeps all content appropriately inline under a clean hierarchy (Purpose, Instructions with four labeled steps, Output format, Usage examples, Pro tips), making navigation trivial. Per the simple-skill scoring note, well-organized sections with no need for external references warrant a 5. | 5 / 5 |
Total | 17 / 20 Passed |