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.
A generally actionable, well-commanded skill whose connection setup workflow includes genuine state-checkpoint handling. Its main weaknesses are padding around the overview, a destructive/batch action catalog with no verification guidance, and internal references to a nonexistent "Step 2".
Suggestions
Add a validation step before destructive actions (delete-customer, cancel-subscription, refund-invoice, void-invoice), e.g. confirming the target ID with the user or re-fetching the record before and after running.
Fix the two "skip to **Step 2**" references by renaming the target section ("Searching for actions") to Step 2 or updating the pointers.
Trim the introductory paragraph and the bare "Chargebee Overview" bullet list, which explain things Claude already knows and add no actionable detail.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is mostly efficient commands and tables, but includes unnecessary padding: the introductory paragraph "Chargebee is a subscription billing and revenue management platform. It helps SaaS and subscription-based businesses automate recurring billing...", the hollow "Chargebee Overview" bullet list (Customer/Subscription/Plan/Addon/Coupon with no explanations), and Membrane internals prose like "The URL is normalized to a domain and matched against known apps". | 3 / 5 |
Actionability | Concrete, copy-paste-ready CLI commands throughout ("npm install -g @membranehq/cli@latest", "membrane connection ensure", "membrane action run ... --input '{\"key\": \"value\"}'"), with only minor gaps: "membrane login --tenant --clientName=<agentType>" never shows what value --tenant takes, and <actionId> is never shown being resolved from action list output. Not 5 because of these executable gaps; not 3 because everything given is runnable, not pseudocode. | 4 / 5 |
Workflow Clarity | The connection workflow has a good state-based decision tree (READY / BUILDING / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR with polling), but the text twice says "skip to **Step 2**" while no Step 2 heading exists, and the action catalog includes destructive operations (Delete Customer, Cancel Subscription, Refund Invoice, Void Invoice) with no validation/verification guidance — the rubric's destructive-operation cap of 3 applies. | 3 / 5 |
Progressive Disclosure | Single-file skill (no bundle files present) with well-organized sections (Install, Authentication, Connecting, Searching, Running, Proxy, Best practices) and compact inline tables (Popular actions, proxy flags). Not 5 because the dangling "Step 2" references and the 20-row action catalog inlined in the main file are minor organization gaps; not 3 because nothing that clearly belongs in a separate file is buried. | 4 / 5 |
Total | 14 / 20 Passed |