Content
63%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 delivers strong, executable Membrane CLI guidance with a sensible workflow and good state-handling coverage. Its main weaknesses are the content-free overview section, the empty-descriptions actions table, and dangling "Step 2" references that hurt both conciseness and navigation.
Suggestions
Cut the content-free "Ascora Overview" section and the filler line "Use action names and parameters as needed.", or replace them with a one-line statement of what Ascora entities the actions cover.
Fill in or remove the empty Description column in the "Popular actions" table (e.g., "mark-payments-sent — batch-mark selected invoices/payments as sent"), and add one complete worked example such as a full `membrane action run list-payments` command with real input and output.
Fix the broken step references: either label the workflow steps explicitly (Step 1: connect, Step 2: search actions, ...) and define where "Step 2" points, or drop the step numbering entirely; consider moving the actions catalog and proxy flag table into a references/ file.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The CLI instructions are mostly efficient, but the "Ascora Overview" section is content-free filler ("Use action names and parameters as needed.") and the "Popular actions" table has entirely empty Description columns, wasting tokens. Fits anchor 3 ("Mostly efficient but includes some unnecessary explanation or could be tightened"); not 4 because these padded sections are clearly trimmable. | 3 / 5 |
Actionability | Concrete copy-paste commands appear throughout ("npm install -g @membranehq/cli@latest", "membrane connection ensure \"https://www.ascora.com.au/\" --json", "membrane action list --connectionId=CONNECTION_ID --intent \"QUERY\" --limit 10 --json") with a full proxy flag table. Not 5: no worked end-to-end example with real action IDs or inputs — the parameter example is the placeholder '{"key": "value"}' and action descriptions are blank. | 4 / 5 |
Workflow Clarity | A clear setup-to-usage sequence (install → login → connection ensure → poll until READY → handle clientAction → search/run actions → proxy fallback) with validation checkpoints (state polling, clientAction fields, error handling on CONFIGURATION_ERROR). Not 5: "skip to **Step 2**" is referenced twice but no Step 2 is ever defined, and the "#### 1b" heading implies an unlabeled step 1, leaving minor coherence gaps. | 4 / 5 |
Progressive Disclosure | The skill is a single ~145-line file with clear section headers but no bundle files; the auto-generated "Popular actions" table and the proxy flags reference would fit a references/ file, and the overview section carries no navigational value. Fits anchor 3 ("Some structure but could be better organized ... content that should be separate is inline"); not 4 because of the broken step numbering and inline reference material. | 3 / 5 |
Total | 14 / 20 Passed |