Content
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid CLI reference skill with excellent actionability — every command has concrete, executable examples with real spec identifiers. The main weaknesses are minor redundancy (duplicate examples, some restated information in the usage patterns section), and the lack of error handling/validation guidance in workflows. The structure is good but could benefit from slightly tighter editing and explicit error recovery steps.
Suggestions
Remove the duplicate 'DOM#concept-tree' example in the query section and trim explanatory sentences that restate what the examples already demonstrate.
Add brief error handling guidance — e.g., what to do when a query returns empty results, how to handle specs that fail to fetch, or how to interpret common error messages.
Consider moving the 'Usage patterns for Gecko development' section to a separate file (e.g., GECKO_PATTERNS.md) and linking to it, keeping SKILL.md as a concise command reference.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Generally efficient but has some redundancy — the 'DOM#concept-tree' example appears twice in the query section, and the 'Usage patterns for Gecko development' section partially repeats information already covered in the commands section. Some explanatory sentences like 'This is the primary command — use it to read what a spec section says' could be trimmed. | 2 / 3 |
Actionability | Every command is shown with concrete, copy-paste-ready examples. Multiple usage patterns are demonstrated with real spec identifiers, flags, and expected behaviors (e.g., exit codes for `exists`). The installation instructions are also concrete. | 3 / 3 |
Workflow Clarity | The 'Usage patterns for Gecko development' section provides reasonable multi-step workflows, but there are no validation checkpoints or error recovery steps. For example, what happens if a query returns no results, or if cargo install fails? The workflows are sequential but lack feedback loops. | 2 / 3 |
Progressive Disclosure | The content is well-structured with clear sections and headers, but it's somewhat long for a single file with no references to external documentation. The 'Usage patterns for Gecko development' section could potentially be a separate file, and there's no mention of a --help flag or external docs for deeper reference. | 2 / 3 |
Total | 9 / 12 Passed |