Conciseness

Lean and dense; every sentence carries operational content (exact scopes, event subscriptions, URL patterns, security rules, acceptance criteria). No explanation of concepts Claude already knows and no padding — e.g., 'Never replace the entire manifest with only the generated fragment' earns its place.

Actionability

Highly concrete guidance: exact required bot scopes and events, generated URL patterns ('/v1/integrations/slack/<connectionId>/', '/v1/integrations/slack/oauth/callback'), field locations ('Basic Information' to the connector's 'signing-secret field'), the ten-minute authorization window, and the /openwork command. Held below 5 by minor gaps: 'check setup metrics' and 'Send a short DM test' do not specify where or how exactly; manifest 'merge' is described but not operationalized.

Workflow Clarity

Clear four-phase sequence (Establish the target → Configure the existing app → Link the invoking member → Verify and report) with explicit validation checkpoints ('Fix validation errors before saving', 'Verify the Events URL challenge and save its Verified state') and an explicit feedback loop ('If a step fails, inspect its concrete error, make a targeted correction, and retry; stop repeating an unchanged failing installation'). Risky manifest operations are guarded by a before/after comparison requirement, so the destructive-operation cap does not apply.

Progressive Disclosure

Under 50 lines with no bundle files, organized into clear sections, and the two external guide links are clearly signaled at the top and only one level deep. Content is appropriately self-contained; nothing that belongs in a separate file is inlined.

Specificity

Lists several concrete actions — 'Configure and verify the OpenWork Slack assistant', 'installing or linking' — scoped to a specific domain (private-alpha organization, existing Slack app, individual-account connector). Not 5 because it does not enumerate the fuller capability set (e.g., manifest merging, member verification); not 3 because it goes well beyond 1-2 generic actions.

Completeness

Explicitly answers both what ('Configure and verify the OpenWork Slack assistant for an approved private-alpha organization, using its existing Slack app and individual-account connector') and when with concrete trigger phrases ('Use when a user wants @openwork in Slack or needs help installing or linking it'). Written in third person with no fluff.

Trigger Term Quality

Includes natural phrases a user would actually say: 'wants @openwork in Slack', 'needs help installing or linking it'. Not 5 because common synonyms like 'set up', 'connect', or 'add to Slack' are missing; not 3 because coverage goes beyond a single generic keyword.

Distinctiveness Conflict Risk

Occupies a clear niche (OpenWork Slack assistant setup) with a unique, unlikely-to-collide trigger ('@openwork', private-alpha). Minimal overlap risk with any other skill.