Conciseness

The body is mostly tight, executable command blocks, but contains unnecessary explanation such as "It's used by individuals and businesses who need to convert documents, images, audio, and video files" (background Claude does not need) and filler like "Use action names and parameters as needed." It fits anchor 3 (mostly efficient, some unnecessary explanation) rather than 4 because there are several such sentences, and not 2 because the bulk is lean command documentation.

Actionability

Concrete, copy-paste-ready commands throughout — "npm install -g @membranehq/cli@latest", "membrane connection ensure \"https://cloudconvert.com\" --json", "membrane action run <actionId> --connectionId=CONNECTION_ID --input '{\"key\": \"value\"}' --json" — plus an 18-action catalog and a proxy flag table. It is anchor 4 rather than 5 because no worked example with real parameters is shown (e.g. an actual convert-file or create-job input), so the reader must discover inputSchema separately; the generic '{"key": "value"}' placeholder leaves a minor gap.

Workflow Clarity

The install → login → connection → search → run sequence is clear, with a good connection-state feedback loop (READY / CLIENT_ACTION_REQUIRED with re-poll instructions / CONFIGURATION_ERROR with error-field checking). However, "skip to Step 2" references a step that is never labeled, and there is no validation after execution — no instruction to poll get-job/get-task until a conversion finishes — despite the catalog including destructive and batch operations ("Delete a job and all its tasks", "Create a new conversion job with multiple tasks"), which caps this at anchor 3 per the rubric.

Progressive Disclosure

A single self-contained file with well-organized, clearly headed sections (Install the CLI, Authentication, Connecting, Searching for actions, Popular actions, Running actions, Proxy requests, Best practices) and no nested or buried references — no bundle files exist to verify. It is anchor 4 rather than 5 because at ~160 lines the 18-row action table and proxy details could be split into a reference file, and not 3 because nothing is buried and navigation is easy.

Specificity

"Manage Deals, Persons, Organizations, Leads, Projects, Pipelines and more" offers only the generic verb "Manage" while never naming the skill's actual capabilities (converting, importing, or exporting files); it names the domain but the actions are minimal or generic, matching anchor 2. It is not 3 because no concrete CloudConvert action is described, and not 1 because the domain and objects are explicitly named.

Completeness

Both parts are explicitly stated: what ("Cloud Convert integration. Manage Deals, Persons, Organizations, Leads, Projects, Pipelines and more") and when ("Use when the user wants to interact with Cloud Convert data"). It is not 5 because the 'when' is circular (only fires when the product is named) and the 'what' omits the core conversion capability, and not 3 because an explicit 'Use when...' clause is present.

Trigger Term Quality

The only natural keyword is the brand name "Cloud Convert"; the phrases users would actually say for file conversion ("convert file", "file conversion", "PDF to Word", "change format", file extensions) are all absent, and "interact with Cloud Convert data" is not a phrase users say. This lands at anchor 2 (one or two generic keywords, missing natural phrases) rather than 3, since beyond the brand name there is no relevant conversion vocabulary.

Distinctiveness Conflict Risk

The trigger clause "Use when the user wants to interact with Cloud Convert data" is product-specific, but "Deals, Persons, Organizations, Leads, Projects, Pipelines" are classic CRM nouns that would collide with CRM integration skills and capture wrong intents. It is somewhat specific but could still overlap with similar skills (anchor 3), not 4 because of that entity-list overlap, and not 2 because the explicit trigger names the exact product.