Content
72%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 admirably lean and appropriately scoped for a simple single-purpose skill, with clean structure and a sensible step order. Its weaknesses are the absence of executable formatter commands and any validation/verification checkpoint for what is a batch file-modifying operation, which hold actionability and workflow clarity at the midpoint.
Suggestions
Provide the concrete run command per detected config, e.g. '.prettierrc → npx prettier --write <files>', 'rustfmt.toml → cargo fmt', '.clang-format → clang-format -i <files>', so the guidance is executable rather than implied.
Add a validation checkpoint after formatting, such as re-running the formatter to confirm no further diffs or checking the exit status before reporting, to satisfy the batch-operation feedback-loop requirement.
Clarify how to detect the config when none of the three named files exists (e.g. fall back to asking the user or checking package.json formatter fields), closing a gap in step 1.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is nine lean lines with zero padding: 'Run the project's code formatter on specified files' plus a three-item step list. It assumes Claude's competence, explains nothing it already knows, and every token earns its place — a clear match for anchor 5. | 5 / 5 |
Actionability | There is some concrete guidance — specific config filenames ('.prettierrc', 'rustfmt.toml', or '.clang-format') — but 'Run the formatter on the specified files' gives no executable commands (e.g. 'npx prettier --write', 'cargo fmt', 'clang-format -i'), leaving key details missing. This matches anchor 3 ('Some concrete guidance but incomplete... missing key details') rather than 4, since nothing is copy-paste executable. | 3 / 5 |
Workflow Clarity | The sequence (find config → run formatter → report changed files) is clearly ordered, but running a formatter across files is a batch file-modifying operation with no validation or verification step, which caps workflow clarity at 3 per the rubric guideline that overrides the simple-skill exception. It is not 2 because the steps are coherent and step 3 provides partial change-tracking. | 3 / 5 |
Progressive Disclosure | This is a simple skill under 50 lines with no need for external references (no references/, scripts/, or assets/ exist), and the content is organized into a purpose line plus a '## Steps' section. Per the rubric's simple-skill guideline, well-organized sections alone warrant anchor 5. | 5 / 5 |
Total | 16 / 20 Passed |