Conciseness

The body is mostly efficient with concrete commands, but the opening marketing paragraph ('Clerk.io is an ecommerce personalization platform. It helps online stores increase sales...') is padding, and the action-list command is duplicated across 'Searching for actions' and 'Popular actions'. This matches 'mostly efficient but includes some unnecessary explanation or could be tightened', not level 4 which requires only minor trims.

Actionability

Concrete executable commands throughout (install, login with headless fallback, connection ensure, action run with --input JSON, proxy flags table) cover the common cases. Minor gaps: no example of extracting the connection id from the JSON output, and inconsistent CLI invocation ('membrane' vs 'npx @membranehq/cli') — matches 'mostly executable guidance with minor gaps', just below copy-paste-ready level 5.

Workflow Clarity

Clear sequence (install → login → connect → wait → search → run → proxy fallback) with state-based decision branches (READY / BUILDING / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR) and a re-poll feedback loop after the user completes an action. Not 5 because recovery guidance for CONFIGURATION_ERROR is thin ('check the error field for details') and no validation is described for the run results themselves.

Progressive Disclosure

No bundle files exist (references/, scripts/, assets/ all absent), and the single ~150-line file is well-sectioned (Install, Authentication, Connecting, Searching, Running, Proxy, Best practices). Minor organization gaps — the proxy flag table and client-action state details are inline content that could live in a reference file — match anchor 4 rather than the cleanly split structure of anchor 5.

Specificity

The description names the domain ('Clerk.io integration') but its actions are generic — 'Manage data, records, and automate workflows' gives no concrete Clerk.io capabilities (e.g., syncing products, fetching orders, managing search terms). This matches the anchor for naming the domain with minimal or generic actions, not the level above which requires 1-2 concrete actions.

Completeness

The 'when' is explicit ('Use when the user wants to interact with Clerk.io data') but the 'what' is vague ('Manage data, records, and automate workflows' does not say what the skill actually does). It falls between a clear 'what' with weak 'when' (3) and both present with 'when' improvable (4) — the 'when' is fine but the 'what' is not clear, so it cannot score 4.

Trigger Term Quality

The only keywords are 'Clerk.io' (repeated) and the generic 'data'; natural phrases users would say (products, orders, recommendations, search, ecommerce personalization) are absent. This is one or two generic keywords missing the natural phrases users actually say.

Distinctiveness Conflict Risk

'Clerk.io' is a clear niche trigger tied to an explicit 'Use when' clause, giving minimal conflict risk; however the generic opening ('Manage data, records, and automate workflows') creates minor overlap risk with other data-management skills, keeping it just below the clear-niche anchor 5.