Conciseness

The body is command-driven with little explanation of concepts Claude already knows, e.g. install ("npm install -g @membranehq/cli@latest"), auth, and proxy usage are all given as bare commands. Minor trimmable padding exists — the stub data-model bullets under 'Autobound Overview' ('**Account** / **Contacts**' with no descriptions) and the filler line 'Use action names and parameters as needed' — which keeps it below a 5.

Actionability

Guidance is mostly executable: concrete commands for login, connection ensure with a real URL, action list/run with JSON input examples, and a proxy flags table. The main gap is the 'Popular actions' table having an entirely empty Description column, so the reader cannot tell what each action does without running a search; that incompleteness prevents a 5.

Workflow Clarity

The setup flow is clearly sequenced (install → login → connection ensure → poll state → search → run) with state-based checkpoints and recovery guidance for 'CLIENT_ACTION_REQUIRED' and error states. Minor gaps: 'skip to **Step 2**' references a heading that does not exist, and the '#### 1b' numbering implies a step structure that was never defined — noticeable but not disqualifying, so a 4 rather than 5.

Progressive Disclosure

The ~150-line body is a single well-sectioned file (Install, Authentication, Connecting, Searching, Popular actions, Running, Proxy, Best practices) with no bundle files and no buried references. Structure is good and content is mostly appropriately placed for an overview of this size; it is not a 5 because the connection-state handling and proxy options could arguably live in a separate reference file, and the sparse Overview bullets add little navigational value.

Specificity

The description names the domain ("Autobound integration") but its actions — "Manage data, records, and automate workflows" — are generic with no concrete capabilities (no mention of email openers, sequences, insights, or contacts). This matches the anchor 'Names the domain but actions are minimal or generic'; it is not a 3 because no specific action like 'generate personalized emails' is stated.

Completeness

Both clauses are explicitly present: 'what' ("Autobound integration. Manage data, records, and automate workflows") and 'when' ("Use when the user wants to interact with Autobound data"). The 'when' could be more specific and the 'what' is vague, fitting anchor 4 rather than 5; it is not a 3 because the 'when' clause is explicit, not merely implied.

Trigger Term Quality

The only substantive natural keyword is "Autobound" (appearing twice); "data", "records", and "workflows" are generic and users seeking sales outreach help would not say them. Common variations like 'sales outreach', 'email personalization', 'prospecting', or 'sequences' are missing, matching 'Some relevant keywords but missing common variations or synonyms'.

Distinctiveness Conflict Risk

The brand name "Autobound" in both the what and when clauses makes this skill mostly distinct with minimal conflict risk against other app-integration skills. It is not a 5 because the generic phrases "Manage data, records, and automate workflows" could overlap with other data-management or workflow-automation skills.