Content
14%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill content is essentially a one-line restatement of the skill description with no actionable guidance. It provides no concrete commands, no formatter name, no examples, and no workflow — making it nearly useless as an instruction for Claude. It fails on every dimension except avoiding verbosity, and even there it crosses from concise into vacuous.
Suggestions
Add the specific formatter command(s) to run, e.g., `black`, `prettier`, `rustfmt`, or a project-specific script with exact invocation syntax.
Include at least one concrete example showing how to format a file or set of files, with expected command-line usage.
Add a brief workflow: 1) identify files to format, 2) run the formatter command, 3) verify changes (e.g., diff or re-run with --check flag).
If the project uses a specific configuration file or has formatting conventions, reference them or link to the relevant config file.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is extremely brief, which avoids verbosity, but it's so terse that it provides no useful information beyond restating the skill description. There's nothing unnecessary, but there's also nothing of value. | 2 / 3 |
Actionability | The content is entirely vague — no concrete commands, no code examples, no mention of which formatter to use, no file paths, no flags. It describes rather than instructs. | 1 / 3 |
Workflow Clarity | There is no workflow, no steps, no sequence, and no validation. Even for a simple task like running a formatter, there should be at minimum a concrete command and expected outcome. | 1 / 3 |
Progressive Disclosure | There is no structure whatsoever — no sections, no headers, no references to other files. It's a single sentence with no organization. | 1 / 3 |
Total | 5 / 12 Passed |