CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

recruiting-pipeline

Track and manage recruiting pipeline stages. Trigger with "recruiting update", "candidate pipeline", "how many candidates", "hiring status", or when the user discusses sourcing, screening, interviewing, or extending offers.

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

72%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is an appropriately lean, well-structured overview, but it reads as reference material rather than instructions: it defines the pipeline's stages and metrics without telling Claude what to do with them when the skill triggers. Adding where state lives and what action each trigger maps to would lift both actionability and workflow clarity.

Suggestions

Specify where pipeline state is stored and in what format (e.g., a candidates.md or JSON file with stage, source, and dates), so updates are unambiguous.

Map each trigger to a concrete action, e.g., "recruiting update" -> apply stage change and confirm, "how many candidates" -> report current counts per stage.

Make the ATS section actionable: name the tool or integration to check and the concrete steps to pull or update candidate data.

DimensionReasoningScore

Conciseness

The ~30-line body is lean: a stage table, five one-line metrics, and a single ATS line, with no padding and no explanation of concepts Claude already knows. Every token earns its place.

5 / 5

Actionability

The stage definitions and metric names are concrete content, but the body never says how to execute: there is no guidance on where pipeline state is stored, what format an update takes, or what to do when the skill triggers ("Personalized outreach", "Evaluate basic fit" describe rather than instruct). This fits the anchor for some concrete guidance with missing key details, not the mostly-executable anchor.

3 / 5

Workflow Clarity

While organized, the body leaves the operational workflow undefined: it is ambiguous whether a "recruiting update" means persisting a stage change, asking for details, or reporting metrics, so the single action is not unambiguous as the simple-skill 5-score exception requires.

3 / 5

Progressive Disclosure

Under 50 lines with no need for external references, and the content is well organized into clear sections (Pipeline Stages, Metrics to Track, If ATS Connected), which scores 5 under the rubric's simple-skill guidance.

5 / 5

Total

16

/

20

Passed

Description

81%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: third-person voice, explicit trigger phrases, and a clear niche. The main weakness is the what-clause, which relies on generic verbs ("track and manage") instead of enumerating the skill's concrete capabilities.

Suggestions

Expand the what-clause with concrete actions, e.g., "Update candidate stages from sourcing through offer acceptance and report pipeline metrics such as stage conversion and time to fill."

DimensionReasoningScore

Specificity

"Track and manage recruiting pipeline stages" names the domain with two fairly generic verbs; it does not enumerate several distinct concrete actions (e.g., update candidate stages, report pipeline metrics), matching the anchor for 1-2 concrete actions rather than a comprehensive list.

3 / 5

Completeness

Both the what ("Track and manage recruiting pipeline stages") and an explicit when ("Trigger with ... or when the user discusses ...") are present, but the what is thinner than the trigger side and could list more specific actions, so it fits the anchor where one half could be more explicit rather than the fully concrete both-halves anchor.

4 / 5

Trigger Term Quality

"recruiting update", "candidate pipeline", "how many candidates", "hiring status", plus "sourcing, screening, interviewing, or extending offers" give comprehensive, natural coverage of phrases a user would actually say.

5 / 5

Distinctiveness Conflict Risk

The recruiting/hiring pipeline niche with triggers like "candidate pipeline" and "hiring status" is clearly distinct from other skill domains, with minimal overlap risk.

5 / 5

Total

17

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

anthropics/knowledge-work-plugins

Path

human-resources/skills/recruiting-pipeline/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.