Conciseness

The body is mostly efficient command documentation, but includes padded sentences such as 'It's used by merchants of all sizes looking for a secure and reliable payment gateway' and 'so you can focus on the integration logic rather than auth plumbing', plus repetitive best-practice framing — fitting 'Mostly efficient but includes some unnecessary explanation or could be tightened'. It is above a 2 because there is no extensive explanation of concepts Claude already knows.

Actionability

Nearly all guidance is copy-paste ready: 'npm install -g @membranehq/cli@latest', 'membrane connection ensure "https://www.bambora.com/" --json', 'membrane action run <actionId> --connectionId=... --input ...', the proxy command with its full flags table. Minor gaps: the 'Popular actions' section contains no actual Bambora actions, and the proxy section shows only '/path/to/endpoint' with no Bambora-specific endpoint example — 'concrete code or commands with minor gaps', not anchor 5's 'specific examples cover the common cases'.

Workflow Clarity

The install → login → connection → action discovery → run/proxy sequence is clear and includes explicit state checkpoints with feedback loops (READY / CLIENT_ACTION_REQUIRED with 'poll again ... to check if the state moved to READY' / CONFIGURATION_ERROR with 'Check the error field'). Gaps: 'skip to **Step 2**' references a step that is never labeled, and there is no verification guidance for action-run outputs — 'clear sequence with most checkpoints present; minor validation gaps', short of anchor 5's complete validation steps.

Progressive Disclosure

A single-file skill (~140 lines) with well-organized, clearly headed sections and no nested or broken references. At this length, the generic Membrane CLI/auth/connection boilerplate (shared across Membrane app skills) could be split into a reference file, and the empty 'Popular actions' section is an organization gap — matching 'Good structure; most content is appropriately placed; ... minor organization gaps' rather than anchor 5's fully appropriate split.

Specificity

The only capability statements are the generic phrases 'Manage data, records, and automate workflows' — no concrete operations (e.g. payment profiles, transactions, reports, refunds) are named, matching the anchor 'Names the domain but actions are minimal or generic'. It is not a 3 because no concrete, specific action is actually listed.

Completeness

Both questions are answered explicitly: what — 'Bambora integration. Manage data, records, and automate workflows'; when — 'Use when the user wants to interact with Bambora data'. The explicit 'Use when' clause avoids the cap at 3, but the when clause is circular and the what is vague, so it fits anchor 4 ('when' could be more explicit) rather than anchor 5's concrete trigger phrases.

Trigger Term Quality

The relevant keywords are 'Bambora integration' and 'interact with Bambora data' — the app name is a strong specific trigger, but natural payment-domain phrases users would say ('payments', 'transactions', 'refunds', 'merchant') are entirely absent, fitting 'Some relevant keywords but missing common variations or synonyms'. It is above a 2 because 'Bambora' is a specific, natural term rather than generic filler, and below a 4 because keyword coverage is limited to the proper noun.

Distinctiveness Conflict Risk

The trigger hinges entirely on the unique proper noun 'Bambora', a specific payment platform, so the skill occupies a clear niche and is very unlikely to fire for the wrong skill — matching 'Clear niche with distinct triggers; minimal conflict risk'.