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 skill delivers genuinely actionable CLI guidance with a solid polling/feedback model for connection states, but is undermined by an incoherent step structure (dangling 'Step 2', orphaned '1b', empty 'Popular actions') and padded introductory sections. Tightening the workflow numbering and trimming boilerplate would lift it substantially.
Suggestions
Fix the workflow numbering: define the steps explicitly (1. Install, 2. Authenticate, 3. Connect, 4. Discover actions, 5. Run) so references like 'skip to Step 2' resolve to real sections.
Populate 'Popular actions' with actual example action names (e.g. list/search conversations, send message, update user) or remove the empty section.
Trim the introductory prose (the 'what is CommBox' paragraph and the Overview bullet list with 'Use action names and parameters as needed') and standardize on one CLI invocation form (`membrane` vs `npx @membranehq/cli`).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is mostly efficient commands and tables, but contains unnecessary prose ("CommBox is a customer communication platform. It's used by businesses to manage and respond to customer inquiries...") and a vacuous Overview section ending in "Use action names and parameters as needed". Not 4 because these padded sections and filler sentences could be trimmed without losing information. | 3 / 5 |
Actionability | Concrete, copy-paste-ready commands cover install, login, headless auth, connection setup, polling, action discovery, action execution, and proxy requests, plus a flags table. Not 5 because invocation is inconsistent (`membrane` vs `npx @membranehq/cli`), the 'Popular actions' section contains no actual actions, and the referenced 'Step 2' does not exist. | 4 / 5 |
Workflow Clarity | The install → login → connection → poll → discover → run sequence exists with state-based checkpoints (READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR with re-poll instructions), but the flow references a 'Step 2' that is never defined, has an orphaned '1b' heading, and the 'Popular actions' section is empty. These gaps in an otherwise present sequence match 'steps listed but validation gaps; sequence present but checkpoints missing or implicit' more than the cleaner anchor 4. | 3 / 5 |
Progressive Disclosure | The single-file skill (no references/, scripts/, or assets/ exist) is organized into clear sections (Install, Authentication, Connecting, Searching, Running, Proxy, Best practices) with no nested or dangling file references. Not 5 because at ~140 lines, content like the proxy flag table and clientAction schema could be split out, and the section ordering is slightly jumbled (Running actions appears under Popular actions). | 4 / 5 |
Total | 14 / 20 Passed |