Individual skill

hire-or-pass

Turn a hiring debrief into a typed decision — hire, hire at a different level, get more signal, or pass — from rubric evidence only, with probabilities and confidence. Use when asked should we hire this candidate, run the debrief, hire or no-hire, or when interviewers disagree and the manager has to call it. Produces the evidence state per competency, the four-way decision with probabilities, the act-or-hold verdict, and when holding, the exact competency to test and who tests it. Decision support for a human decision — a person owns the hire.

plugins/pm-decisions/skills/hire-or-pass/SKILL.md

Read pinned source

Source commit f7c90bc09ee05dc25cf257bdb1826f2c2552c2cb

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 9, 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)
1,538
Repository last updated
Nov 9, 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

# Hire or Pass

Debriefs go wrong when the loudest interviewer wins or when everyone waits to see what the manager thinks. This skill forces the evidence into a fixed shape — per competency, strongest example and strongest counter-example, from whom — and defines the four possible outcomes before the discussion starts. The output is a distribution over those outcomes and, when it is close, the *specific* extra signal to go get.

**Boundary.** This is decision support. A person makes and owns the hiring decision, applies the company's process and the law where they are, and is accountable for it. Never let a distribution replace that.

## Where this sits

After [`hiring-rubric`](../hiring-rubric/SKILL.md) (which defines the competencies) and [`engineering-hiring-rubric`](../engineering-hiring-rubric/SKILL.md), and after the interviews. This one runs the debrief decision.

## What This Skill Produces

- **The evidence state** — per must-have competency: strongest example, strongest counter-example, which interviewer saw it, rubric scores
- **The decision** — `hire` / `hire_at_different_level` / `more_signal` / `pass` with probabilities and confidence
Back to top