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 content is lean, executable, and clear for a single-command skill, scoring well on conciseness, actionability, and workflow clarity. Its main weakness is progressive disclosure: it advertises a `search.mjs` script that is not present in the bundle.
Suggestions
Ship the referenced `search.mjs` under a `scripts/` directory (or remove the script reference) so the bundle matches the documented invocation.
If the script grows, move detailed flag/env documentation into a short reference file and link to it one level deep to keep SKILL.md as an overview.
Add a one-line validation note (e.g. expected exit behavior or how to confirm URLs appeared) so users can verify a successful run.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean and efficient: a short overview, the script name, a copy-paste command, two examples, a flag list, and brief output/notes. It assumes Claude's competence and avoids explaining what web search or Node are. | 5 / 5 |
Actionability | It gives a fully executable invocation `node search.mjs "..." --purpose "..."`, two concrete examples, and a complete optional-flags list (provider, model, timeout, json) — copy-paste ready and covering common cases. | 5 / 5 |
Workflow Clarity | This is a single-command skill where the action is unambiguous: run the script with a query and purpose. Per the simple-skill exception, an unambiguous single action can score 5, and the "Output expectations" and "Notes" sections clearly frame results and failure handling. | 5 / 5 |
Progressive Disclosure | The body references `search.mjs` but no `scripts/` directory or `search.mjs` file exists in the bundle, so the one referenced path is broken; structure is otherwise minimal sections with no deeper reference material to navigate to. | 2 / 5 |
Total | 17 / 20 Passed |