candidate-scorecard ยท git:20260714.b87d8d4 ยท 2026-07-14 ยท sha256 04a5f131c709db0a
candidate-scorecard git:20260714.b87d8d4A
Immutable. This exact content is served forever at /api/v1/blob/04a5f131c709db0a.
---
name: candidate-scorecard
description: "Turn interview notes into a structured candidate scorecard and hire recommendation. Use when asked to write an interview scorecard, a candidate evaluation, an interview debrief, or to summarize feedback into a hire/no-hire call. Produces a per-competency assessment with evidence and ratings, an overall recommendation with confidence, and the open questions for the next round โ evidence-based, bias-aware, and decision-ready."
homepage: https://mohitagw15856.github.io/pm-claude-skills/skill/candidate-scorecard.html
metadata:
{
"openclaw": { "emoji": "๐งฒ" }
}
---
# Candidate Scorecard Skill
A scorecard converts a fuzzy "I liked them" into an evidence-based, comparable evaluation. It rates the
candidate against the **same competencies** the role defined, ties each rating to **specific evidence** from the
interview, and lands a clear recommendation โ so debriefs are about evidence, not who argues hardest. (For the
role's question set and competencies, pair with [`interview-question-bank`](../interview-question-bank/SKILL.md).)
## Working from a brief
Given rough interview notes, **produce the full scorecard anyway** โ organize the evidence under the relevant
competencies and give a rating + recommendation, marking where evidence is thin *(low confidence / probe next
round)*. Never invent things the candidate said; if a competency wasn't assessed, say so rather than guessing.
## Required Inputs
Ask for these only if they aren't already provided (else mark as not assessed):
- **The role & competencies** โ what's being assessed (or use the role's interview kit).
- **Interview notes** โ what the candidate said/did, ideally with examples.
- **The interview scope** โ which round/competencies this interviewer covered.
- **Scale** โ the rating scale to use (e.g. 1โ4: strong no / no / yes / strong yes).
## Output Format
### Candidate Scorecard: [name] โ [role]
- **Summary** โ one-line read: overall rating and the headline reason.
- **Per-competency assessment** โ for each competency assessed:
| Competency | Rating | Evidence (what they said/did) | Concern / gap |
|---|---|---|---|
Mark any competency you couldn't assess as **Not assessed**.
- **Strengths** โ the 2โ3 clearest, evidence-backed.
- **Risks / gaps** โ the real concerns, with the evidence (not vibes).
- **Open questions for next round** โ what to probe to resolve uncertainty.
- **Recommendation** โ Hire / No hire / Lean yes / Lean no, with a **confidence level** and the one-sentence rationale.
## Quality Checks
- [ ] Every rating is tied to specific evidence from the interview, not impressions
- [ ] Competencies not actually assessed are marked "Not assessed", not guessed
- [ ] Strengths and risks are concrete and balanced โ not a one-sided narrative
- [ ] The recommendation states a confidence level and what would change it
- [ ] Open questions hand the next interviewer something specific to probe
- [ ] No invented quotes/claims; bias-prone "culture fit" is replaced with job-related evidence
## Anti-Patterns
- [ ] Do not rate on overall vibe โ anchor each score to what the candidate actually demonstrated
- [ ] Do not invent or embellish what they said to justify a rating
- [ ] Do not score competencies you didn't test โ flag them for the next round
- [ ] Do not hide low confidence behind a confident-sounding verdict โ say how sure you are
- [ ] Do not lean on "culture fit" as a reason โ name the specific, job-related concern
## Based On
Structured-hiring practice โ competency ratings anchored to evidence, calibrated recommendations with confidence, and bias-aware, decision-ready debriefs.