Conciseness

The body is mostly efficient CLI commands, but includes unnecessary filler such as 'Use action names and parameters as needed.', token-burn commentary ('This will burn less tokens'), and a redundant entity list whose nesting ('Customer' -> 'Charge/Invoice') conveys little. Not 4 because several sections could be tightened without losing information.

Actionability

Concrete, copy-pasteable commands throughout — 'npm install -g @membranehq/cli@latest', 'membrane connection ensure "https://chargeover.com/" --json', 'membrane action run <actionId> --connectionId=CONNECTION_ID --input {...}' — plus a flags table for proxy requests. Not 5 due to gaps: the popular-actions table lists keys but never shows how to resolve an actionId, and 'npx @membranehq/cli connection get' is inconsistent with the 'membrane' prefix used elsewhere.

Workflow Clarity

A clear install → login → connection ensure → poll state → search actions → run sequence exists, with explicit state-based validation (READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR branches). However, the skill exposes destructive and financial operations (Delete Customer, Delete Item, Cancel Subscription, Make Payment) with no verification or confirmation steps, which caps workflow clarity at 3; additionally 'skip to Step 2' references a step that is never labeled.

Progressive Disclosure

Sections are well-labeled, but this ~190-line file inlines material that belongs in reference files — a 20-row popular-actions catalog and a proxy flag/options table — and has no bundle files or external references to offload them. This matches anchor 3 ('content that should be separate is inline') better than 4, which expects most content appropriately placed.

Specificity

The phrase 'Manage data, records, and automate workflows' names the ChargeOver domain but the actions are entirely generic ('manage', 'automate workflows') with no concrete domain operations (e.g., create invoices, manage subscriptions). It matches anchor 2 ('Names the domain but actions are minimal or generic') rather than 3, which requires 1-2 concrete actions.

Completeness

Both 'what' ('Manage data, records, and automate workflows') and 'when' ('Use when the user wants to interact with ChargeOver data') are explicitly present, satisfying the 'Use when...' clause requirement. Not 5 because the 'when' ('interact with ChargeOver data') lacks concrete trigger phrases like subscriptions or billing; not 3 because the 'when' is explicit, not merely implied.

Trigger Term Quality

'ChargeOver' and 'data'/'records' are relevant keywords, but coverage misses the natural terms users would say for this product — subscriptions, recurring billing, invoices, customers, payments. Not 4 because the keyword set is thin on domain synonyms, not just missing 'a few'.

Distinctiveness Conflict Risk

'ChargeOver' is a distinct niche product named in both the what and when clauses, so the description triggers only for ChargeOver work and has minimal overlap with generic billing or data skills. This matches anchor 5 ('Clear niche with distinct triggers; minimal conflict risk').