Conciseness

The operational core (install, auth, connection, action discovery, running, proxy flags) is tight and command-first, but there is real padding: the opening marketing paragraph ("helps sales, investment banking, and consulting teams close more deals. It automates the collection of relationship data..."), the cryptic "Affinity Overview" bullet list ("Document / Section / Project / Tag"), the filler line "Use action names and parameters as needed.", and "This will burn less tokens" in Best practices. This matches "mostly efficient but includes some unnecessary explanation or could be tightened" rather than the minor-trim level of a 4.

Actionability

Every phase of the lifecycle ships a copy-paste-ready command with real flags: `npm install -g @membranehq/cli@latest`, `membrane login --tenant --clientName=<agentType>`, `membrane connection ensure "https://www.affinity.co/" --json`, `membrane action list --connectionId=... --intent "QUERY" --limit 10 --json`, `membrane action run <actionId> --input '{...}'`, and a full proxy flag table (-X, -H, -d, --json, --rawData, --query, --pathParam). A 20-row action table with names, keys, and descriptions covers the common cases; not a 4 because there are no material gaps — the actionId source is explained by the action-list output schema ("Each result includes id, name, description, inputSchema...").

Workflow Clarity

The connection phase is genuinely strong — explicit state-machine checkpoints (poll with --wait until READY, handle CLIENT_ACTION_REQUIRED via clientAction.agentInstructions, re-poll after the user acts, check the error field on CONFIGURATION_ERROR/SETUP_FAILED). But the data-operation phase has no validation guidance at all: the skill drives create/update of CRM records (update-person, update-organization, update-opportunity, create-list-entry) with no verify-after-write step and no error-checking on action run results, so the destructive/batch cap of 3 applies. There is also a dangling navigation reference: "If the returned connection has state: \"READY\", skip to **Step 2**" — no "Step 2" is labeled anywhere in the document, and the only numbered heading is "#### 1b", implying a step scheme that was never written.

Progressive Disclosure

A single-file skill (no references/, scripts/, or assets/ exist, so no dangling or nested references) with a clean one-level section structure: Install → Authentication → Connecting → Searching → Popular actions → Running → Proxy → Best practices. This lands on "good structure; most content is appropriately placed; minor organization gaps" — the 20-row Popular actions table is borderline reference material that could move to a reference file, which is what keeps it from a 5, but at ~160 lines with headers doing real navigation work the split is a nicety, not a defect.

Specificity

"Manage Organizations, Leads, Pipelines, Users, Roles, Filters" names the domain plus six concrete capability areas, matching the anchor for several specific actions with minor coverage gaps. It falls short of a 5 because a single generic verb ("Manage") stands in for distinct actions (create/update/search), and capabilities shown in the body (notes, lists, list entries, opportunities) are not covered.

Completeness

Both halves are present: the "what" ("Affinity integration. Manage Organizations, Leads, Pipelines, Users, Roles, Filters.") and an explicit "Use when the user wants to interact with Affinity data" trigger clause, matching the anchor where "when" could be more explicit or specific. It is not a 5 because the when-clause is a single generic phrase without concrete trigger variations (e.g. "mentions Affinity, wants to create or update a lead/organization/opportunity").

Trigger Term Quality

"Affinity" plus the entity terms ("Organizations, Leads, Pipelines, Users, Roles, Filters") give good keyword coverage of what users would naturally say. Not a 5: common synonyms and variations are missing (CRM, contacts, deals, opportunities — the body's action table uses "Opportunities" and "Lists", terms absent from the description).

Distinctiveness Conflict Risk

Naming the specific app ("Affinity") gives it a clear niche with distinct triggers, but generic CRM entity terms ("Organizations", "Leads", "Pipelines") create minor overlap risk with other CRM/sales skills when the user does not name the app — the "mostly distinct; minor overlap risk with closely related skills" anchor. A 5 would require triggers that keep it clearly separate from those neighboring skills.