Conciseness

The body is dominated by copy-paste commands and compact tables, with only minor over-explanation that could be trimmed — the two-sentence intro on what Campayn is and the rambling "Agent Types : claude, openclaw, codex, warp, windsurf, etc." line. Matches anchor 4 (efficient, minor instances of over-explanation); not 5 because these padded passages exist and "This is the fastest way to get a connection..." explains more than strictly needed.

Actionability

Fully executable bash throughout: "npm install -g @membranehq/cli@latest", "membrane connection ensure \"https://www.campayn.com\" --json", "npx @membranehq/cli connection get <id> --wait --json", and "membrane action run <actionId> --connectionId=CONNECTION_ID --input '{\"key\": \"value\"}' --json", plus a proxy flags table. Covers the common cases (search, run, proxy); no gaps, matching anchor 5.

Workflow Clarity

Clear sequence (install → login with headless fallback "membrane login complete <code>" → connection ensure → poll --wait) with explicit state-based branching (READY / CLIENT_ACTION_REQUIRED with uiUrl and agentInstructions, CONFIGURATION_ERROR / SETUP_FAILED with error-field checks) and a re-poll feedback loop after the user completes an action. Matches anchor 4; not 5 because "skip to **Step 2**" references a step that is never labeled, and no guidance covers a failed action run.

Progressive Disclosure

No bundle files exist; the single file is well-sectioned (Install, Authentication, Connecting, Searching, Popular actions, Running, Proxy, Best practices) and defers bulk API detail to the live "membrane action list" discovery mechanism rather than inlining it. Matches anchor 4 (good structure, minor gaps); not 5 because the file exceeds 50 lines and the 10-row actions table plus clientAction schema detail are candidates for a reference file.

Specificity

"Campayn integration" names the domain, but the only actions offered are the generic "Manage data, records, and automate workflows" — no concrete operations like creating contacts or sending email campaigns. This matches anchor 2 ("Names the domain but actions are minimal or generic"); it is not 3 because no concrete, app-specific action is listed.

Completeness

It has both a 'what' ("Campayn integration. Manage data, records, and automate workflows") and an explicit 'when' ("Use when the user wants to interact with Campayn data"), but the 'when' is vague — comparable to the anchor-4 example "Use when working with PDF files". Not 5 because the trigger phrase lacks concrete, specific terms.

Trigger Term Quality

The only keywords are the brand name "Campayn" and generic terms ("data", "records", "workflows"); the natural phrases a user would say for this domain — email marketing, newsletters, mailing lists, campaigns, subscribers — are absent. Matches anchor 2 (one or two generic keywords, missing the natural phrases users say).

Distinctiveness Conflict Risk

"Campayn" is a distinct brand name, so the trigger is unlikely to fire for unrelated skills. Minor overlap risk remains with sibling Membrane app-integration skills that share the identical template wording ("Manage data, records, and automate workflows. Use when the user wants to interact with X data"), which matches anchor 4.