Content
68%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 highly actionable, command-first integration guide with good connection-state feedback loops and a clean single-file structure. Its main defects are broken internal navigation (an undefined "Step 2" and an unanchored "1b") that confuses the workflow, plus a small amount of filler (the duplicated entity overview and Membrane implementation details) that could be trimmed or externalized.
Suggestions
Fix the dangling references: define "Step 2" (e.g., label the action-search/run sections as steps) or rewrite "skip to Step 2" as "skip to Searching for actions", and rename "1b" so it follows an explicitly numbered step 1.
Remove or compress the "Agiled Overview" bullet list, which duplicates **Task** and is followed by the meaningless instruction "Use action names and parameters as needed.".
Show one complete worked example from `membrane action list` output (with a real action id) through `membrane action run <actionId> --input ...` so the placeholder-to-execution flow is unambiguous, and reconcile the global `npm install -g` with the later `npx @membranehq/cli` usage.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is overwhelmingly command-driven with minimal concept explanation, but contains trimmable padding: the "Agiled Overview" bullet list (with a duplicated **Task** entry and the filler line "Use action names and parameters as needed.") and Membrane-internal details like "The URL is normalized to a domain and matched against known apps." This fits anchor 4 (efficient, minor over-explanation) better than 3, since the padding is a small fraction of the document. | 4 / 5 |
Actionability | Nearly every section gives copy-paste-ready commands: `npm install -g @membranehq/cli@latest`, `membrane login --tenant --clientName=<agentType>`, `membrane connection ensure "https://agiled.app/" --json`, `membrane action run <actionId> --connectionId=... --input '{...}'`, plus a concrete proxy flag table. Not 5 because the flow from `action list` results to a concrete `<actionId>` value in `action run` is never shown end-to-end, and the install uses the global CLI while later invoking `npx @membranehq/cli` inconsistently. | 4 / 5 |
Workflow Clarity | A real sequence exists (install → login → connect → poll for READY → search actions → run → proxy) with good state-feedback loops for BUILDING/CLIENT_ACTION_REQUIRED (re-poll instructions), but it is undermined by dangling navigation: "skip to **Step 2**" is referenced twice yet no Step 2 exists anywhere, and section "1b. Wait for the connection" has no corresponding labeled step 1. This matches anchor 3 (sequence present but with gaps) rather than 4, where only validation — not structural references — would be missing. | 3 / 5 |
Progressive Disclosure | A single well-sectioned SKILL.md with clear headers, one-level-deep content, and no nested references (no bundle files exist, which is acceptable at this size). Minor organization gaps keep it at anchor 4 rather than 5: the 21-row popular-actions table and the proxy options reference are bulk reference material that could live in separate files, and the confusing "Agiled Overview" section adds little navigational value. | 4 / 5 |
Total | 15 / 20 Passed |