Content
86%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 body is a tight, actionable, well-structured wrapper around a single script with concrete examples and a clear input/output contract. Its only gaps are a duplicated example payload and the absence of an explicit error-recovery loop.
Suggestions
De-duplicate the example JSON: keep the full payload only in 'Common patterns' and reference it from the Execution block, or vice versa.
Add a short error-recovery note in the Output or Execution section (e.g. on ok=false, inspect error.code/error.message, adjust path/params, and re-run).
Optionally note the collections list pagination/size handling so the higher timeout_sec guidance ties to a concrete verification step.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean and assumes Claude's competence (no explanation of what CELLxGENE or single-cell data is), but the same example JSON payload is duplicated between 'Common CELLxGENE patterns' and the 'Execution' block. Not 5 because of that duplicated payload that could be trimmed; not 3 because it is otherwise efficient with every line operational. | 4 / 5 |
Actionability | Quotes the copy-paste ready command 'echo '{...}' | python scripts/rest_request.py' plus concrete JSON input examples, a specific base_url, a real collection_id, specific paths, and explicit field lists. Not 4 because the guidance is fully executable and covers the common cases rather than having minor gaps. | 5 / 5 |
Workflow Clarity | The single action (build JSON input, pipe to script, interpret output) is unambiguous and the Output section documents the success/failure shape as a checkpoint; this is a read-only API call so the destructive/batch cap to 3 does not apply. Not 5 because there is no explicit validate→fix→retry recovery loop; not 3 because the sequence and error shape are clearly documented. | 4 / 5 |
Progressive Disclosure | At 37 lines with well-organized sections (Operating rules, Execution behavior, Input, Output, Execution, References) and a single one-level-deep reference to the real file scripts/rest_request.py, this fits the simple-skill exception for a 5. Not 4 because structure and the single reference are clear with no organization gaps. | 5 / 5 |
Total | 18 / 20 Passed |