Conciseness

The body is dominated by concrete commands, a compact flags table, and terse state descriptions, with only minor over-explanation such as 'This is the fastest way to get a connection' and the padded best-practice note 'This will burn less tokens and make communication more secure'. It fits the 'efficient; minor instances of over-explanation that could be trimmed' anchor, not 5 because a few editorial sentences and the redundant 'Popular actions' line don't earn their tokens.

Actionability

Nearly all guidance is copy-paste executable ('npm install -g @membranehq/cli@latest', 'membrane connection ensure "https://alterapayroll.com/" --json', "membrane action run <actionId> --input '{\"key\": \"value\"}' --json") with a flags table for proxy options. It falls short of 5 due to minor gaps: no worked example of a real action id or --intent value, and inconsistent invocation ('npx @membranehq/cli@latest action list' vs 'membrane action list').

Workflow Clarity

The sequence install → login → connect → poll state → search → run → proxy is clear, and the connection lifecycle includes a real feedback loop (poll with '--wait' until not BUILDING, handle CLIENT_ACTION_REQUIRED, 'poll again ... to check if the state moved to READY'). Not 5 because the step references are broken: 'skip to **Step 2**' and '#### 1b. Wait for the connection' exist with no labeled Step 1a or Step 2 heading, leaving the reader to infer what Step 2 is.

Progressive Disclosure

The single-file body is well sectioned (Overview, Install, Authentication, Connecting, Searching, Running, Proxy, Best practices) with no nested or buried references since no bundle files exist. It sits at the 'good structure; most content appropriately placed; minor organization gaps' anchor rather than 5 because the connection state-machine detail and proxy flag table could be split into reference files, and the 'Popular actions' section merely repeats the search command.

Specificity

The description names the domain ('Altera Payroll integration') but its actions — 'Manage data, records, and automate workflows' — are generic with no concrete payroll operations (e.g., run payroll, view paychecks, handle taxes). This matches the anchor 'Names the domain but actions are minimal or generic'; it is above 1 because the domain is explicitly named, and below 3 because no specific action verb appears.

Completeness

It has both a 'what' ('Altera Payroll integration. Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with Altera Payroll data'). Matches the anchor 'Has both what and when; when could be more explicit or specific' — the when clause is present but narrow, and the what is thin on concrete capabilities, keeping it below 5.

Trigger Term Quality

'Altera Payroll' (twice) and 'interact with Altera Payroll data' are relevant natural keywords, but common variations a user would say are missing: 'payroll', 'paycheck', 'pay run', 'employee payments', 'taxes'. This fits the 'some relevant keywords but missing common variations or synonyms' anchor, not 4 because the only distinctive trigger is the product name.

Distinctiveness Conflict Risk

The product name 'Altera Payroll' is a distinct trigger that clearly separates it from generic data skills, fitting 'mostly distinct; minor overlap risk with closely related skills' — sibling skills from the same Altera HR suite (suggested by help.alterahr.com) could compete, and the phrase 'Manage data, records, and automate workflows' is broad. Not 5 because of that residual overlap; not 3 because the named-product trigger is much stronger than 'Works with document files'.