Conciseness

The body is command-driven with concrete bash blocks for every operation. Only minor trimmable material exists: the value-proposition prose ("This eliminates the need to develop and maintain individual integrations for each platform"), the information-free "API2Cart Overview" bullet tree (Cart/Product/Category/Customer/Order with no guidance), and the duplicated discovery command under "Popular actions". This fits 'Efficient; minor instances of over-explanation that could be trimmed' — the brief API2Cart intro itself is justified since it is a niche API Claude may not know.

Actionability

Every core flow has copy-paste-ready commands: "npm install -g @membranehq/cli@latest", "membrane login complete <code>" for headless auth, "membrane connection ensure \"https://api2cart.com/\" --json", "npx @membranehq/cli connection get <id> --wait --json", "membrane action run <actionId> --connectionId=CONNECTION_ID --input '{\"key\": \"value\"}' --json", plus a complete proxy flag table. Placeholders (CONNECTION_ID, QUERY) are introduced by the preceding discovery steps, matching 'Fully executable; copy-paste ready commands; specific examples cover the common cases'.

Workflow Clarity

There is a clear sequence (install → login → connection ensure → poll state → discover actions → run → proxy) with explicit checkpoints: --wait long-polling, a fully spelled-out clientAction state machine, and error handling for CONFIGURATION_ERROR/SETUP_FAILED. However, "If the returned connection has state: \"READY\", skip to **Step 2**" references a step that does not exist (the only numbered heading is an orphaned "1b"), and "Popular actions" is a stub heading with no actions. This fits 'Clear sequence with most checkpoints present; minor validation gaps' rather than level 5.

Progressive Disclosure

No bundle files exist and none are claimed; the single-file body is appropriately sectioned (Install, Authentication, Connecting, Searching, Running actions, Proxy requests, Best practices) with no nested or dead references — everything is one level deep and inline content is reasonably sized for a CLI-driven skill. Minor organization gaps (the stub "Popular actions" section and the empty Overview tree) keep it at 'Good structure; most content is appropriately placed; minor organization gaps' rather than 5.

Specificity

The description names the domain ("API2Cart integration") but the actions are purely generic — "Manage data, records, and automate workflows" — with no concrete API2Cart operation (no 'sync products', 'fetch orders', 'list customers'). This matches the anchor 'Names the domain but actions are minimal or generic' and falls below the level-3 anchor, which requires 1-2 concrete actions.

Completeness

Both parts are explicitly present: 'what' = "API2Cart integration. Manage data, records, and automate workflows" and 'when' = "Use when the user wants to interact with API2Cart data". However the 'when' clause is circular — it restates the domain name instead of giving concrete trigger phrases — so it fits 'Has both what and when; when could be more explicit or specific' rather than the level-5 anchor requiring concrete triggers.

Trigger Term Quality

"API2Cart" is a strong, relevant domain keyword, but it is essentially the only one — the natural phrases a user would say (shopping platforms, e-commerce integration, Shopify, Magento, WooCommerce, syncing orders/products) are all missing. This matches 'Some relevant keywords but missing common variations or synonyms'; it is above level 2 because the keyword present is the domain's own name rather than generic filler like 'Works with files'.

Distinctiveness Conflict Risk

The API2Cart brand name carves out a clear niche and the trigger is keyed to it, giving minimal conflict risk. It is not level 5 because the descriptive half ("Manage data, records, and automate workflows") is generic enough to overlap with broad data-management skills, fitting 'Mostly distinct; minor overlap risk with closely related skills'.