Conciseness

The opening paragraph pads with marketing-style background Claude doesn't need ("It provides tools for product management, order processing, marketing, and customer relationship management. It's used by small to medium-sized businesses looking to sell products online"), and lines like "Use action names and parameters as needed." are pure filler. This matches anchor 3 ("Mostly efficient but includes some unnecessary explanation or could be tightened"): not 2 because the bulk is command-focused with little other padding, not 4 because the intro and filler go beyond minor trimming.

Actionability

The guidance is copy-paste ready throughout: "npm install -g @membranehq/cli@latest", "membrane connection ensure \"https://cloudcart.com/\" --json", "membrane action run <actionId> --connectionId=CONNECTION_ID --input '{\"key\": \"value\"}' --json", plus a concrete 20-action table and a proxy flags table. Placeholders like CONNECTION_ID are explicitly marked, and the common cases (connect, search, run, proxy) are each covered. No gaps found, so it matches anchor 5 rather than 4.

Workflow Clarity

A real sequence exists (install → login → connect → search → run) and connection-state handling has explicit checkpoints (poll with --wait, act on CLIENT_ACTION_REQUIRED, inspect CONFIGURATION_ERROR). But "skip to **Step 2**" references a step that is never labeled anywhere in the document, and the create/update actions have no verification step, which caps this at 3 per the destructive/batch validation rule. Not 4 because of the dangling step references and missing write-verification; not 2 because the sequence and several checkpoints are present and coherent.

Progressive Disclosure

No bundle files exist, and the single-file body is well-sectioned (Install, Authentication, Connecting, Searching, Popular actions, Running, Proxy, Best practices) with no buried or nested references — everything is one level deep at most. This matches anchor 4 ("Good structure; most content is appropriately placed"): not 5 because at ~160 lines the 20-row action catalog and proxy flag table could be split into a reference file to keep the overview lean; not 3 because nothing is buried and organization is solid.

Specificity

The description names the domain ("CloudCart integration") but its actions are generic — "Manage data, records, and automate workflows" is vague, with "automate workflows" reading as buzzword. It matches anchor 2 ("Names the domain but actions are minimal or generic"): not 1 because the domain is named with some action wording, not 3 because it never states concrete actions like managing products, orders, or customers.

Completeness

Both parts are explicitly present: a what ("Manage data, records, and automate workflows") and an explicit when ("Use when the user wants to interact with CloudCart data"). It matches anchor 4 rather than 5 because the what is vague and the when offers no concrete trigger phrases beyond "CloudCart data"; not 3 because the when is explicit, not merely implied.

Trigger Term Quality

"CloudCart" is the primary natural term a user would say and it appears in the trigger clause "Use when the user wants to interact with CloudCart data", but common variations are missing — no mention of orders, products, customers, online store, or e-commerce. This matches anchor 3 ("Some relevant keywords but missing common variations or synonyms"): not 2 because the key natural term is present, not 4 because coverage beyond the platform name is thin.

Distinctiveness Conflict Risk

"CloudCart" names a specific e-commerce platform and the trigger is tied to it ("interact with CloudCart data"), creating a clear niche with minimal conflict risk against other skills. Not 4: there is no meaningful overlap — the distinct platform name does the differentiating work.