Content
57%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 well-structured, mostly executable guide to driving Wave Financial through the Membrane CLI, with strong command coverage and a clear connection-state workflow. It loses points for marketing-style padding, placeholder-only action examples, missing validation around destructive operations, and an inlined reference table that belongs in a separate file.
Suggestions
Trim the opening product/marketing paragraph to one sentence of integration-relevant context only.
Add an explicit validation/confirmation step before destructive actions, e.g. verify the invoice exists and confirm with the user before running delete-invoice/delete-customer.
Move the Popular actions reference table into a separate references/ file and link to it from the overview to improve progressive disclosure.
Include at least one concrete end-to-end action example with real parameters (e.g. create-invoice with actual customer/amount fields) instead of the generic {"key": "value"} placeholder.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The bulk is lean, executable CLI commands and genuinely useful state-handling detail, but the opening paragraph ("accounting and bookkeeping software... affordable and easy-to-use accounting solution") and phrases like "so you can focus on the integration logic rather than auth plumbing" are product/marketing padding Claude does not need. Mostly efficient with some unnecessary explanation. | 3 / 5 |
Actionability | Commands are concrete and copy-paste-ready (install, login, connection ensure/get, action list/run, request) with flags explained. Held below 5 because action-invocation examples use abstract placeholders ("--input '{\"key\": \"value\"}'", "<actionId>") rather than a concrete end-to-end example with real fields. | 4 / 5 |
Workflow Clarity | The connect-and-poll workflow has explicit state checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED) and a re-poll feedback loop, but the skill exposes destructive operations (delete-invoice, delete-customer) run via the generic `membrane action run` with no validation or confirmation step. The destructive-operations cap holds this at 3. | 3 / 5 |
Progressive Disclosure | The skill is a single ~160-line file with no bundle files, and the 20-row Popular actions table plus the proxy-flags table are reference-style content inlined in the overview rather than split into a separate reference file. Structure is reasonable, but content that should be separate is inline with no one-level-deep references. | 3 / 5 |
Total | 13 / 20 Passed |