Content
88%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 highly actionable, well-structured curl reference with a clear validated workflow and strong handling of destructive/batch operations. It is slightly verbose in places and keeps all reference material inline rather than progressively disclosing it into separate files.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense and reference-like, assuming Claude knows what curl/Airtable are, but a few prose asides ("Great for idempotent syncs.", "Burst on a single base will be throttled.") could be trimmed, so it falls just short of fully lean. | 4 / 5 |
Actionability | Copy-paste-ready curl commands cover list/get/filter/sort/view/create/batch/update/upsert/delete/pagination, with concrete request bodies and URL-encoding patterns — fully executable guidance across the common cases. | 5 / 5 |
Workflow Clarity | The "Typical Hermes Workflow" sequences six numbered steps with explicit validation checkpoints (expect 200 on auth, inspect schema before mutating, read-before-write to resolve record IDs, echo-back + confirm before destructive deletes), satisfying the batch/destructive validation requirement. | 5 / 5 |
Progressive Disclosure | No bundle files exist and the single SKILL.md is well-organized into clearly headed sections, but the full field-type table and API reference are inlined rather than split into separate reference files, leaving minor organization gaps. | 4 / 5 |
Total | 18 / 20 Passed |