Conciseness

The body is dominated by executable commands and a compact flag table, but includes minor padding such as "Cacoo is a user-friendly online diagramming tool. It's used by teams to collaborate..." and the agent-types list "claude, openclaw, codex, warp, windsurf, etc." that could be trimmed. Not 3 because the bulk is lean CLI instruction rather than explanation of known concepts; not 5 because the intro paragraph and Membrane marketing framing ("This is the fastest way to get a connection. The URL is normalized to a domain...") slightly over-explain.

Actionability

Concrete, copy-paste-ready commands cover install ("npm install -g @membranehq/cli@latest"), auth ("membrane login --tenant --clientName=<agentType>"), connection ("membrane connection ensure \"https://cacoo.com/\" --json"), action discovery/run, and proxy flags. Not 5 because there is no worked example of a real Cacoo action (e.g., searching "list diagrams" and running a concrete actionId) — every invocation uses placeholders like CONNECTION_ID and <actionId> without a demonstrated end-to-end case.

Workflow Clarity

A clear sequence is present (install → login → connection ensure → poll state → search actions → run / proxy) and the connection phase has genuine validation checkpoints (polling until state leaves BUILDING, explicit READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR handling and re-poll after user action). Not 5 because "skip to **Step 2**" is referenced twice but no Step 1/Step 2 headings exist (a dangling, incoherent reference), and running actions has no error-checking or output-validation guidance.

Progressive Disclosure

No bundle files exist (references/, scripts/, assets/ are absent) and the body is reasonably well organized into clearly headed sections (Overview, Working with Cacoo, Popular actions, Best practices) with no nested or broken file references. Scored 4 rather than 5 because at ~145 lines the Cacoo overview entity tree and proxy flag table could partly live in a reference file, and the stray numbered-step convention ("1b", "Step 2") muddies navigation slightly.

Specificity

"Cacoo integration" names the domain, but the stated actions — "Manage data, records, and automate workflows" — are minimal and generic boilerplate that never mentions diagrams, the actual capability domain. Not 3 because no concrete action (e.g., "create and edit diagrams" or "manage folders and projects") is listed; not 1 because the domain is named and third-person action verbs are used.

Completeness

It has an explicit "when" — "Use when the user wants to interact with Cacoo data" — but the "what" ("Manage data, records, and automate workflows") is vague boilerplate that does not concretely state what the skill does. Not 4 because anchor 4 requires a clear "what", and "manage data, records" could describe almost any data app; not 2 because the "when" clause is present and reasonably explicit.

Trigger Term Quality

"Cacoo" and "Cacoo data" are relevant, specific keywords a user would say when they need this skill, but all natural task-level terms users would actually use — diagram, flowchart, mind map, network diagram, wireframe — are missing. Not 4 because keyword coverage is essentially a single app name with no variation or synonym coverage; not 2 because "Cacoo" is a specific, genuinely natural trigger rather than a generic filler keyword.

Distinctiveness Conflict Risk

The Cacoo brand name gives it a clear niche and it will trigger correctly whenever the user mentions Cacoo, with minimal conflict risk against unrelated skills. Not 5 because the generic "Manage data, records, and automate workflows" phrasing creates minor overlap risk with other diagramming/data-app skills (Miro, Lucidchart, draw.io) whose descriptions could read nearly identically apart from the app name.