Conciseness

The ~170-line flat entity list (with many duplicate entries: Alert, Comment, Event, File, Folder, Link, Message, Notification, Review, Task each appear twice) and the marketing-style intro paragraph ('Biztera is a business management platform designed to help small to medium-sized businesses streamline their operations...') plus the vacuous line 'Use action names and parameters as needed.' add substantial padding. This matches anchor 2 ('Noticeably verbose; several unnecessary explanations or padded sections'); it is not 1 because the CLI workflow sections themselves are lean and command-focused.

Actionability

Concrete, executable commands appear throughout: 'npm install -g @membranehq/cli@latest', 'membrane connection ensure "https://biztera.com/" --json', 'membrane action run <actionId> --connectionId=CONNECTION_ID --input \'{"key": "value"}\' --json', plus a proxy options table. This matches anchor 4 ('Mostly executable guidance; concrete code or commands with minor gaps'); it is not 5 because 'Use action names and parameters as needed' is vague and there is no worked end-to-end example with real values.

Workflow Clarity

A clear sequence is present (install → login → connection ensure → poll until READY → handle CLIENT_ACTION_REQUIRED → search actions → run), with state-based branching, a re-poll feedback loop after user actions, and error handling ('CONFIGURATION_ERROR or SETUP_FAILED — check the error field'). This matches anchor 4 ('Clear sequence with most checkpoints present; minor validation gaps'); it is not 5 because 'skip to Step 2' references a step that is never labeled, and action-run outputs are not validated.

Progressive Disclosure

Sections are well-organized with clear headers and no nested references, but the ~170-line entity list is inline content that clearly belongs in a separate reference file, matching anchor 3 ('Some structure but could be better organized... content that should be separate is inline'). It is not 2 because the rest of the body is appropriately sectioned and navigable; not 4 because the entity list is exactly the kind of bulk content that should be split out.

Specificity

"Manage data, records, and automate workflows" names the Biztera domain but the actions are generic — no concrete operations (e.g., create projects, list invoices, manage approval requests) that the skill body shows are available. It matches the anchor 'Names the domain but actions are minimal or generic' and falls short of 3 because not even 1-2 truly concrete actions are stated.

Completeness

Both a 'what' ("Manage data, records, and automate workflows") and an explicit 'when' ("Use when the user wants to interact with Biztera data") are present, matching anchor 4. It is not 5 because the 'what' is vague and the trigger phrase is generic; not 3 because the 'when' clause is explicit, not merely implied.

Trigger Term Quality

Relevant keywords are present ("Biztera", "data", "records", "workflows") and a user mentioning Biztera would naturally trigger it, but common variations and task-level terms (projects, invoices, CRM, approval requests) are missing. It fits anchor 3 ('Some relevant keywords but missing common variations or synonyms') rather than 4 because coverage beyond the app name is thin.

Distinctiveness Conflict Risk

Naming the specific app "Biztera" creates a clear niche with minimal conflict risk against other skills, matching anchor 4 ('Mostly distinct; minor overlap risk'). It is not 5 because the generic 'manage data' phrasing could overlap with other data-management skills.