Content
71%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 provides a clear, executable four-step workflow with concrete MCP tool names and parameters. Its main weakness is redundancy: the Guidelines and When-to-Use sections repeat content already covered in the steps and the description.
Suggestions
Merge the "Version awareness" and "One topic per query" guideline bullets into their corresponding steps (Step 2 and Step 3) so each rule appears exactly once.
Trim the "When to Use This Skill" section to a single line or remove it, since it duplicates the frontmatter description.
Add a brief fallback to Step 2 for when resolution returns no good match (e.g., retry with a more specific libraryName, or answer from training data with a caveat).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | "Version awareness" and "One topic per query" in the Guidelines section restate the version and multi-concept guidance already given in Steps 2 and 3, and "When to Use This Skill" duplicates the frontmatter description. Mostly efficient with no concept padding, but the duplicated rules mean it could be noticeably tightened. | 3 / 5 |
Actionability | Gives concrete tool names (`resolve-library-id`, `query-docs`) with explicit parameters (`libraryName`, `query`, `libraryId`) and an example ID (`/vercel/next.js`). Minor gaps: no example call payload and no description of the resolution result fields needed for Step 2's selection criteria. | 4 / 5 |
Workflow Clarity | A clear four-step sequence (resolve → select → fetch → use) with concrete selection criteria (exact match, benchmark scores, version-specific IDs). This is a read-only lookup so no validation cap applies, but there is no fallback guidance for when resolution returns no good match. | 4 / 5 |
Progressive Disclosure | A compact (~50 line) single-file skill with no bundle files and no need for external references, organized into clear sections (When to Use, How to Fetch Documentation, Guidelines). Per the simple-skill note, well-organized sections alone merit full credit here. | 5 / 5 |
Total | 16 / 20 Passed |