Conciseness

The body is mostly efficient commands, but contains trimmable padding: the marketing opener "AddSearch is a hosted search solution for websites. It allows website owners to provide a better search experience", the content-free "AddSearch Overview" bullet list (Search/Result/Index/Configuration/Account), and a redundant repeat of the action-discovery command (once as `membrane action list`, once as `npx @membranehq/cli@latest action list`). Fits anchor 3 (mostly efficient but some unnecessary explanation); not 4 because there are several such sections, not just minor instances.

Actionability

Concrete, executable commands throughout — install, login (including headless completion), connection ensure, polling with --wait, action run with --input JSON, and a proxy flags table. Fits anchor 4 (mostly executable, minor gaps) rather than 5 because the "Popular actions" section lists no actual AddSearch actions (only discovery instructions), and CLI invocation is inconsistent between `membrane` and `npx @membranehq/cli`.

Workflow Clarity

A rough sequence exists (install → login → connect → poll → act) with genuinely good state-based feedback loops (poll until not BUILDING, re-poll after user completes auth, check the error field on CONFIGURATION_ERROR/SETUP_FAILED). However, "If the returned connection has state: READY, skip to Step 2" references a Step 2 that is never labeled anywhere, and the "1b" heading has no corresponding numbered step scheme — the sequence is present but its checkpoints and flow references are broken. Fits anchor 3; not 4 because dangling step references make the intended order impossible to follow as written.

Progressive Disclosure

Single-file skill with no bundle files and no references to nonexistent files; sections are clearly headed (Install, Authentication, Connecting, Searching, Running actions, Proxy, Best practices) and content is appropriately placed for a ~140-line skill. Fits anchor 4 (good structure, minor organization gaps) — the useless Overview bullet list and the reference-grade proxy flags table are the minor gaps; not 3 since nothing is buried or clearly misplaced for this skill size.

Specificity

"Manage data, records, and automate workflows" names the AddSearch domain but the actions are generic boilerplate — no concrete operations like indexing pages, searching records, or configuring crawlers. It matches anchor 2 (domain named, actions minimal/generic), not 3, because no concrete action is actually listed.

Completeness

Explicitly answers both: what ("AddSearch integration. Manage data, records, and automate workflows") and when ("Use when the user wants to interact with AddSearch data"). Fits anchor 4 (both present, 'when' could be more specific) — not 5 because the 'what' is vague and the 'when' is near-circular, not 3 because the when-clause is explicitly stated.

Trigger Term Quality

"AddSearch" is a strong, specific brand trigger, but beyond it only "data" and "records" appear — natural variations users would say (site search, search index, crawler, search results) are missing. Fits anchor 3 (some relevant keywords, missing common variations); not 4 because coverage beyond the brand name is thin.

Distinctiveness Conflict Risk

The AddSearch brand anchors a clear niche with minimal conflict risk for search-related work, but "manage data, records, and automate workflows" is generic phrasing shared by many app-integration skills. Fits anchor 4 (mostly distinct, minor overlap risk); not 5 because the generic tail could collide with other integration skills.