Hiring loop
Agent Skills-compatible leadership and manager workflow library
npx -y skills add stephenrogan/leadership-skills --skill hiring-loopAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Creates a structured hiring loop with role scorecard, competencies, interview plan, question bank, evidence rubric, debrief packet, and bias checks. Use when opening a role, designing interviews, consolidating feedback, or preparing a hire/no-hire debrief.
The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
4.2 KB, as published. Nobody here has run it
Hiring Loop
Overview
Use this skill to support the leader as Team builder. A hiring loop that evaluates evidence against role needs instead of vibes and recency bias.
This skill is human-led by design: the agent prepares the work, but the human leader owns judgment, relationship, accountability, and final decisions.
When to Use
Run this skill when:
- New or replacement role is approved
- Interview loop needs design
- Candidate feedback is scattered or inconsistent
Do not use it as a substitute for legal, HR, finance, security, medical, or executive approval. If the workflow affects employment, compensation, customer commitments, external messaging, or sensitive personal data, prepare the packet and stop for human review.
Inputs
Ask for or gather:
- Role outcomes and competencies
- Must-have and nice-to-have requirements
- Interview notes and scorecards
- Team gaps and ramp expectations
If inputs are missing, proceed with explicit assumptions and label confidence. Do not invent private context, motives, or facts.
Workflow
Follow this sequence:
- Define role outcomes before interview questions
- Map each interview to competencies and evidence needed
- Create behavioural questions and score rubric
- Consolidate debrief evidence by competency
- Flag missing evidence, inconsistencies, and possible bias
Before finalizing, run the boundary check: what is evidence, what is interpretation, what is a recommendation, and what must remain a human decision?
Output Format
Produce a concise, decision-ready artifact using this structure:
# Hiring Loop
## Situation
[Brief context and why this workflow is being run.]
## Evidence and Signals
- Fact:
- Pattern:
- Hypothesis, confidence:
## Recommended Focus
1. [Highest leverage focus]
2. [Second focus]
3. [Third focus, optional]
## Working Artifact
[Agenda, memo, brief, plan, map, script, or tracker depending on the workflow.]
## Human Decisions Required
- [Decision/action the agent must not take.]
## Follow-Up
- Owner:
- Date:
- Success signal:
Expected deliverables:
- Role scorecard
- Interview loop plan
- Question bank
- Debrief packet
- Evidence-gap and bias checklist
See assets/output-template.md for a reusable version.
Human Decision Boundary
The agent may prepare, synthesize, compare, draft, and track. The agent must not cross these boundaries:
- Do not make final hire/no-hire or compensation decision
- Do not infer protected characteristics or cultural fit vaguely
- Hiring manager owns final judgment and legal compliance
Stop and ask for explicit approval before sending messages, changing employment status, making customer promises, publishing, sharing sensitive information, or committing budget/resources.
Quality Bar
A strong output for this skill:
- Separates facts, interpretations, hypotheses, and recommendations.
- Names uncertainty and missing context instead of hiding it.
- Produces an artifact a busy leader can use immediately.
- Reduces avoidance, ambiguity, rework, or decision drift.
- Makes the human judgment boundary visible.
- Includes concrete follow-up with owner, date, and success signal where applicable.
Failure Modes
Watch for these mistakes:
- Overconfident claims from thin notes or sentiment.
- Generic management advice with no artifact.
- Automating sensitive judgment instead of preparing it.
- Producing too many options without a recommended default.
- Treating leadership as text generation rather than accountability.
References
- Google re:Work structured interviewing
- Laszlo Bock, Work Rules!
- Structured interview validity research
For the shared methodology spine, see ../../docs/SOURCE-SPINE.md.