agentsclimarketplace

Hiring loop

Skill stephenrogan/leadership-skills/skills/hiring-loop

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.From its SKILL.md

Install
npx -y skills add stephenrogan/leadership-skills --skill hiring-loop

Assembled 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 file declares

Copied from the file, not written here

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, 760 tokens by cl100k_base, 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:

  1. Define role outcomes before interview questions
  2. Map each interview to competencies and evidence needed
  3. Create behavioural questions and score rubric
  4. Consolidate debrief evidence by competency
  5. 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.

What ships with it: 3 files

4.3 KB alongside SKILL.md

assets/

evals/

references/

Gives 0 of the 12 instructions most hr recruiting skills give in 760 tokens

Counted across 356 of the 357 authors here whose files we hold, read 2026-08-07

  • Quantify achievements with specific metricsin 14 of 356, across 6 files
  • Keep the resume under two pagesin 14 of 356, across 6 files
  • Request the full job description if not providedin 12 of 356, across 4 files
  • Extract keywords and prioritize job requirementsin 12 of 356, across 4 files
  • Stop and ask for clarification if required inputs are missingin 12 of 356, across 5 files
  • Map candidate experience to job requirementsin 11 of 356, across 3 files
  • Ask if the user wants adjustmentsin 11 of 356, across 3 files
  • Provide strengths and gap analysis after the resumein 10 of 356, across 2 files
  • Request candidate background details if not providedin 10 of 356, across 2 files
  • Format experience bullets as action verb plus resultin 10 of 356, across 2 files
  • Ask for missing inputs before startingin 10 of 356, across 9 files
  • Use exact job description terminologyin 9 of 356, across 1 file

Said here and by no other author read

  • Define role outcomes before interview questions
  • Create behavioral questions and score rubric
  • Consolidate debrief evidence by competency
  • Flag missing evidence inconsistencies and possible bias
  • Label confidence when proceeding with assumptions
  • Separate facts interpretations hypotheses and recommendations

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.