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.
A well-structured, mostly lean maintenance skill that delegates executable detail to a real one-level reference and includes the necessary destructive-operation safeguards (SSOT-sync gate, backups, dry-run, WIP exclusion, Before/After reporting). The body could tighten its contextual sections and surface a more explicit validate-then-proceed loop inline.
Suggestions
Tighten the "auto-cleanup-hook との連携" and "関連スキル" sections to one or two lines each, or fold them into the quick-reference table, to trim non-executable context.
Add an explicit "validate before proceeding" checkpoint in the 実行手順 sequence (e.g. run with --dry-run first, confirm the enumerated changes with the user, then execute) rather than relying on cleanup.md for the feedback loop.
Inline one short representative bash snippet (e.g. the logs find -delete or the state tail -2000 trim) so the most common subcommand is copy-paste ready without opening the reference.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean and assumes Claude's competence (terse quick-reference table, numbered steps, no concept explanations), but the "auto-cleanup-hook との連携" and "関連スキル" sections are contextual handoff material that could be trimmed slightly without losing executability. | 4 / 5 |
Actionability | Concrete subcommands, numbered execution steps, specific file paths, and an executable backup command ("cp <file> <file>.bak.$(date +%s)") are present, with the copy-paste-ready bash procedures delegated to cleanup.md; the body alone has minor gaps because the core deletion/split logic lives in the reference. | 4 / 5 |
Workflow Clarity | A clear 4-step sequence includes an explicit SSOT-sync validation gate (step 2) and Before/After reporting (step 4), and cleanup.md adds dry-run, backups, WIP-tag exclusion, and stop-on-error; it falls short of 5 because the body's own validate-then-proceed loop is brief and the detailed feedback checkpoints rely on the reference. | 4 / 5 |
Progressive Disclosure | A clear overview with well-organized sections points to a single one-level-deep reference ("[cleanup.md](./references/cleanup.md)") that exists and holds the detailed procedures; content is appropriately split and navigation is easy. | 5 / 5 |
Total | 17 / 20 Passed |