Conciseness

The ~77-line flat bullet list of entity names ('Contact', 'Entity Contribution', etc.) closing with the vacuous 'Use action names and parameters as needed' is a large padded section with no actionable content, and the intro ('CiviCRM is an open source CRM used by non-profit...') explains a concept Claude already knows. This matches 'Noticeably verbose; several unnecessary explanations or padded sections' — the entity list alone is roughly a third of the body — rather than level 3's 'some unnecessary explanation'.

Actionability

Concrete, largely executable CLI commands appear throughout: `npm install -g @membranehq/cli@latest`, `membrane connection ensure "https://civicrm.org/" --json`, `membrane action run <actionId> --connectionId=... --input '{...}'`, plus a proxy flags table and a 20-row actions table with keys. It is not level 5 because of minor gaps: `membrane login --tenant` shows no example value, and the entity overview provides no usable parameters or examples.

Workflow Clarity

The connection setup sequence has explicit state-based checkpoints and feedback loops — poll with `--wait` while `BUILDING`, handle `CLIENT_ACTION_REQUIRED` by showing `uiUrl` and re-polling, and check the `error` field on `CONFIGURATION_ERROR`. It is not level 5 because the text twice says 'skip to **Step 2**' but no Step 2 (or Step 1) heading exists, and the install → authenticate → connect → act sequence is implied by section order rather than explicitly numbered. The destructive-operation cap does not apply since the prescribed workflow is connection setup, not batch/destructive execution.

Progressive Disclosure

There are no bundle files at all, and the 77-line entity list plus the full actions and proxy-flag tables are inlined in a ~235-line SKILL.md where a leaner body with a separate entities/actions reference file would serve better. Section headers are reasonable, but 'content that should be separate is inline' places this at level 3 rather than level 4's 'most content is appropriately placed'.

Specificity

"Manage data, records, and automate workflows" names the domain (CiviCRM) but the actions are generic — no concrete verbs or objects like contacts, contributions, events, or memberships. It sits at the 'Names the domain but actions are minimal or generic' anchor, below level 3 because none of the listed actions are concrete, and above level 1 because the domain is clearly named.

Completeness

It has both a 'what' ("CiviCRM integration. Manage data, records, and automate workflows") and an explicit 'when' ("Use when the user wants to interact with CiviCRM data"), matching 'Has both what and when; when could be more explicit or specific'. It is not level 5 because neither the what nor the when names concrete capabilities or trigger phrases, and not level 3 because the 'Use when' clause is explicitly present rather than missing or weakly implied.

Trigger Term Quality

"CiviCRM" is a strong natural trigger term, but the remaining keywords ("data", "records", "workflows") are generic, and common variations a user would actually say — contacts, donations, memberships, events, non-profit CRM — are absent. This matches 'Some relevant keywords but missing common variations or synonyms', not level 4 which requires good keyword coverage.

Distinctiveness Conflict Risk

CiviCRM is a clearly delineated niche product and the description is anchored on that name, giving it distinct triggers and minimal overlap risk with other skills — matching the level 5 anchor. The generic 'Manage data, records' tail does not create meaningful conflict risk.