Conciseness

The core CLI guidance is efficient, but the ~60-item bare entity list ('- **Profile** ... - **Shared Link**') carries no actionable information, and filler like 'Use action names and parameters as needed' plus introductory product prose add tokens without teaching anything Claude couldn't infer. This matches 'Mostly efficient but includes some unnecessary explanation or could be tightened'; it is not 4 because the entity list is a substantial padding block.

Actionability

Commands are concrete and executable end-to-end: install command, login with headless fallback, 'membrane connection ensure "https://www.asavie.com/" --json', action list/run with '--input '{"key": "value"}', and a complete proxy flag table. This matches 'Mostly executable guidance; concrete code or commands with minor gaps' — the gaps being the dangling 'skip to Step 2' with no Step 2 and unexplained actionId sourcing. It is not 5 because common cases lack a fully worked example (e.g. one complete search-then-run sequence with real values).

Workflow Clarity

There is a clear sequence (install → authenticate → connect → poll for readiness → discover actions → run), and the state-handling section provides genuine checkpoints: poll with '--wait', explicit handling of 'READY', 'CLIENT_ACTION_REQUIRED' with its clientAction fields, and 'CONFIGURATION_ERROR'/'SETUP_FAILED' error guidance. This matches 'Clear sequence with most checkpoints present; minor validation gaps' — the broken 'Step 2' reference, inconsistent numbering ('1b' with no '1'/'2'), and the undated auth-error retry loop keep it below 5.

Progressive Disclosure

The body has reasonable section headers and no nested references, but the ~60-item entity inventory is exactly the kind of inline content that belongs in a separate reference file (or should be dropped entirely), and there are no bundle files at all to offload detail. This matches 'Some structure but could be better organized; content that should be separate is inline'. It is not 4 because a large low-value list is fully inlined rather than split out or summarized.

Specificity

"Manage data, records, and automate workflows" names the domain (Asavie) but the actions are minimal and generic — no concrete operations are described, matching the anchor 'Names the domain but actions are minimal or generic'. It is above 1 because the domain and entity types are named, but below 3 because no specific concrete action is listed.

Completeness

Both parts are present: "what" via "Asavie integration. Manage data, records, and automate workflows" and an explicit "when" via "Use when the user wants to interact with Asavie data". The "when" clause exists but could be more specific with concrete trigger phrases, so it matches 'Has both what and when; when could be more explicit or specific' rather than 5.

Trigger Term Quality

"Asavie" and "interact with Asavie data" are natural terms a user would say, but coverage stops there — missing common variations or synonyms such as SIM management, connectivity, mobile workforce, or IoT. This matches 'Some relevant keywords but missing common variations or synonyms'; it is not 4 because keyword coverage is essentially a single term.

Distinctiveness Conflict Risk

"Asavie" is a clearly distinct product niche with its own trigger terms ("Use when the user wants to interact with Asavie data"), so it is unlikely to fire for unrelated skills. This matches 'Clear niche with distinct triggers; minimal conflict risk'.