Conciseness

The body is mostly lean, command-first content with a dense flag table and little padding. Minor instances of over-explanation could be trimmed — the opening paragraph explaining what ActBlue is and who uses it ('ActBlue is an online fundraising platform for Democratic candidates... It's primarily used by Democratic campaigns, progressive non-profits...') is background Claude already knows, and the 'Agent Types' aside is awkwardly written. This matches anchor 4 rather than 3 because the padding is minor relative to the document's overall density.

Actionability

Concrete, copy-paste-ready commands cover the full path: 'npm install -g @membranehq/cli@latest', 'membrane connection ensure "https://secure.actblue.com/" --json', and 'membrane action run <actionId> --connectionId=CONNECTION_ID --input {...} --json', plus a proxy flag table. It matches anchor 4 rather than 5 because no ActBlue-specific example appears — every action example uses placeholders or a generic '{"key": "value"}' input instead of a realistic contribution query, so the common cases are not covered.

Workflow Clarity

The setup sequence (install → login → connection ensure → poll/branch by state → search actions → run) is clear, with an explicit state-branching feedback loop for connection readiness ('CLIENT_ACTION_REQUIRED — the user or agent needs to do something' followed by 'poll again with membrane connection get <id> --json to check if the state moved to READY'). It is anchor 4 rather than 5 because 'Step 2' is referenced twice ('skip to Step 2') but never defined, and the core action-run and proxy steps have no error-handling or output-validation guidance.

Progressive Disclosure

A single ~150-line file with clear section headers ('## Working with Actblue', '### Proxy requests', '## Best practices') and appropriately scoped content; no bundle files exist and none are strictly required. This matches anchor 4's 'good structure; most content appropriately placed' — it is not 5 because the under-50-line simple-skill exception does not apply, and detail-heavy material such as the clientAction state reference and the proxy flag table would sit naturally in a separate reference file.

Specificity

It names the domain ('Actblue integration') and enumerates a few capability areas ('Manage data, records, and automate workflows'), but every action phrase is generic — no concrete operations like 'search contributions' or 'manage recurring donation series'. This sits between anchor 2 (actions minimal or generic) and anchor 3 (1-2 concrete actions), landing at 3 because multiple capability areas are at least enumerated.

Completeness

Both parts are explicitly present: what ('Manage data, records, and automate workflows') and when ('Use when the user wants to interact with Actblue data'). It matches anchor 4 rather than 5 because the 'when' is a single circular condition ('interact with Actblue data') without concrete trigger phrases, and the 'what' remains generic.

Trigger Term Quality

The natural keyword present is essentially just 'Actblue' (plus generic 'data' and 'records'); the terms users of this domain would actually say — 'donations', 'fundraising', 'contributions', 'contribution forms' — are all missing. This matches anchor 3: some relevant keywords but missing common variations and synonyms.

Distinctiveness Conflict Risk

'Actblue' is a distinctive proper noun naming one specific fundraising platform, giving a clear niche with minimal conflict risk against other skills — matching anchor 5. It is not merely anchor 4 because there is no realistic overlap with closely related skills; the only weakness is reliance on a single term rather than a set of distinct triggers.