Conciseness

The opening paragraph ('Autodesk Revit is a BIM (Building Information Modeling) software... Revit helps streamline workflows from concept to construction') explains a concept Claude already knows, and filler like 'Use action names and parameters as needed.' adds nothing. Otherwise the body is mostly efficient commands, matching the anchor 'Mostly efficient but includes some unnecessary explanation or could be tightened' — not level 2 since only one section is clearly padded, and not level 4 because the overview paragraph and filler lines should be trimmed.

Actionability

Commands are concrete and executable throughout: 'npm install -g @membranehq/cli@latest', 'membrane connection ensure "https://www.autodesk.com/products/revit/overview" --json', 'membrane action run <actionId> --connectionId=... --input {...}'. This matches 'Mostly executable guidance; concrete code or commands with minor gaps' — placeholders (CONNECTION_ID, QUERY, actionId) are never shown with realistic values and there is no example of parsing a response, which keeps it below level 5.

Workflow Clarity

The install → login → connection → search → run sequence is present, and the connection state machine (READY / BUILDING / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR) gives explicit checkpoints with a poll-again feedback loop. However, 'skip to **Step 2**' references a step that is never labeled (no steps are numbered), and there is no validation or error-handling guidance after running an action. This matches 'Steps listed but validation gaps; sequence present but checkpoints missing or implicit' rather than level 4, whose clear navigation is broken by the dangling step references.

Progressive Disclosure

No bundle files exist (references/, scripts/, assets/ are all absent) and nothing is offloaded: ~140 lines are fully inline, including the proxy flag options table and the detailed clientAction state-machine documentation that belong in a reference file. Section headers provide decent structure, so this is above level 2, but it matches 'Some structure but could be better organized... content that should be separate is inline' — the 'Popular actions' heading even duplicates the earlier 'Searching for actions' guidance.

Specificity

The description names the domain ('Autodesk Revit integration') but its actions are generic — 'Manage data, records, and automate workflows' and 'interact with Autodesk Revit data' contain no concrete operations (e.g. list elements, update parameters, extract schedules). This matches the anchor 'Names the domain but actions are minimal or generic'; it is above level 1 because the domain is clearly identified, but below level 3 because no action is concrete.

Completeness

Both parts are present: the 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with Autodesk Revit data'). It falls short of level 5 because the trigger clause is broad and lacks concrete trigger phrases, and the 'what' is generic.

Trigger Term Quality

'Autodesk Revit' is a keyword users would naturally say, but coverage stops there — no synonyms or variations such as 'Revit', 'BIM', 'building model', or '.rvt files' appear. This matches the anchor 'Some relevant keywords but missing common variations or synonyms' rather than level 4's 'good keyword coverage'.

Distinctiveness Conflict Risk

'Autodesk Revit' is a clear niche with a distinct trigger ('interact with Autodesk Revit data') that is unlikely to fire for other skills. This matches the anchor 'Clear niche with distinct triggers; minimal conflict risk'.