Content
57%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 strong operational guide for the Membrane CLI workflow: executable install/auth/connect/run commands, a useful actions catalog, and solid connection error-handling. Its main weaknesses are generic filler sections, dangling step references ('skip to Step 2', '1b' with no '1a'), an actions table with an empty Description column, and everything being inlined with no reference files for the bulk API material.
Suggestions
Fix the broken sequence references: label the workflow steps explicitly (Step 1, Step 2...) so 'skip to Step 2' and '1b' resolve, or convert them to section-name links.
Populate the empty Description column of the Popular actions table (or remove it) and add one worked end-to-end example with realistic values (connect → find action → run with --input).
Trim the conceptual filler — the 'who uses AskYourPDF' intro, the unexplained entity tree, and 'Use action names and parameters as needed.' — and consider moving the action catalog and proxy flag reference into a separate reference file.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is mostly operational commands, but it pads with content Claude doesn't need: the marketing-style app intro ('primarily used by students, researchers, and professionals'), an unexplained entity tree (PDF Document → Pages, Chat History, Annotations) that instructs nothing, and filler like 'Use action names and parameters as needed.' This matches anchor 3 ('mostly efficient but includes some unnecessary explanation'), not 4, because several such sections would need trimming. | 3 / 5 |
Actionability | The skill gives concrete, executable commands throughout — 'npm install -g @membranehq/cli@latest', 'membrane connection ensure "https://askyourpdf.com/" --json', 'membrane action run <actionId> --connectionId=... --input ...', plus a full proxy flags table. It falls short of anchor 5 because the Popular actions table has an entirely empty Description column and there is no worked end-to-end example with realistic values. | 4 / 5 |
Workflow Clarity | The implicit sequence (install → login → connect → poll/error-handle → search actions → run → proxy fallback) is present with genuinely good error-recovery for the connection flow (BUILDING polling, CLIENT_ACTION_REQUIRED handling, CONFIGURATION_ERROR guidance). However, 'skip to **Step 2**' references a step that is never labeled, and '#### 1b.' has no corresponding '1a'/Step 1 heading — dangling references that break navigation, matching anchor 3 rather than 4. | 3 / 5 |
Progressive Disclosure | Section headers are clear and there are no nested references, but the ~175-line body inlines everything — including a 17-row API-style action table and a full proxy flag reference that would fit better in separate reference files. With no bundle files present and no external references, this matches anchor 3 ('some structure... content that should be separate is inline'), not 4. | 3 / 5 |
Total | 13 / 20 Passed |