interview-debrief-synthesizer
Skill0 starsChanged 40 days agoMITView on GitHub
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.
In this repository9 other files it gives its agents.
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 6 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 26
Every score and concern in the summary is traceable to a named interviewer and cited evidence.
- Distinctive: line 33
Do not auto-decide, issue a final hire/no-hire, or rank the candidate against others by protected traits - this synthesis only informs a …
- Distinctive: line 34
Do not average away disagreement to produce a clean composite score.
- Distinctive: line 35
Do not let an unsupported impression carry weight.
- Distinctive: line 36
Do not evaluate on anything but job-relevant evidence.
- Distinctive: line 37
Do not synthesize from a partial loop.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Interview Debrief Synthesizer
Turn a set of independent interviewer scorecards into one calibrated, evidence-led decision summary that a human panel can defend.
Workflow
- 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.
- 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.
- 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.
- 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.
- 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.
- 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
Produce a debrief summary document containing: the per-competency score matrix (every interviewer's rating side by side with their cited evidence), the divergences of 2+ points each with both sides' evidence and the signal that would resolve it, the list of unassessed or thin-coverage competencies, the flagged bias and process risks, and the decision framing - hire / no-hire / more signal - with the evidence behind each option and space for the panel's written rationale.
Quality bar
- Every score and concern in the summary is traceable to a named interviewer and cited evidence.
- Divergences of 2+ points are shown, not silently reconciled; the summary names what additional signal would resolve each one.
- The output presents decision options with evidence; it never hands back a single number as the answer.
- Bias and uncovered-competency risks are called out explicitly for the hiring manager and recruiter.
Do NOT
- Do not auto-decide, issue a final hire/no-hire, or rank the candidate against others by protected traits - this synthesis only informs a human decision.
- Do not average away disagreement to produce a clean composite score.
- Do not let an unsupported impression carry weight; require the underlying behavior first.
- Do not evaluate on anything but job-relevant evidence. Strike or quarantine any input referencing age, race, gender, disability, family status, religion, national origin, or salary history, and apply the same bar to every candidate.
- Do not synthesize from a partial loop; if a scorecard is outstanding, chase it or mark the loop incomplete rather than deciding on partial coverage.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

