Content
50%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The body is a well-organized but monolithic API reference with concrete curl examples, two of which are malformed and non-executable. It lacks validation checkpoints and keeps all detail inline with no progressive disclosure into reference files.
Suggestions
Fix the malformed JSON in the Tavily Search and Tavily Crawl curl examples so they are copy-paste executable (wrap parameters in a "body":{…} object inside the `-d` string).
Move the verbose per-parameter reference into a separate references/ file (e.g. REFERENCE.md) and keep SKILL.md as a concise overview with one-level-deep links.
Tighten the long parameter descriptions (search_depth, auto_parameters, chunks_per_source) to the essential choices and tradeoffs, dropping redundant prose.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is a dense, verbose inline API reference — e.g. the multi-paragraph search_depth and auto_parameters descriptions — that could be tightened or moved to a reference file. It does not explain concepts Claude already knows, so it stays above 1, but the padding keeps it from a lean level-3. | 2 / 3 |
Actionability | Each endpoint ships a concrete curl command, but the Tavily Search and Tavily Crawl examples contain malformed JSON (fields like "query"/"url" sit outside the `-d '…'` string), so they are not copy-paste executable. That incompleteness matches the level-2 anchor rather than the fully-executable level-3 anchor. | 2 / 3 |
Workflow Clarity | Setup is sequenced (read credentials, or tell the user to run `npx gooseworks login`), but the API-call steps lack validation checkpoints or error-recovery guidance. The sequence is present but checkpoints are missing, matching level 2 rather than the validate-and-retry level-3 anchor. | 2 / 3 |
Progressive Disclosure | No bundle files exist and the entire ~190-line API reference lives inline in SKILL.md, matching the level-2 example of "200 lines of API reference that could be in a separate file". It is well-headed per endpoint, so it clears level 1, but nothing is split out to reach level 3. | 2 / 3 |
Total | 8 / 12 Passed |