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 is a solid, command-dense integration guide with good state-handling for connection setup and a sensible action-first-then-proxy escalation path. Its main defects are a dangling "Step 2" reference with incoherent step numbering, a filler overview section, and inconsistent CLI invocation forms.
Suggestions
Define or renumber the steps: the text says "skip to Step 2" twice but no Step 2 exists, and "1b" has no "1" — replace with explicit numbered headings (1. Connect, 2. Discover actions, 3. Run actions) or drop the step labels.
Delete the "## Cirrus Labs Overview" section and the Membrane-internals explanation of URL normalization; keep only the one-line platform identification.
Add a brief error-recovery example for action runs or proxy failures (e.g., what to do on CONFIGURATION_ERROR / expired credentials), and pick one canonical invocation form (`membrane` vs `npx @membranehq/cli`).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The commands and code blocks are lean, but there are several unnecessary or padded passages: the bare "## Cirrus Labs Overview" hierarchy (Project/Issue/Document/User plus "Use action names and parameters as needed") carries no actionable value, "This is the fastest way to get a connection. The URL is normalized to a domain and matched against known apps" explains Membrane internals, and the auth-plumbing reassurance line is filler. This matches anchor 3 ("mostly efficient but includes some unnecessary explanation or could be tightened"); it exceeds anchor 2's threshold of pervasive padding but is not 4's "minor instances only". | 3 / 5 |
Actionability | The body provides mostly executable, copy-paste-ready commands with concrete flags and placeholders: `npm install -g @membranehq/cli@latest`, `membrane login complete <code>`, `membrane connection ensure "https://cirrus-ci.org/" --json`, `membrane action run <actionId> --input '{"key": "value"}'`, plus a complete proxy flag table. Anchor 4 ("mostly executable guidance with minor gaps") rather than 5, because "Step 2" is referenced but never defined and the invocation form inconsistently alternates between `membrane` and `npx @membranehq/cli`. | 4 / 5 |
Workflow Clarity | A real sequence exists (install → login → ensure connection → poll state → handle clientAction → search/run actions → proxy fallback) with a state-machine branch for READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR and a polling loop, but "skip to **Step 2**" appears twice with no Step 2 defined, a "1b" subsection exists with no "1" or "2", and error recovery is just "Check the `error` field for details". Anchor 3 ("sequence present but checkpoints missing or implicit") rather than 4, because the broken step references make the multi-step flow genuinely hard to follow. | 3 / 5 |
Progressive Disclosure | There are no bundle files (no references/, scripts/, or assets/), and this single-file skill (~140 lines) is organized into clearly headed, appropriately sized sections with no monolithic wall of text. Anchor 4 ("good structure; most content appropriately placed; minor organization gaps") rather than 5, because the content exceeds the sub-50-line simple-skill case and contains the filler overview section and dangling step labels. | 4 / 5 |
Total | 14 / 20 Passed |