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.
A generally actionable, well-structured integration guide whose connection-handling workflow is unusually thorough. The main weaknesses are workflow loose ends — a broken "Step 2" cross-reference, inconsistent command forms, and no validation guidance for the destructive delete actions the skill advertises.
Suggestions
Fix the broken cross-reference ("skip to **Step 2**" points to a step that is never labeled) and unify the polling command form, which currently switches between "npx @membranehq/cli connection get" and "membrane connection get".
Add validation guidance for destructive operations, e.g. verify the record with get-contact-by-id before running delete-contact, or confirm with the user before any delete action.
Clarify the relationship between the Popular actions "Key" (e.g. create-contact) and the <actionId> required by "membrane action run", and include one full example invoking a real Agile CRM action with a realistic payload.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The bulk is efficient executable commands and tables, with only minor trimmable prose such as the opening paragraph explaining what a CRM is ("Agile CRM is a customer relationship management platform used by sales and marketing teams..."), the filler line "Use action names and parameters as needed", and "so you can focus on the integration logic rather than auth plumbing". | 4 / 5 |
Actionability | Provides copy-paste-ready commands throughout ("membrane connection ensure", "membrane action run <actionId> --connectionId=CONNECTION_ID --input '{\"key\": \"value\"}' --json") plus a proxy flags table, but the Popular actions table lists a "Key" (e.g. create-contact) while the run command requires an <actionId> and no end-to-end example with a real payload is given. | 4 / 5 |
Workflow Clarity | The install → login → connection → search → run sequence is present and the connection-state feedback loop (READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR) is well handled, but "skip to **Step 2**" references a step that is never labeled, the polling command switches between npx and membrane forms, and destructive operations (delete-contact, delete-company, delete-deal, delete-task) have no validation or verification guidance, capping this dimension at 3. | 3 / 5 |
Progressive Disclosure | Well-organized single-file structure with clear section headers and no nested references, but the 20-row Popular actions table is API-reference material inlined in SKILL.md that could live in a separate reference file, and the skill exceeds the simple-skill line length. | 4 / 5 |
Total | 15 / 20 Passed |