Content
61%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 provides genuinely executable CLI guidance with a well-handled connection state machine, but it is undermined by a dangling "Step 2" reference, an empty "Popular actions" section, inconsistent command invocation styles, and a few marketing-fluff sentences that waste tokens. Fixing the broken workflow navigation and tightening the prose are the highest-leverage improvements.
Suggestions
Fix the dangling navigation: "skip to Step 2" points nowhere — either number the sections explicitly (1. Connect, 2. Discover actions, 3. Run) or link directly to "Searching for actions".
Trim padding sentences such as "It's used by businesses and individuals looking for transparent and efficient ad buying and selling" and "This is the fastest way to get a connection" to reduce token spend.
Either populate "Popular actions" with 3-5 concrete example invocations for common AdShares tasks (campaign creation, wallet balance, transaction lookup) or remove the empty heading; also standardize on one invocation form ("membrane" vs "npx @membranehq/cli").
Add brief error-handling guidance for "membrane action run" failures so the run step has a validation checkpoint.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is mostly efficient commands with brief explanations, but includes unnecessary padding such as "It's used by businesses and individuals looking for transparent and efficient ad buying and selling" and "This is the fastest way to get a connection", matching 'Mostly efficient but includes some unnecessary explanation or could be tightened'. Not a 2 because the padding is limited to a few sentences rather than whole padded sections. | 3 / 5 |
Actionability | Concrete executable commands appear throughout ("npm install -g @membranehq/cli@latest", "membrane connection ensure \"https://adshares.net\" --json", the proxy flags table), matching 'Mostly executable guidance with minor gaps'. Not a 5 because the invocation style is inconsistent ("membrane" vs "npx @membranehq/cli"), the "Popular actions" section lists no actual actions, and there are no worked example invocations. | 4 / 5 |
Workflow Clarity | A sequence exists (install CLI → login → connection ensure → poll for READY → search actions → run actions) with state-machine checkpoints for connection states, but "skip to Step 2" points to a Step 2 that never appears in the document, and there is no error-handling or validation guidance after running an action, matching 'Steps listed but validation gaps; sequence present but checkpoints missing or implicit'. Not a 4 because the dangling cross-reference and absent post-run verification are more than minor gaps. | 3 / 5 |
Progressive Disclosure | The body is well-sectioned with clear headers, no nested references, and no bundle files exist so nothing is mis-filed; however inline detail such as the clientAction specification and the proxy flags table could be moved to reference files and the "Popular actions" section is an empty shell, matching 'Good structure; most content appropriately placed; minor organization gaps'. | 4 / 5 |
Total | 14 / 20 Passed |