Content
88%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 maximally lean and its one instruction is unambiguous, but the skill is behaviorally thin — a word limit and persona sentence with no examples or guidance on what concise output should look like. It qualifies for the simple-skill exceptions on workflow and disclosure, with actionability the only real gap.
Suggestions
Add one short example of a desired concise response (a question and a 2-3 sentence model answer) to make the expected output style concrete.
Clarify edge behavior beyond the word limit, e.g., how to handle multi-part questions or code-heavy answers where 500 words is impractical.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is two sentences with zero padding and no explanation of concepts Claude already knows; every token (persona, word limit, exception clause) earns its place, matching the lean-and-efficient anchor. | 5 / 5 |
Actionability | "Keep responses under 500 words unless asked for more detail" is a concrete, executable rule with a numeric threshold, but there is no example of the desired output style and no coverage of common cases, placing it at the mostly-executable anchor rather than fully-executable. | 4 / 5 |
Workflow Clarity | This is a simple single-purpose skill and its single action — respond concisely, under 500 words, with an explicit exception — is unambiguous, so the simple-skill exception applies. | 5 / 5 |
Progressive Disclosure | The skill is under 50 lines with no bundle files and nothing that belongs in a separate file, so inline placement is appropriate; however there are no sections or organization at all, leaving it just below the well-organized anchor. | 4 / 5 |
Total | 18 / 20 Passed |