Conciseness

The body is mostly command-first and efficient, but includes unnecessary padding: the generic one-liner 'Airmeet is a platform for hosting virtual events and meetings. It's used by businesses and organizations...', the thin entity bullet list under 'Airmeet Overview', and a 'Popular actions' section that repeats the action-discovery command already shown under 'Searching for actions' — anchor 3 ('mostly efficient but includes some unnecessary explanation'). It is above anchor 2 because padding is limited rather than extensive, and below anchor 4 because the duplication and filler are real trim targets.

Actionability

Concrete, copy-paste-ready commands throughout — 'npm install -g @membranehq/cli@latest', 'membrane connection ensure "https://www.airmeet.com/" --json', 'membrane action run <actionId> --connectionId=CONNECTION_ID --input ...', plus a complete proxy flags table — fitting anchor 4 ('mostly executable guidance with minor gaps'). It falls short of anchor 5 because no concrete action id or real --intent query example is shown, and the 'Popular actions' section lists no actual actions.

Workflow Clarity

The install → login → connection ensure → poll-until-ready → search → run → proxy sequence is clear, with explicit state handling ('READY', 'CLIENT_ACTION_REQUIRED' with poll-again instructions, 'CONFIGURATION_ERROR' with error field) forming a real feedback loop — anchor 4. It is below anchor 5 because the text twice says 'skip to **Step 2**' while no step 2 is labeled in the document, a broken cross-reference that muddies the sequence; no destructive or batch operations apply, so no cap is triggered.

Progressive Disclosure

No bundle files exist, and the ~140-line body is organized into clear, well-leveled sections with all content reasonably inline at this size — anchor 4 ('good structure; most content is appropriately placed; minor organization gaps'). It is below anchor 5 due to the redundant 'Popular actions' section and the 'Airmeet Overview' hierarchy that adds structure without usable navigation, and above anchor 3 because nothing that belongs in a separate file is inlined and the sections are clearly signaled.

Specificity

The description names the domain ("Airmeet integration") but its actions — "Manage data, records, and automate workflows" — are generic with no concrete verbs (e.g., create events, list sessions, fetch attendees), matching the anchor 'names the domain but actions are minimal or generic'. It is below anchor 3 because no specific concrete action is listed, and above anchor 1 because the domain is at least explicitly named.

Completeness

Both halves are present: what ("Manage data, records, and automate workflows") and an explicit when ("Use when the user wants to interact with Airmeet data"), matching anchor 4. It is above anchor 3 because the 'Use when' trigger is explicit rather than weakly implied, but below anchor 5 because neither the what nor the when uses concrete trigger phrases like events, webinars, or sessions.

Trigger Term Quality

"Airmeet" is a natural keyword users would say, but the description misses common variations and synonyms such as "events", "webinars", "sessions", "meetups", or "attendees" — fitting anchor 3 ('some relevant keywords but missing common variations or synonyms'). It falls short of anchor 4 because coverage beyond the product name is thin.

Distinctiveness Conflict Risk

Naming the distinct product "Airmeet" with an Airmeet-specific trigger ("interact with Airmeet data") gives a clear niche with minimal conflict risk, but the boilerplate "Manage data, records, and automate workflows" is interchangeable with any generic integration skill, leaving minor overlap risk — anchor 4 rather than 5.