Content
58%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 (a strong 5 on conciseness and trivially well-structured for its size) but tells Claude nothing executable: what 'inspect' means, how to find the selected graph, or what result to produce is left entirely to guesswork. The single vague directive caps actionability and workflow clarity at the low end, making the skill unusable as written despite its token efficiency.
Suggestions
Define 'inspect' concretely: specify the exact command, API, or steps to run and the output to produce (e.g., a code snippet or command that dumps the selected graph's structure).
Explain how to locate 'the exact selected graph' (e.g., from editor state, a session variable, or a file path) so the directive is executable.
If inspection can fail or produce multiple candidates, add a short validation/checkpoint step so the workflow is unambiguous.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body 'Inspect the exact selected graph.' is five words with zero padding, no explanation of concepts Claude already knows, and no filler — every token earns its place. This matches anchor 5 ('Lean and efficient; assumes Claude's competence'). | 5 / 5 |
Actionability | 'Inspect the exact selected graph.' is a single high-level directive with no method, tool, command, code, or expected output — matching anchor 2 ('Minimal concrete guidance; high-level hints but missing the specific steps to execute'). It is above anchor 1 because it instructs a specific action on a specific object rather than merely describing, and below anchor 3 because even pseudocode-level concreteness is absent: 'inspect' is left entirely undefined. | 2 / 5 |
Workflow Clarity | The single action is stated but ambiguous — 'inspect' has no defined procedure, the expected output is unspecified, and how to identify 'the exact selected graph' is unaddressed (anchor 2: 'steps poorly defined'). The simple-skill exception would allow a 5 only if the single action were unambiguous, which it is not. | 2 / 5 |
Progressive Disclosure | The skill is a single line under 50 lines with no bundle files (no references/, scripts/, or assets/ directories exist) and no content that belongs in separate files, so the simple-skill exception applies: the trivial structure is fully appropriate, with no monolithic text, buried references, or nested references. | 5 / 5 |
Total | 14 / 20 Passed |