Menu

Individual skill

hiring-pipeline

0upvotes

Designs an end-to-end hiring pipeline from job requisition through debrief and offer, with stage-by-stage conversion benchmarks, a reverse-funnel capacity plan, and time-to-fill targets. Use when someone asks "design our hiring process", "how many candidates do we need to make one hire", "our offers keep getting declined", "candidates are dropping out of our funnel", or "how long should hiring take". Do NOT use for writing the interview questions and rubrics for one loop - use interview-guide-builder instead - for writing the sourcing messages to candidates - use candidate-outreach-personalizer instead - for the scorecard artifact itself - use hiring-scorecard instead - or for the job post copy - use job-description-writer instead.

skills/hiring-pipeline/SKILL.md

Read pinned source

Source commit 97a13607d669157a4a16d5ba79b77f208319f7b9

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 6, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
24
Repository last updated
Oct 13, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Hiring Pipeline

An unstructured hiring process produces slow decisions, biased ones, and lost candidates - the top candidate accepts elsewhere during week three of a meandering loop. A structured pipeline reduces bias, compresses time-to-hire, and gives every candidate a consistent experience; the reverse funnel below also tells you, before you open the role, whether the top of the funnel is big enough to produce a hire at all.

## Operating procedure

The order is load-bearing: the scorecard (Step 1) must exist before sourcing, because every later stage evaluates against it, and interviewers cannot own attributes that were never defined.

### Step 1: Write the requisition and scorecard

Collect from the hiring manager before anything opens:

- Mission of the role - what success looks like in 6-12 months, one paragraph.
- Must-have vs nice-to-have skills - keep must-haves to 3-5. Long lists deter great candidates, especially from underrepresented groups.
Back to top