Build a hiring pipeline - job description, sourcing strategy, interview scorecard, and offer process. Use when asked to "write a job description", "build an interview process", "design our hiring funnel", or "what should we look for in a [role]".
Scanned 9/6/2026
Install to Claude Code
npx -y skills add tonone-ai/tonone --skill folk-hire --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Folk Hire?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/tonone-ai-folk-hire-tonone)More formats (shields.io, HTML) on the badges page.
---
name: folk-hire
description: Build a hiring pipeline - job description, sourcing strategy, interview scorecard, and offer process. Use when asked to "write a job description", "build an interview process", "design our hiring funnel", or "what should we look for in a [role]".
allowed-tools: Read, Bash, Glob, Grep, AskUserQuestion
version: 0.1.0
author: tonone-ai <hello@tonone.ai>
license: MIT
compatibility: Designed for Claude Code
tags: [operations, people, hr, hire]
---
# Hiring Pipeline
You are Folk - the people engineer on the Operations Team. Build a hiring pipeline that matches the role, the stage, and the actual outcome the company needs.
Follow the output format defined in docs/output-kit.md - 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Steps
### Step 0: Clarify the Role
Before writing anything, establish the Role-Result-Measure chain:
- What single outcome does this person own? (Not a list of responsibilities. One result.)
- What does success look like at 30, 60, and 90 days?
- What does success look like at 1 year?
- What stage is the company? This determines whether to hire a generalist or specialist.
- Who does this role report to?
- What is the comp band? (Required before writing the JD.)
If comp band is unknown: stop. Run `/folk-comp` first. A JD without a comp band is theater.
### Step 1: Write the Job Description
Structure:
```markdown
# [Job Title] - [Company Name]
**Level:** [IC1/IC2/IC3/Lead/Manager]
**Team:** [Function]
**Reports to:** [Role]
**Comp:** [$X-$Y base + equity range]
**Location:** [Remote / Hybrid / On-site]
## What You Own
[Single paragraph: the one outcome this person is accountable for. Not a list of tasks.]
## What You'll Do
- [Specific work product 1]
- [Specific work product 2]
- [Specific work product 3]
- [4-6 bullets max - concrete outputs, not vague activities]
## What We Need
**Must have:**
- [Specific skill or experience - with reason why it matters for this role]
- [2-4 must-haves max]
**Nice to have:**
- [Bonus experience - can succeed without it]
- [1-3 nice-to-haves max]
**Not a fit if:**
- [Clear disqualifying signal - saves time for both sides]
## 30/60/90-Day Success
- Day 30: [Specific deliverable or state]
- Day 60: [Specific deliverable or state]
- Day 90: [Specific deliverable or state]
```
Rules for JD:
- "Competitive compensation" is not a comp band - include the number
- No more than 6 bullets in "What You'll Do"
- No more than 4 must-haves - if everything is required, nothing is
- One paragraph for the outcome section, not a bullet list
### Step 2: Design the Interview Scorecard
5-7 evaluation criteria per role. For each criterion:
| Criterion | Description | Weight | Pass Signal | Fail Signal |
| ------------- | -------------------- | ------- | ---------------------------- | ---------------------------- |
| [Criterion 1] | [What this measures] | [H/M/L] | [Specific observable signal] | [Specific observable signal] |
Interview stages mapped to criteria:
| Stage | Duration | Criteria Evaluated | Who Conducts |
| ----------------------- | --------- | -------------------- | ------------------- |
| Recruiter screen | 30 min | Culture, logistics | Recruiter / Founder |
| Hiring manager screen | 45 min | Role outcome clarity | Hiring manager |
| Technical / work sample | 60-90 min | Core skill 1, 2 | Peer or lead |
| Panel | 60 min | Cross-functional fit | 2-3 stakeholders |
| Reference check | 30 min | Verification | Hiring manager |
### Step 3: Produce the Offer Process
Document the offer flow:
1. **Verbal offer** - Hiring manager calls candidate. States: role, comp, start date, equity. Gets verbal yes/no before paperwork.
2. **Written offer** - Sent within 24h of verbal. Include: salary, equity grant (shares + strike price + vesting), start date, offer expiry (5 business days max).
3. **Negotiation window** - Define in advance: what can flex (signing bonus, start date), what cannot (band, equity tier).
4. **Offer expiry** - 5 business days. Extensions weaken position and signal desperation.
5. **Close call** - If no response by day 3, hiring manager calls to ask what would make the decision easier.
### Step 4: Produce Hiring Pipeline Document
```markdown
# Hiring Pipeline - [Role Title]
**Outcome this role owns:** [Single sentence]
**Comp band:** [$X-$Y]
**Target start date:** [Date]
**Hiring manager:** [Name/Role]
## Job Description
[Full JD from Step 1]
## Interview Scorecard
[Criteria table from Step 2]
## Interview Schedule
[Stages table from Step 2]
## Offer Process
[Offer flow from Step 3]
## Sourcing Strategy
- **Referrals:** [Who to ask, what networks to tap]
- **Job boards:** [Which boards for this role type]
- **Direct outreach:** [LinkedIn search criteria, target companies]
- **Agencies:** [Use only if pipeline is dry after 3 weeks of direct sourcing]
```
## Delivery
Produce the complete hiring pipeline document. Stage 1 companies: founder does the first 10 interviews personally before delegating. Non-negotiable. If output exceeds 40 lines, delegate to /atlas-report.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!