Conciseness

Mostly efficient command-focused prose, but it includes padding Claude doesn't need: the four-sentence "Beehiiv is an email newsletter platform built for writers and creators..." intro, the "Beehiiv Overview" bullet tree (Newsletter/Post, Audience/Subscription), and the filler line "Use action names and parameters as needed." It is not 2 (the bulk is genuine operational guidance, not padded explanation) but not 4 because several sections could be trimmed.

Actionability

Concrete, executable commands throughout — `npm install -g @membranehq/cli@latest`, `membrane connection ensure "https://www.beehiiv.com/" --json`, `membrane action run <actionId> --connectionId=... --input '{...}'` — plus a full flag table for proxy requests. It falls short of 5 due to minor gaps: the CLI is invoked as `npx @membranehq/cli` in one example but `membrane` elsewhere, and the mapping between the action `Key` in the Popular actions table and `<actionId>` at run time is never made explicit.

Workflow Clarity

The connect-and-run sequence is clear and includes real feedback loops: poll with `--wait`, branch on `READY`/`CLIENT_ACTION_REQUIRED`/`CONFIGURATION_ERROR`, then re-poll after the user completes the action. It is not 5 because the flow references "Step 2" which is never defined, the "1b" heading has no "1a", and destructive actions (Delete Post, Delete Subscription) are listed with no verification guidance.

Progressive Disclosure

No bundle files exist, so everything is inline; the single file is well-organized into clearly headed sections (Install, Authentication, Connecting, Searching, Running, Proxy, Best practices) and each block is reasonably scoped. It is not 5 because the 20-row Popular actions table and the proxy flag reference are bulk material that would sit better in a separate reference file, and the dangling "Step 2"/"1b" numbering slightly hurts navigation.

Specificity

"Manage Users, Publications" names the domain and 1-2 objects but the verb "Manage" is generic — the actual capabilities (posts, subscriptions, tiers, segments, automations, custom fields) are absent. It is above anchor 2 ("Names the domain but actions are minimal or generic") because it does name two concrete objects, but below anchor 4 because it does not list several specific actions.

Completeness

Both parts are explicit: what — "Beehiiv integration. Manage Users, Publications."; when — "Use when the user wants to interact with Beehiiv data." It is not 5 because the 'what' is vague ("Manage") and lacks concrete trigger phrases beyond "interact with Beehiiv data"; it is not 3 because the 'when' clause is explicit, not merely implied.

Trigger Term Quality

Natural terms present are "Beehiiv", "Users", and "Publications", but common phrasings a user would actually say — "newsletter", "subscribers", "email", "posts" — are missing. This matches "Some relevant keywords but missing common variations or synonyms"; it is not 2 (keywords are domain-relevant, not generic) nor 4 (coverage is thin for what the platform does).

Distinctiveness Conflict Risk

"Beehiiv" is a distinctive brand name that no other skill category would claim, and the trigger "interact with Beehiiv data" is uniquely tied to it. This matches "Clear niche with distinct triggers; minimal conflict risk" — nothing about it overlaps with generic document, file, or data skills.