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.
The content is a lean, highly actionable single-call skill: an exact endpoint with a ready request body, per-status-code error recovery, and a clean split of schema detail into a real one-level reference. Its main weakness is redundancy — the pagePath rules, no-SSE point, and package metadata are each stated twice, which could be tightened without losing information.
Suggestions
State the pagePath construction rules once (the prose paragraph and the first bullet say the same thing) and drop the duplicated intro line that repeats the frontmatter description verbatim.
Trim the 'Source and updates' section by not restating the version hash and source digest already present in the frontmatter, keeping just the canonical URL and update instruction.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense and directive with no beginner-concept explanations, but contains several duplications: the frontmatter description is repeated verbatim as the intro, the pagePath constraints appear both as prose ("The HTTP body requires pagePath... no origin, query or fragment") and again as a bullet ("do not send an origin, query, fragment or cache-refresh flag"), the no-SSE point is made twice, and the version, digest, and canonical URL are restated from the frontmatter. This matches 'Mostly efficient but includes some unnecessary explanation or could be tightened' — above 2 because there is no padding or taught concepts, below 4 because the redundancy is real and trimmable. | 3 / 5 |
Actionability | The call is fully specified — "one HTTPS POST request to https://govisit.ai/api/tools/v1/list_collection_places with Content-Type: application/json" plus a copy-paste JSON body with concrete values — and error handling maps each status to an action ("HTTP 400/413/415 require correcting the request; 429 requires waiting for Retry-After"). Minor gaps keep it at 4: no literal executable command (e.g., curl) and no sample response payload, with output shape deferred to contract.json. | 4 / 5 |
Workflow Clarity | This is a simple single-call skill whose single action is unambiguous (construct pagePath → POST → read data.items/data.count), which per the simple-skill exception can score 5. It additionally includes explicit error-recovery feedback loops: "invalid-input means correct the arguments", 429 → wait for Retry-After, and "Avoid unbounded retries", satisfying the 5 anchor's error-recovery requirement rather than the 4 anchor's 'minor validation gaps'. | 5 / 5 |
Progressive Disclosure | The body is a well-sectioned overview (call, interpret, browser variant, updates, licensing) that delegates the detailed input/output schemas to a 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" — the file exists and itself contains no further references. Content is appropriately split with easy navigation, matching the 5 anchor; the inline GitHub URL duplicate is a trivial blemish, not an organization gap. | 5 / 5 |
Total | 17 / 20 Passed |