Content
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
An actionable, well-organized single-purpose tool skill with executable commands and complete schemas. Its main weakness is redundancy: the input parameters are restated in prose, a call template, and a table.
Suggestions
Collapse the duplicated input descriptions — keep the parameter table and the executable call example, and remove or trim the separate prose 'Inputs' section that repeats the same information.
Drop the generic JSON-schema 'How to Call' template in favor of a single realistic example with actual filter values to reduce token overhead.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly efficient with executable command templates and schemas, but the inputs are described three times (prose 'Inputs', a 'How to Call' template, and an 'Input' table) which is redundant padding. | 2 / 3 |
Actionability | Provides a concrete, copy-paste-ready CLI invocation, stdin/file variants, and full input/output JSON schemas, all of which are executable. | 3 / 3 |
Workflow Clarity | This is a simple single-action tool skill where the single action is unambiguous; per the simple-skills note, a clearly presented call plus troubleshooting guidance earns 3, and there are no destructive or batch operations requiring validation checkpoints. | 3 / 3 |
Progressive Disclosure | A self-contained skill under 50 lines with no bundle files and clear, well-organized sections (Inputs, How to Call, Input schema, Output schema); per the guidelines this satisfies the bar for 3. | 3 / 3 |
Total | 11 / 12 Passed |