Content
83%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 an excellent lean reference catalog: token-efficient tables with copy-paste-ready usage for every script, plus genuinely novel details (session naming rules, cpx fallback order, excluded dangerous scripts). Its main weaknesses are the absence of validation guidance around destructive commands like git-abort and mux delete, and missed opportunity to move the lengthy tmux/solo detail into a reference file.
Suggestions
Add pre-flight validation guidance for destructive commands, e.g. "Before git abort, run git status and confirm no uncommitted work is needed" and "Before mux delete, run mux show to review panes that will be lost".
Move the detailed tmux/mux naming and registry rules and the solo configuration description into a references/ file (e.g. references/tmux.md), keeping a short table plus a clearly signaled link in SKILL.md.
For git-sync and git-tidy, note what "cleanup" and "merged/deleted on remote" will actually remove so their effects are verifiable before running.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is pure reference tables pairing each script with usage syntax and purpose, with no explanations of concepts Claude already knows; even the dense mux paragraph conveys only novel, non-derivable information (session naming scheme, registry behavior, hook-based restore). | 5 / 5 |
Actionability | Every entry gives copy-paste-ready usage examples ("git save file1 file2 \"message\"", "killport 3000", "mux tab <name> [path]") plus a one-line purpose, and supplementary details like cpx's fallback order and git-issue's env-var requirement are exactly the specifics needed to execute. | 5 / 5 |
Workflow Clarity | As a command reference each entry's usage is unambiguous, but destructive operations ("git-abort ... Hard reset + clean untracked files (destructive)", "mux delete", "git-delete") carry only warning labels with no validation or verification guidance, which caps this dimension at 3 per the rubric's destructive-operation rule. | 3 / 5 |
Progressive Disclosure | Sections are clearly organized by category with a useful "Not Documented" exclusion list, but at ~110 lines all content is inline (exceeding the under-50-line simple-skill exception) and self-contained detail blocks like the tmux/mux system and solo configuration could live in a one-level-deep reference file. | 4 / 5 |
Total | 17 / 20 Passed |