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 strongly actionable CLI reference with real copy-paste commands and a well-handled connection state machine, but it is padded in places and ships destructive GDPR delete actions with no validation guardrails. Organization is good, though the dangling "Step 2" reference and inconsistent membrane/npx invocations leave minor workflow gaps.
Suggestions
Add an explicit validation step before destructive actions: for "bulk-delete-contacts-gdpr" and "delete-contact-gdpr", confirm the target contacts with the user and verify the selection (e.g. via get-contact) before running, and re-check the result afterward.
Cut the AskNicely marketing intro and the content-free "AskNicely Overview" section; Claude does not need to be told the product's positioning, only the commands.
Fix the "skip to Step 2" dangling reference by naming the target section, and make command invocations consistent (choose either "membrane" or "npx @membranehq/cli" for the polling example).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly command-and-table content, but the intro ("AskNicely is a customer experience platform that helps businesses measure and improve customer satisfaction..."), the near-empty "AskNicely Overview" list ("Use action names and parameters as needed"), and wordy best-practices prose ("This will burn less tokens and make communication more secure") could all be trimmed. Not 4 because several sections add tokens without adding guidance Claude doesn't have. | 3 / 5 |
Actionability | Concrete, copy-paste-ready commands throughout ("membrane connection ensure", "membrane action run <actionId> --connectionId=... --input '{...}'"), plus a flags table and a popular-actions table with keys and descriptions. Not 5 because "membrane login --tenant --clientName=<agentType>" is not executable as written and the polling example inconsistently uses "npx @membranehq/cli" where other steps use "membrane". | 4 / 5 |
Workflow Clarity | The install → login → connect → poll → search → run sequence is clear and the connection-state polling loop (BUILDING/CLIENT_ACTION_REQUIRED/READY with "poll again with membrane connection get") is a genuine feedback loop. Capped at 3 per the destructive/batch rule: the skill surfaces "Bulk Delete Contacts (GDPR)" and "Delete Contact (GDPR)" — permanently destructive batch operations — with no validation, confirmation, or verification guidance, and the "skip to Step 2" reference points at a step that is never labeled. | 3 / 5 |
Progressive Disclosure | No bundle files exist and the ~150-line body is organized into clear sections (Install, Authentication, Connecting, Searching, Popular actions, Running, Proxy, Best practices) with appropriately inline tables. Not 5 because the document exceeds the under-50-lines simple-skill case and the popular-actions and proxy-flag tables could live in a reference file to keep the overview leaner. | 4 / 5 |
Total | 14 / 20 Passed |