Conciseness

The body is largely lean commands, a flag table, and state-machine bullets with little padding; the only over-explanation is the opening "ClayHR is a human resources management system (HRMS)..." paragraph that tells Claude what ClayHR is, matching the score-4 anchor of efficient with minor trimmable instances; it is not a 5 because that overview paragraph and a few restated notes earn slight padding, and not a 3 because the bulk is tight and command-driven rather than noticeably verbose.

Actionability

Concrete executable commands abound — `npm install -g @membranehq/cli@latest`, `membrane connection ensure`, `membrane action run`, plus a complete proxy flag table — fitting the score-4 anchor of mostly executable guidance with minor gaps; it is not a 5 because examples rely on placeholders (CONNECTION_ID, QUERY, actionId) and the only input sample is the generic `{"key": "value"}` rather than a real ClayHR-shaped payload, and not a 3 because the commands are real and copy-pasteable, not pseudocode.

Workflow Clarity

The connection flow is a clear sequenced state machine (ensure -> poll/wait -> READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR) with explicit feedback loops ("poll again... to check if the state moved to READY"), matching the score-4 anchor of a clear sequence with most checkpoints; it is not a 5 because action execution has no validation or error-recovery checkpoint (only "The result is in the output field"), and the "Step 2" / "1b" labels reference steps that are not consistently numbered, and not a 3 because the connection workflow does have explicit checkpoints and retry guidance.

Progressive Disclosure

The skill is a single ~160-line file with no bundle files (references/scripts/assets absent) and no external reference offloading; sections are headed and navigable but reference-style content (the proxy flag table, action discovery) is inlined rather than split out, and "Popular actions" restates "Searching for actions", fitting the score-3 anchor of some structure with content that could be better organized; it is not a 4 because nothing is offloaded to one-level-deep reference files and there is redundancy, and not a 2 because headers and logical sectioning keep it navigable rather than a buried or monolithic wall.

Specificity

Quotes "Manage data, records, and automate workflows" name the ClayHR domain with a couple of actions, but the verbs are generic ("manage", "automate") rather than the specific HR operations the body exposes (time off, payroll, employees), matching the score-3 anchor of domain plus 1-2 concrete actions without comprehensive coverage; it is not a 2 because it lists more than a single minimal action, and not a 4 because the actions lack the concrete specificity of the score-4 example.

Completeness

It answers what ("ClayHR integration. Manage data, records, and automate workflows.") and when ("Use when the user wants to interact with ClayHR data."), satisfying the score-4 anchor of having both with a 'when' that could be more explicit; it is not a 5 because the trigger phrase is generic and lacks the concrete trigger enumerations of the score-5 example, and not a 3 because both what and when are explicitly present.

Trigger Term Quality

The phrase "Use when the user wants to interact with ClayHR data" anchors on the product name "ClayHR", a relevant keyword, but offers no synonyms, natural variations, or related HR terms (employees, payroll, time off) users might actually say, fitting the score-3 anchor of some relevant keywords missing common variations; it is above 2 because "ClayHR" is a real natural term, and below 4 because coverage is thin with no extensions or synonyms.

Distinctiveness Conflict Risk

Anchoring to the distinct product name "ClayHR" with the trigger "interact with ClayHR data" gives it a clear niche with minimal conflict risk, matching the score-4 anchor of mostly distinct with minor overlap; it is not a 5 because the generic "manage data, records, and automate workflows" phrasing could overlap with other integration skills, and not a 3 because the ClayHR-specific trigger clearly separates it.