Conciseness

The body is mostly efficient with executable commands, but includes unnecessary background Claude already knows ("Cloud Foundry is an open source cloud application platform as a service (PaaS). It's used by developers to deploy, run, and scale applications in the cloud.") and some repetition of the action-discovery command. Fits mostly efficient with some unnecessary explanation. Not a 4 because the intro paragraph is pure filler; not a 2 because the bulk is lean command reference.

Actionability

Concrete, copy-pasteable commands appear throughout ("npm install -g @membranehq/cli@latest", "membrane connection ensure ...", "membrane action run <actionId> --connectionId=CONNECTION_ID --json") with a clear options table. Minor gaps: placeholders like CONNECTION_ID are never shown resolved, and action parameters are shown only abstractly. Matches mostly executable with minor gaps. Not a 5 because no end-to-end worked example resolving placeholders; not a 3 because guidance is concrete and executable, not pseudocode.

Workflow Clarity

A sequence is present (install -> authenticate -> connect -> poll for READY -> search actions -> run/proxy), and the connection-state branching is spelled out, but there is no validation step confirming an action succeeded before proceeding, and the "Step 2" referenced is never defined — a dangling checkpoint. Fits steps listed with validation/sequence gaps. Not a 4 because "Step 2" is undefined and success verification is absent; not a 2 because the core connect->ready->act flow is coherent.

Progressive Disclosure

Content is well-organized into clearly signaled sections (Install, Authentication, Connecting, Searching, Popular actions, Proxy, Best practices) with no bundle files to defer to, so all detail appropriately lives in one SKILL.md. Minor gap: the "Cloud Foundry Overview" bullet list and the full proxy-flags table could be trimmed, but structure is clear and one-level. Matches good structure, mostly well placed. Not a 5 because no detailed subtopics are split out and some inline reference-like bulk remains; not a 3 because organization is clear and references are not buried.

Specificity

Quotes "Manage data, records, and automate workflows" name the Cloud Foundry domain plus a few actions, but the actions ("manage data", "records") are generic rather than comprehensive concrete capabilities — matching the anchor for domain named with 1-2 actions. Not a 4 because no list of several specific actions; not a 2 because actions go beyond a single minimal generic verb.

Completeness

Both halves are present: "Manage data, records, and automate workflows" answers what, and "Use when the user wants to interact with Cloud Foundry data" answers when explicitly. Fits the anchor for both present with when somewhat generic. Not a 5 because the trigger phrases lack concrete specifics; not a 3 because the when clause is explicit rather than missing or weakly implied.

Trigger Term Quality

Keywords include "Cloud Foundry", "data", "records", "workflows", and "interact with Cloud Foundry data", giving some relevant natural terms but missing common variations a user might actually say ("deploy apps", "CF", "orgs", "spaces", "services"). Fits the anchor for some relevant keywords missing common variations. Not a 4 due to gaps in natural phrasing; not a 2 because more than one generic keyword is present.

Distinctiveness Conflict Risk

"Cloud Foundry integration" is a clear niche unlikely to trigger for the wrong skill, though the generic "manage data, records" phrasing leaves minor overlap risk with other data-integration skills. Matches mostly distinct with minor overlap. Not a 5 due to generic action verbs; not a 3 because the domain scoping is clear.