Content
77%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.
A well-structured, highly actionable single-purpose skill whose calling guidance, error handling, and reference split are exemplary. The main drag is token efficiency: the 'Source and updates' and licensing sections duplicate frontmatter metadata and repeat URLs already stated elsewhere.
Suggestions
Trim the 'Source and updates' section: the version hash and source digest are already in the frontmatter, so the body can simply point to the canonical URL and the discovery index without restating them.
State the contract reference once with a single URL (either the bundled path or the web URL) instead of giving both inline and again in 'Source and updates'.
Add a one-line ready-to-use request example (e.g., a curl command) or a second JSON example covering 'auto'/'intent' mode to close the small actionability gap.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The instructional sections ('Call the tool', 'Interpret the response') are dense and assumption-respecting, but the 'Source and updates' section repeats the version hash and source digest already present in frontmatter, and the canonical and contract URLs each appear twice in the body. Time-sensitive version identifiers are not confined to a deprecation-style section, so the body could be meaningfully tightened. | 3 / 5 |
Actionability | Concrete, executable guidance throughout: exact endpoint and method ('HTTPS POST request to https://govisit.ai/api/tools/v1/search_places with Content-Type: application/json'), a complete JSON request body, mode-specific limits, and per-status error semantics (400/413/415, 404, 429 with Retry-After, 503). Minor gaps keep it below 5: no ready-made request command (e.g., a curl line) and only the 'name' mode is exemplified. | 4 / 5 |
Workflow Clarity | For this single-task skill the sequence is unambiguous — build arguments per the contract, make one POST, interpret data.items, then verify — with explicit checkpoints and feedback loops: 'Open returned canonical URLs to inspect published evidence before making claims', 'invalid-input means correct the arguments', '429 requires waiting for Retry-After', and 'Avoid unbounded retries'. This matches the anchor-5 pattern of explicit validation steps and error-recovery loops. | 5 / 5 |
Progressive Disclosure | The body is a lean overview that defers exact schemas to a single clearly signaled, one-level-deep reference — 'Read [references/contract.json](references/contract.json) for the exact input and output JSON schemas, supported fields, and defaults' — and that file exists in the bundle and matches the described endpoint. Sections are well organized with no nested-reference chains. | 5 / 5 |
Total | 17 / 20 Passed |