Content
50%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 skill provides organized API reference coverage with concrete curl examples, but several examples are malformed and non-executable, and there is no explicit validation loop for the async research-task workflow. Content is well-sectioned but entirely inline with no bundle files.
Suggestions
Fix the broken curl JSON for /search, /findSimilar, and /contents so the request body is correctly inside the -d string and parameter names match the documented schema (e.g. numResults, not num_results).
Add an explicit create-task → poll-task validation workflow with a checkpoint (e.g. poll GET /research/v1/{researchId} until status is complete; handle failed/error statuses before returning results).
Remove the duplicated Capabilities list or the standalone restatement of the description to tighten conciseness, and consider moving the per-endpoint parameter reference into a bundled reference file.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is mostly efficient reference material, but the Capabilities list duplicates the per-endpoint descriptions that reappear in Usage, and the standalone line 'Neural search engine for...' restates the frontmatter description. | 3 / 5 |
Actionability | Concrete curl examples are provided per endpoint, but several are malformed (stray JSON lines outside the -d string for /search, /findSimilar, /contents) and parameter names diverge from the docs (num_results vs numResults), making them not copy-paste executable. | 3 / 5 |
Workflow Clarity | Setup and per-endpoint usage are sequenced, but this is reference-style documentation; the async create-then-poll flow mentions polling 'until the task is finished' without an explicit validation checkpoint or error-recovery loop. | 3 / 5 |
Progressive Disclosure | The ~200-line body is organized into clear sections (Setup, Capabilities, Usage, Use Cases, Discover More) with no bundle files, but the per-endpoint parameter reference is inlined rather than split into separate reference files. | 3 / 5 |
Total | 12 / 20 Passed |