Conciseness

Most of the body is efficient, copy-paste commands, but it includes unnecessary explanation Claude does not need: 'ChatBotKit is a platform for building and deploying AI chatbots. It's used by businesses and developers…', the filler line 'Use action names and parameters as needed.', and a somewhat padded Best practices section. This matches anchor 3 ('mostly efficient but includes some unnecessary explanation') rather than 4, where only minor trimmable instances would remain.

Actionability

Concrete executable commands appear throughout — 'npm install -g @membranehq/cli@latest', 'membrane connection ensure "https://chatbotkit.com/" --json', 'membrane action run <actionId> --connectionId=CONNECTION_ID --input …' — plus a proxy flags table. It falls short of anchor 5 because the run examples use placeholders instead of real action keys from the table, and one table row is erroneous ('Get Message | get-message | There is no get message action.').

Workflow Clarity

The sequence (install → login → connection ensure → poll state → search actions → run → proxy) is present with explicit state checkpoints (READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR) and a re-poll loop, but the numbering is incoherent — 'skip to Step 2' references a step that never exists and '1b' has no '1a' — and there is no verification guidance for executed actions, including create/delete operations. The destructive/batch validation cap of 3 applies, so it cannot score 4.

Progressive Disclosure

The single ~180-line file has clear section headers, but the 20-row Popular actions table and the proxy options table are reference material that belongs in a separate file, and nothing is offloaded (no references/ or assets/ exist). This matches anchor 3 ('some structure… content that should be separate is inline') rather than 2, since structure and navigation within the file are genuinely clear.

Specificity

The description names the domain ('ChatBotKit integration') but its actions are minimal and generic — 'Manage data, records, and automate workflows' uses vague verbs with no concrete ChatBotKit operations (bots, conversations, datasets, messages). It matches anchor 2 rather than 3 because no concrete platform-specific action is listed.

Completeness

Both 'what' ('Manage data, records, and automate workflows') and 'when' ('Use when the user wants to interact with ChatBotKit data') are present, satisfying anchor 4. It falls short of 5 because the 'what' is vague and the trigger phrase is not concrete or varied.

Trigger Term Quality

The key natural term 'ChatBotKit' appears ('Use when the user wants to interact with ChatBotKit data'), but common variations users would say — chatbot, bot, conversation, dataset, message — are missing and 'data'/'records' are generic. This mirrors anchor 3 ('Works with PDF files') rather than 4, which requires good keyword coverage.

Distinctiveness Conflict Risk

'ChatBotKit integration' pins a clear niche platform with minimal confusion risk, matching anchor 4. It is not 5 because the boilerplate 'Manage data, records, and automate workflows' phrasing overlaps with many generic SaaS-integration skills.