Individual skill
interview-debrief-synthesizer
Consolidates multiple interviewer scorecards into a calibrated hire/no-hire summary that foregrounds evidence, surfaces disagreement, and flags bias risks for a human panel. Use when you have collected scorecards or written feedback from a completed interview loop and need to run the debrief, calibrate divergent ratings, or produce a defensible decision write-up. Do NOT use when you are preparing questions or rubrics before interviews - use interview-question-kit instead.
skills/interview-debrief-synthesizer/SKILL.md
Source commit 97a13607d669157a4a16d5ba79b77f208319f7b9
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Instructions only
- Last checked
- Nov 11, 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)
- 24
- Repository last updated
- Oct 13, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- claude Repository topic
- claude-skills Repository topic
- skill-me Repository topic
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 4,641 bytes
Read excerpt
# Interview Debrief Synthesizer
Turn a set of independent interviewer scorecards into one calibrated, evidence-led decision summary that a human panel can defend.
## Workflow
1. **Gather inputs.** Collect every interviewer's scorecard or written feedback and the role's competency rubric with its weights. If the rubric is missing, ask for it; do not infer a bar from the comments. Push to run the synthesis within 48 hours of the final interview - recall of specific candidate answers decays fast, and evidence gathered late drifts toward impression.
2. **Aggregate against the shared rubric.** Map each interviewer's ratings to the defined competencies. Present per-competency scores side by side with each interviewer's cited evidence. Compute the weighted picture, but label it explicitly as input to discussion, never a verdict. Flag any competency no interviewer actually assessed, and treat any competency assessed by only one interviewer as thin coverage worth naming.
3. **Surface disagreement instead of averaging it.** Where interviewers diverge by 2 or more points on the same competency, show both ratings with both sides' evidence. Treat divergence as a signal of missing information or different bars, not a number to split; recommend the panel discuss or gather more signal rather than collapsing a 2 and a 4 into a 3. Divergence of a single point is normal calibration noise - do not manufacture a controversy from it.
4. **Separate evidence from impression.** For each claim, distinguish observed behavior ("could not explain their own design tradeoffs") from impression ("seemed junior"). Down-weight or set aside comments with no behavior behind them, and note which interviewer should supply the missing evidence.
5. **Flag bias and process risks.** Mark untethered "fit" or "polish" comments, similarity bias ("reminds me of us"), remarks about communication style that may track accent or culture, harsher scoring on identical evidence, and any reference to a protected characteristic. Frame these as risks for the panel to examine, not as accusations.
6. **Frame the decision and its rationale.** Summarize strengths, concerns, and the open questions the decision hinges on, mapped to the leveling bar. Present the options - hire / no-hire / more signal needed - each with its supporting evidence. Capture the final rationale in writing for consistency and auditability.
## Deliverable