skills/by-role/recruiter/candidate-debrief/SKILL.md
Structure and run a post-interview candidate debrief. Use when the user says "run the debrief", "how do we decide on this candidate", "let's calibrate", "we need to make a hire/no-hire call", "prep the debrief meeting", or wants to structure the decision-making process after interviews are complete - even if they don't explicitly say "debrief". Also use when a recruiter wants to prevent groupthink or HiPPO effect (highest paid person's opinion) from dominating the decision.
npx skillsauth add qa-aman/claude-skills candidate-debriefInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Based on Who: The A Method for Hiring (Smart & Street) and Work Rules! (Laszlo Bock). Unstructured debriefs default to the loudest voice, the most senior person, or whoever interviewed last. A calibrated debrief separates evidence from impression, surfaces disagreement before consensus forms, and produces a decision anchored in scorecard data - not gut feel.
This is the most important rule: scorecards must be submitted independently before anyone discusses the candidate. Once people hear each other's opinions, anchoring kicks in and individual assessments become unreliable.
Before the debrief meeting:
Debrief agenda:
1. Ground rules (2 min) - recruiter facilitates
2. Independent scorecard read-out (10-15 min) - each interviewer shares their
rating and top evidence before open discussion
3. Discuss disagreements (10-15 min) - focus on evidence gaps, not vibes
4. Decision (5 min) - hire / no-hire, or identify what's still unknown
5. Next steps (3 min) - offer, decline, or additional interview
Go around the room in reverse seniority order. Junior interviewers speak first to prevent anchoring on the hiring manager's view.
For each interviewer:
Recruiter records this without editorial comment. Do not allow discussion during the read-out phase.
After all read-outs, the recruiter identifies disagreements:
For each disagreement, ask: "What specific evidence supports your rating?" Not "Why do you feel that way?"
Common disagreement sources:
If the disagreement can't be resolved with existing evidence, name it explicitly: "We have conflicting data on [competency]. We either accept the uncertainty and decide, or schedule a targeted follow-up."
From Work Rules! (Bock): the best hires come from calibrated committees, not from managers hiring in their own image. Run these checks before the final decision:
Bar-raiser check: Would this candidate raise the average performance level of the team? If the team is a 7/10, does this candidate rate above 7?
Regret minimization: Which is worse - hiring someone who underperforms, or losing this candidate to a competitor? Use this to calibrate risk tolerance, not to override data.
Counterfactual test: "If this candidate's resume showed up in our pipeline 6 months from now after we've hired someone else, would we be upset we missed them?"
Decision categories:
HIRE - Strong Yes majority, no Strong No votes
→ Move to offer
HIRE WITH RESERVATIONS - Yes majority, at least one No
→ Document the specific reservation, define how it will be managed onboard
NO HIRE - No majority, or any Strong No with corroborating evidence
→ Decline. Do not "create a role" to accommodate someone who didn't clear the bar.
HOLD FOR MORE DATA - Genuine evidence gap on a critical competency
→ Schedule one targeted follow-up interview focused only on the gap.
Cap at one hold per candidate. Two holds is a soft no.
If the group is split, the hiring manager makes the final call. The recruiter's role is to ensure the decision is based on scorecard evidence, not politics.
For every candidate, document:
This documentation serves calibration for future hires and provides defensible records.
1. Allowing pre-debrief discussion Bad: "Quick Slack before the meeting - she was fantastic, right?" Good: Scorecards submitted independently. No discussion until the structured read-out.
2. Starting with the hiring manager's opinion Bad: Hiring manager leads: "I thought she was great, especially her answer on X..." Good: Junior interviewers speak first. Hiring manager synthesizes last.
3. Conflating impression with evidence Bad: "I just got a great vibe from him. He'd fit our culture." Good: "He described rebuilding the deployment pipeline solo at his last company - that's the ownership signal we need."
4. The "create a role" trap Bad: "She's not right for this role but she seems talented - can we find something for her?" Good: Evaluate against this role's scorecard only. If she doesn't clear the bar, decline. The "create a role" pattern inflates headcount and dilutes talent density.
5. Over-indexing on one interview Bad: "Her system design interview was excellent, so I'm willing to overlook the weak behavioral round." Good: All competencies on the scorecard are load-bearing. An A on one and C on another is a C-level hire.
6. Treating "hold for more data" as the safe default Bad: Every close call gets a third interview to defer the decision. Good: One hold is acceptable for a genuine evidence gap. Two is avoidance. Make the call.
development
Plan a webinar end-to-end using April Dunford's Obviously Awesome positioning framework to find the topic angle that makes the webinar obviously valuable to the right audience. Produces topic positioning, abstract, speaker brief, registration page, promotion sequence, day-of run-of-show, and post-webinar follow-up. Use when the user asks to plan a webinar, virtual event, online workshop, "we need a webinar on X", host a webinar, online masterclass, or any live virtual event with promotion and follow-up. Reads ICP, services, and brand voice from knowledge/.
development
Write long-form thought leadership articles, opinion pieces, industry POV essays, and CEO/founder bylines using the Made to Stick SUCCESs framework (Chip and Dan Heath). Use when the user asks for a long-form article, executive byline, opinion piece, industry POV, manifesto, "explain our point of view on X", or wants to publish an authority-building piece (1200-2500 words). Reads brand voice and positioning from knowledge/.
development
Plan a monthly content calendar across channels using the Content Marketing Matrix (Dave Chaffey, Smart Insights) - Entertain/Inspire/Educate/Convince. Every post gets a quadrant label. The monthly calendar must hit 40% Educate, 40% Inspire+Convince, 20% Entertain. Produces a week-by-week posting schedule with topics, formats, channels, and asset links. Use when the user says "content calendar", "social calendar", "plan next month's content", "what should we post", "content plan", "editorial calendar", "schedule posts for the month", or wants a structured posting plan for LinkedIn, Twitter, email, or blog. Reads brand voice, ICP, and past learnings from knowledge/.
development
Write SEO-optimized long-form articles targeting specific keywords using the They Ask You Answer Big 5 framework (Marcus Sheridan). Articles are categorized by Big 5 type (Cost, Problems, Versus, Best/Reviews, How-To) and structured accordingly. The "answer first" rule applies to every article. Use when the user asks for an SEO article, blog post for ranking, "rank for keyword X", organic content, search-optimized post, pillar page, or content for organic traffic. Includes keyword targeting, search intent matching, internal linking suggestions, and meta tags.