Content
85%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.
An exceptionally actionable curl cheat-sheet: complete executable commands for every common operation, a validated workflow with destructive-op confirmation and error-recovery guidance, and tight API-specific content. The weaknesses are inlined lookup material (~215 lines) that could live in reference files, and repeated rate-limit/encoding mentions across sections.
Suggestions
Move the Field Types write-shape table and the filterByFormula pattern list into a references/ file (e.g. references/field-types.md and references/formulas.md), keeping SKILL.md as an overview with well-signaled one-level-deep links.
State the 5 req/sec rate limit once (API Basics) and cross-reference it from the batch-create and Pitfalls sections instead of repeating it four times.
Consolidate the URL-encoding guidance (currently in Common Queries, Sort section, and Pitfalls) into the Pitfalls entry, and remove the duplicated pagination note from 'Important Notes for Hermes'.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense, API-specific material Claude does not already know (endpoints, write shapes, limits, error codes) with no explanation of basic concepts, fitting anchor 4's 'efficient with minor instances that could be trimmed'. It is not anchor 5 because the 5 req/sec rate limit is stated four times (API Basics, batch-create section, Pitfalls, workflow step 5), URL-encoding guidance appears in three places, and pagination is stated twice. | 4 / 5 |
Actionability | Every operation ships a complete, copy-paste-ready curl command (list bases/tables, list/get/filter/sort/view records, create, batch create, PATCH, upsert, delete, batch delete), plus an executable pagination while-loop and a working urllib.parse.quote one-liner. This matches anchor 5: fully executable commands covering the common cases. | 5 / 5 |
Workflow Clarity | The 'Typical Hermes Workflow' is a 6-step checklist with explicit validation at every risky point — "expect 200" auth confirmation, schema inspection before mutating, "Never guess record IDs", and destructive-op confirmation ("echo back the filter + record count and confirm before firing") — plus error-recovery feedback loops ("Monitor the Retry-After header on 429", "Read the errors array on non-2xx"). The destructive/batch cap at 3 does not apply since validation is present, and this fits anchor 5 better than anchor 4. | 5 / 5 |
Progressive Disclosure | The skill is a single 215-line file with no references/, scripts/, or assets/ directories at all — the full API reference (field-type table, formula patterns, every endpoint) is inlined in SKILL.md. This matches anchor 3's '[200 lines of API reference that could be in a separate file]'; the under-50-line simple-skill exception does not apply, and there is no reference structure to justify anchor 4. | 3 / 5 |
Total | 17 / 20 Passed |