Conciseness

The command documentation itself is efficient, but there is unnecessary content: a two-sentence marketing intro ('...targeting entrepreneurs and small to medium-sized businesses'), a content-free overview bullet list (Dashboard/Orders/Customers/Products/Analytics), and the action-list command duplicated in 'Searching for actions' and 'Popular actions'. This matches 'Mostly efficient but includes some unnecessary explanation or could be tightened'; not a 2 because the padding is limited rather than pervasive.

Actionability

Commands are concrete and copy-paste ready throughout (npm install, membrane login, connection ensure, connection get --wait, action list, action run with --input), matching 'Mostly executable guidance; concrete code or commands with minor gaps'. Not a 5 because the proxy section gives a flag table but no complete example request, and usage alternates inconsistently between 'membrane' and 'npx @membranehq/cli@latest'.

Workflow Clarity

The sequence (install → authenticate → connect → poll until READY → discover/run actions) is clear with explicit state-based checkpoints ('poll again... to check if the state moved to READY', 'CONFIGURATION_ERROR or SETUP_FAILED — check the error field'), matching 'Clear sequence with most checkpoints present; minor validation gaps'. Not a 5 because 'skip to Step 2' references a step that is never labeled, and there is no verification guidance for action results.

Progressive Disclosure

Scored against the actual bundle structure: no references/, scripts/, or assets/ directories exist, and the body makes no file references, so nothing is broken or nested. The single-file body (~125 lines) is well organized with clear section headers; minor gaps are that it exceeds the simple-skill threshold and some CLI reference material (the proxy flag table) could live in a separate reference file. This matches 'Good structure; most content is appropriately placed; references mostly clear; minor organization gaps'.

Specificity

Names the domain ('AVADA Commerce integration') but the actions — 'Manage data, records, and automate workflows' — are minimal and generic, matching the anchor 'Names the domain but actions are minimal or generic'. Not a 3 because no concrete action (e.g. orders, customers, products) is explicitly stated.

Completeness

Has both a 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with AVADA Commerce data'), so the missing-trigger cap does not apply; however the 'what' is generic and the 'when' names no concrete scenarios, matching 'Has both what and when; when could be more explicit or specific'. Not a 5 because neither part includes concrete trigger phrases or capabilities.

Trigger Term Quality

'AVADA Commerce' is a relevant natural keyword and the trigger clause repeats it, but common variations users would actually say (orders, customers, products, email marketing) are missing, matching 'Some relevant keywords but missing common variations or synonyms'. Not a 4 because coverage beyond the app name itself is thin.

Distinctiveness Conflict Risk

The named app ('AVADA Commerce integration', 'interact with AVADA Commerce data') gives a clear niche with minimal wrong-skill triggering, but the generic action boilerplate overlaps with other Membrane app-integration skills, matching 'Mostly distinct; minor overlap risk with closely related skills'. Not a 5 because the triggers are just the app name rather than distinctive task phrases.