Conciseness

Commands dominate and are lean, but the action-discovery command is duplicated ("Searching for actions" vs "Popular actions"), filler like "Use action names and parameters as needed" appears, and Membrane internals ("This is the fastest way to get a connection. The URL is normalized to a domain...") are explained unnecessarily. Matches anchor 3 ("Mostly efficient but includes some unnecessary explanation or could be tightened"); not 4 because the duplication and padding exceed minor trims.

Actionability

Concrete, executable commands throughout: `npm install -g @membranehq/cli@latest`, `membrane connection ensure "https://calendarific.com/" --json`, `membrane action run <actionId> --connectionId=CONNECTION_ID --input '{"key": "value"}' --json`, plus a proxy flag table. Matches anchor 4 ("Mostly executable guidance; concrete code or commands with minor gaps"); not 5 because there is no worked example of an actual Calendarific action and "Popular actions" lists none.

Workflow Clarity

The sequence (install → login with headless fallback → connection ensure → `--wait` polling → explicit state dispatch for READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR → re-poll loop → action discovery → run → proxy fallback) has real feedback loops and checkpoints, matching anchor 4. Not 5 because "skip to Step 2" is referenced twice with no Step 2 heading in the document, and "#### 1b" implies step numbering used nowhere else.

Progressive Disclosure

No bundle files exist; this is a single-file skill with clear, one-level-deep section headers (overview, install, auth, connecting, searching, running, proxy, best practices) and easy navigation. Minor organization gaps — the duplicated "Popular actions" section and generic Membrane CLI boilerplate inlined — match anchor 4 ("Good structure; most content is appropriately placed; minor organization gaps").

Specificity

"Manage data, records, and automate workflows" is generic template boilerplate — the domain (Calendarific) is named but no concrete action (e.g., holiday lookup by country/year) is stated, matching the anchor "Names the domain but actions are minimal or generic". Not 1 because the domain is named rather than pure abstraction; not 3 because no concrete capability is actually described.

Completeness

An explicit "Use when..." clause is present, but it is a generic template trigger, and the "what" ("Manage data, records, and automate workflows") is vague. This falls between anchor 3 (clear what, weak when) and anchor 4 (both present, when could be more specific), pulled down by the boilerplate "what" and the trigger-free "when".

Trigger Term Quality

The only keyword is the brand name "Calendarific"; the natural phrases users would say — "holidays", "public holidays", "holiday calendar", "observances" — are entirely absent from "Use when the user wants to interact with Calendarific data". Anchor 2 ("missing the natural phrases users say") fits; it is not 3 because even the artifact class (holidays) is never mentioned.

Distinctiveness Conflict Risk

Naming the specific app "Calendarific" carves a clear niche with low wrong-skill trigger risk, matching anchor 4 ("Mostly distinct; minor overlap risk with closely related skills"). Not 5 because the template actions ("Manage data, records, and automate workflows") are indistinguishable from sibling integration skills.