Content
71%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 content is a strong, executable guide: concrete CLI commands cover install, auth, connection lifecycle (including state polling and error handling), action discovery/execution, and a proxy fallback. Main weaknesses are the broken internal step references ("Step 2", "1b"), inconsistent membrane/npx invocation, and a monolithic structure where connection-state details and proxy reference could live in separate files.
Suggestions
Fix the internal navigation: either add explicit numbered steps (1. Connect, 2. Discover actions, 3. Run) so "skip to Step 2" and "1b" resolve, or replace those references with the actual section names.
Standardize CLI invocation (pick `membrane` after install or `npx @membranehq/cli` consistently) across all examples, including the connection get polling commands.
Move the connection clientAction state-machine details and the proxy flags table into a reference file (e.g., references/connection-states.md, references/proxy.md) to shrink the SKILL.md overview.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is command-dense with little conceptual padding (it explains Membrane, which Claude genuinely doesn't know). Minor trimmable filler remains: "Use action names and parameters as needed." and the rambling Agent Types note. Not 5 because of these small unnecessary passages. | 4 / 5 |
Actionability | Nearly every section gives copy-paste-ready commands (npm install, membrane login, connection ensure, action list/run, request with a full flags table). Not 5 because CLI invocation is inconsistent (bare `membrane` vs `npx @membranehq/cli`) and "skip to Step 2" points at a heading that doesn't exist, leaving minor gaps to resolve before running. | 4 / 5 |
Workflow Clarity | The install → login → connect → search → run sequence is clear, with state-based checkpoints (poll BUILDING, handle CLIENT_ACTION_REQUIRED, check the error field on CONFIGURATION_ERROR/SETUP_FAILED). Not 5 because the step numbering is incoherent — "skip to Step 2" and heading "1b" reference a numbered scheme that isn't in the document — which muddies navigation between phases. | 4 / 5 |
Progressive Disclosure | Sections are well-organized headers, but the ~140-line body is fully monolithic with zero bundle files; content that naturally belongs in references (the connection clientAction state machine, the proxy request flags table) is inlined. Not 4 because there is no offloading at all, and the body exceeds the size where sectioning alone suffices. | 3 / 5 |
Total | 15 / 20 Passed |