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 tight, well-sequenced instruction skill: exact commands, platform-specific trash handling, explicit validation before and after batch changes, and a concrete reporting format. The only slack is slight redundancy with the description and a few unnamed tool references, neither of which materially hurts execution.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean, task-specific, and assumes Claude's competence (no explanations of what bash or file systems are), but the opening paragraph restates the description's trigger list and the document-search boundary is stated twice ("not a document search" and later "Do **not** search document contents, the user's datasources, or the web"). Minor trims are possible — anchor 4, not 5. | 4 / 5 |
Actionability | Concrete commands are named throughout (`ls`, `mkdir`, `mv`, `cp`, a bounded `find`, platform-specific `/usr/bin/trash` and `gio trash`) plus a concrete report format ("old path → new path (one per line)"), but "the converter tools", "the duplicate scan", and "the file-name discovery tools" are referenced without being named, and no concrete bulk-rename pattern is shown. Mostly executable guidance with minor gaps — anchor 4, not 5. | 4 / 5 |
Workflow Clarity | The rules form a clear sequence with validation on both ends of a batch/destructive operation — pre-check ("check that no two targets share a name and that no target already exists before you move anything. Never overwrite an existing file") and post-check ("List the destination folder to check the changes really happened") — which clears the destructive/batch cap. Not 5: there is no explicit error-recovery loop (e.g. what to do when a target name collides beyond skipping and reporting it). | 4 / 5 |
Progressive Disclosure | The body is 35 lines, needs no external references (none exist in the bundle, and none are referenced), and is organized into clearly labeled sections ("How to do it", "Rules") with bolded rule names — matching the simple-skill exception where a short, well-organized skill with no external references scores 5. | 5 / 5 |
Total | 17 / 20 Passed |