Conciseness

The command documentation is efficient, but the marketing-style intro ("ApplicantStack is an applicant tracking system that helps businesses manage their hiring process. Recruiters and HR departments use it to..."), the 16-line bullet list of bare entity names with no guidance, and the "Agent Types" aside add padding that could be cut. Mostly efficient with some unnecessary explanation — anchor 3, not 4.

Actionability

Concrete copy-paste commands cover the main flows: `npm install -g @membranehq/cli@latest`, `membrane login --tenant --clientName=<agentType>`, `membrane connection ensure "https://www.applicantstack.com/" --json`, `membrane action run <actionId> --connectionId=... --input '{"key": "value"}'`, plus the proxy flags table. Minor gaps keep it from 5: a dangling reference to "**Step 2**" that is never labeled, and inconsistent invocation (`membrane` vs `npx @membranehq/cli`).

Workflow Clarity

The sequence install → login → ensure connection → poll state → handle clientAction → search actions → run → proxy fallback is clear, and connection-state handling (READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR with "poll again after the user completes the action") forms a real feedback loop. Anchor 4 rather than 5 because the "Step 2"/"1b" numbering is inconsistent and running actions/proxy requests themselves have no output-validation guidance.

Progressive Disclosure

Well-organized single-file skill with clear section headers and no buried or nested references (no bundle files exist to verify). The inlined connection-state table and proxy flag reference are reasonably sized for a single-file skill, though the connection lifecycle detail could live in a separate reference file. Anchor 4, not 5 — it exceeds the under-50-line simple-skill case and is not split into reference files.

Specificity

"Manage data, records, and automate workflows" names the ApplicantStack domain but the actions are generic ("manage", "automate") with no concrete operations like "create offers" or "track candidates". Matches anchor 2 (domain named, actions minimal/generic) rather than 3, which requires 1-2 concrete actions.

Completeness

Both parts are present: a "what" ("Manage data, records, and automate workflows") and an explicit "when" ("Use when the user wants to interact with ApplicantStack data"). Fits anchor 4 rather than 5 because the "what" is generic rather than a concrete trigger phrase, and not 3 because the "when" clause is explicitly stated, not merely implied.

Trigger Term Quality

"ApplicantStack" and "data"/"records" are relevant keywords a user might say, but common natural phrasings like "candidates", "jobs", "hiring", "recruiting", or "ATS" are missing. Some relevant keywords but missing common variations — anchor 3, not 4, which requires fuller keyword coverage.

Distinctiveness Conflict Risk

Naming "ApplicantStack" gives a clear niche with minimal wrong-skill triggering, but the surrounding generic phrasing ("Manage data, records, and automate workflows") overlaps with other app-integration skills. Mostly distinct with minor overlap risk — anchor 4, not 5, since the distinctiveness rests on the app name alone.