본문으로 건너뛰기
cccskills
무료GitHub에 공개

folk-hire

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]".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

설치 방법 보기

포함된 파일(1)

  • SKILL.md5.2 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

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:

# [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:

CriterionDescriptionWeightPass SignalFail Signal
[Criterion 1][What this measures][H/M/L][Specific observable signal][Specific observable signal]

Interview stages mapped to criteria:

StageDurationCriteria EvaluatedWho Conducts
Recruiter screen30 minCulture, logisticsRecruiter / Founder
Hiring manager screen45 minRole outcome clarityHiring manager
Technical / work sample60-90 minCore skill 1, 2Peer or lead
Panel60 minCross-functional fit2-3 stakeholders
Reference check30 minVerificationHiring 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

# 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.

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

apex

무료

Engineering lead — hand Apex any task and it routes internally. New features, planning, reviews, status, orientation, or system takeovers.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

tonone-ai/tonone762026년 10월 15일 업데이트

Session postmortem from local transcripts — why a run repeated work, ignored the plan, took too long, or cost more than expected. Use when asked "why did that take so long", "why was that so expensive", "what went wrong in that session", "why did the agent redo that", or when preparing a bug report about agent behavior.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

tonone-ai/tonone762026년 10월 15일 업데이트

apex-gate

무료

Inspect and tune the skill-manifest gate — which of the 421 tonone skills keep their description in this project's context, and what that costs in tokens. Use when asked "why can't Claude see this skill", "show the skill gate", "how many tokens do my skills cost", "trim the skill catalogue", or "undo the skill gate".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

tonone-ai/tonone762026년 10월 15일 업데이트

apex-plan

무료

Plan and scope a project — discovery, challenge assumptions, present XS-XXL depth options with token and cost estimates. Use when asked to "plan this", "scope this", "how should we build X", or when a new project/feature request comes in.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

tonone-ai/tonone762026년 10월 15일 업데이트

Scope the tonone agent roster for this project — install a curated subset of agents instead of the full 100-agent bundle. Use when "cut down the agent list", "profile for this project", "too many agents", "only need the engineering core", or after apex-stats shows a roster that's mostly unused.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

tonone-ai/tonone762026년 10월 15일 업데이트

Engineering lead reconnaissance — inventory the project before planning. Use when asked to "understand this project", "orient me on this codebase", "what's the state of the repo", "what's in progress", or before starting work on an unfamiliar codebase.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

tonone-ai/tonone762026년 10월 15일 업데이트

tonone-ai의 스킬 모두 보기

이 스킬의 문제 신고