Content
67%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, executable runbook: real commands, explicit state-machine handling for connection setup, and sensible best practices. Its weaknesses are a padded intro/overview (concept explanation Claude doesn't need), a broken "Step 2" cross-reference from a renumbered workflow, and inconsistent CLI invocation (`membrane` vs `npx @membranehq/cli`).
Suggestions
Delete the opening "ChartIQ is a financial charting library..." paragraph and the content-free "ChartIQ Overview" tree, or replace them with a two-line note of what the skill does that Claude doesn't already know.
Fix the broken navigation: renumber the connection steps (Step 1: create, Step 1b: wait, Step 2: search/run actions) so "skip to Step 2" resolves, and standardize on one invocation form (`membrane` vs `npx @membranehq/cli`).
Clarify placeholders: document what `--tenant` expects in `membrane login` and show one concrete `action list`/`action run` example with a realistic ChartIQ action id and input.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The bulk is efficient CLI instruction, but two sections are pure padding: the opening "ChartIQ is a financial charting library and data visualization tool. It's used by financial institutions, brokers, and trading platforms" explains background Claude already knows, and the near-empty "ChartIQ Overview" section ("**Chart** / **Drawing Tool** / **Study** — Use action names and parameters as needed") adds nothing. Mostly efficient, but the filler could be trimmed. | 3 / 5 |
Actionability | Concrete, executable commands throughout: `npm install -g @membranehq/cli@latest`, `membrane login complete <code>`, `membrane connection ensure "https://chartiq.com" --json`, `membrane action run <actionId> --input '{"key": "value"}' --json`, plus a full flags table for proxy requests. Minor gaps: the vague "Use action names and parameters as needed" line and the unexplained `--tenant` placeholder in the login command. | 4 / 5 |
Workflow Clarity | The connection workflow has real checkpoints and error recovery: poll with `--wait` until state leaves `BUILDING`, branch on `READY` / `CLIENT_ACTION_REQUIRED` (with documented `clientAction` handling and re-poll) / `CONFIGURATION_ERROR` or `SETUP_FAILED` (check `error` field). Not 5 because "skip to **Step 2**" references a section that doesn't exist — headings are "1b. Wait for the connection" with no numbered Step 1 or 2, which breaks the sequence. | 4 / 5 |
Progressive Disclosure | A single self-contained file with no bundle files and a logical section flow (install → authenticate → connect → discover/run actions → proxy → best practices); at ~140 lines nothing clearly needs offloading to separate files, and navigation is easy. Minor gaps: the placeholder "ChartIQ Overview" tree is content-free, and the leftover "1b" numbering suggests a removed step. | 4 / 5 |
Total | 15 / 20 Passed |