Conciseness

Mostly efficient with concrete commands throughout, but it includes explanatory asides Claude already knows (e.g. 'Membrane handles authentication and credentials refresh automatically — so you can focus on the integration logic rather than auth plumbing', 'This will burn less tokens and make communication more secure'), matching the score-3 anchor of 'Mostly efficient but includes some unnecessary explanation or could be tightened'. It does not reach score 4 because several sentences are rationale-style padding, and stays above score 2 because the bulk is actionable commands rather than concept explanation.

Actionability

Commands are concrete and copy-paste ready (e.g. `membrane connection ensure "https://user.com/" --json`, `membrane action run <actionId> --connectionId=CONNECTION_ID --input '{"key": "value"}' --json`) with a flag table, matching the score-4 anchor of 'Mostly executable guidance; concrete code or commands with minor gaps'. It does not reach score 5 because CONNECTION_ID placeholders and action discovery are not fully bridged with a concrete end-to-end example, and clears score 3 because real executable commands dominate.

Workflow Clarity

The connect-to-READY workflow is sequenced with poll-until-ready and state handling, but it performs no validation/verification on the actions it runs and is capped at 3 by the guideline for batch/API operations missing feedback loops; the cap applies because `membrane action run` and `membrane request` perform external mutations without any verify step. It cannot exceed 3 under the cap, and clears score 2 because a clear sequence with state checkpoints is present.

Progressive Disclosure

The body is well-sectioned (Overview, Install, Authentication, Connecting, Searching, Popular actions, Proxy, Best practices) with content appropriately inline and no nested references, and no bundle files exist to verify against, matching the score-4 anchor of 'Good structure; most content is appropriately placed'. It does not reach score 5 because there are no one-level-deep reference pointers and a few sections (e.g. proxy flag table) could live in a reference file, and clears score 3 because organization is clear and consistent.

Specificity

The description names the domain ('User.com integration') and two concrete actions ('Manage data, records, and automate workflows') but the actions are generic ('Manage', 'automate') rather than enumerated specifics, matching the score-3 anchor of '1-2 concrete actions, but not comprehensive'. It does not reach score 4 because there is not a list of several specific concrete actions, and it clears score 2 since concrete actions beyond the domain name are named.

Completeness

The description answers 'what' ('Manage data, records, and automate workflows') and 'when' ('Use when the user wants to interact with User.com data'), matching the score-4 anchor of having both with a 'when' that could be more explicit. It does not reach score 5 because the 'when' lacks concrete trigger phrases, and clears score 3 because an explicit 'Use when...' clause is present.

Trigger Term Quality

The phrase 'interact with User.com data' supplies a relevant keyword tied to the product name, but common natural variations a user would say ('User.com', 'marketing automation', 'live chat', 'CRM') are absent from the description, matching the score-3 anchor of 'Some relevant keywords but missing common variations or synonyms'. It does not reach score 4 because natural synonyms are largely missing, and stays above score 2 since one genuinely natural term is present.

Distinctiveness Conflict Risk

Naming 'User.com' specifically ties the skill to a distinct product niche with low conflict risk, matching the score-4 anchor of 'Mostly distinct; minor overlap risk'. It does not reach score 5 because the generic verbs ('Manage data, records, automate workflows') could loosely overlap with other integration skills, and clears score 3 because the User.com anchor makes it largely distinguishable.