evaluating-candidates

evaluating-candidates is a skill for Claude Code, Codex from cnfeat/top-pm-skills. It costs 47 tokens per session (970 once invoked), scanned A, original, MIT.

A structured guide for evaluating job candidates, including interviews, work samples, references, and final hiring decisions.

In plain words
What is it for?
Use it when screening candidates, reviewing take-home work, conducting reference checks, calibrating evaluations, or choosing between finalists.
Why use it?
It reduces reliance on gut feeling and helps compare candidates using consistent evidence and a clear hiring standard.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it when screening candidates, reviewing take-home work, conducting reference checks, calibrating evaluations, or choosing between finalists.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/cnfeat/top-pm-skills/evaluating-candidates
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add cnfeat/top-pm-skills --skill evaluating-candidates
Clone the repo
git clone --depth 1 https://github.com/cnfeat/top-pm-skills

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for evaluating-candidates

README.md
[![agentmods](https://agentmods.dev/badge/skills/cnfeat/top-pm-skills/evaluating-candidates/github.svg)](https://agentmods.dev/skills/cnfeat/top-pm-skills/evaluating-candidates)
Your own site
<a href="https://agentmods.dev/skills/cnfeat/top-pm-skills/evaluating-candidates"><img src="https://agentmods.dev/badge/skills/cnfeat/top-pm-skills/evaluating-candidates/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for evaluating-candidates

Your own site · 80×15
<a href="https://agentmods.dev/skills/cnfeat/top-pm-skills/evaluating-candidates"><img src="https://agentmods.dev/badge/skills/cnfeat/top-pm-skills/evaluating-candidates.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 47 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 970 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00047 $0.00970
Opus 5 $0.00023 $0.00485
Sonnet 5 $0.00009 $0.00194
Haiku 4.5 $0.00005 $0.00097

Measured 11d ago against content hash b476411a284c, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

evaluating-candidates scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 11d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

参考skill/lenny-skills-main (2)/lenny-skills-main/skills/evaluating-candidates/SKILL.md · 84 lines

How it starts

The opening of the file, as written. The whole thing — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Evaluating Candidates

Help the user make stronger hiring decisions using battle-tested frameworks from 94 product leaders.

How to Help

When the user asks for help evaluating candidates:

  1. Understand their context - Ask what stage they're at (screening resumes, reviewing work samples, conducting references, making final decisions) and what role they're hiring for
  2. Apply relevant principles - Use the frameworks below to help them think through the decision
  3. Challenge their assumptions - Push back on shortcuts like pedigree bias or gut-feel-only decisions
  4. Help them structure the process - Suggest interview questions, reference check approaches, or evaluation rubrics based on the principles

Core Principles

Reference checks trump interviews

Shishir Mehrotra: "I generally value the reference check over interview signals. Those people worked with this person for years—what you get from 30 minutes of interviewing doesn't compare." Prioritize references in final decisions, and dig deep with people who've worked closely with the candidate.

Hire for team balance, not unicorns

Adam Fishman: "The goal is not to find someone who's 11/10 on everything—that person doesn't exist. Create a well-rounded team by hiring to fill gaps in your portfolio." Before opening a role, map your team's current strengths and weaknesses.

Use paid work trials

Elena Verna: "We do 2-3 day paid work trials to see candidates in action—how they handle chaos and lack of clarity. This company is not for everybody." Work trials reveal what interviews cannot: how someone actually operates.

Prioritize agency over experience

Albert Cheng: "High agency and 'clock speed' are better predictors than deep experience. Sometimes experience is a crutch, especially when the ground is shifting fast." Look for candidates who took initiative outside formal channels.

Structure first, intuition after

Annie Duke: "If you use intuition after a structured evaluation—not before—you drastically improve your hit rate." Complete your rubric before letting gut feel influence the decision.

Read the full file on GitHub · 84 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 11d ago First seen · 84 lines · 47 tokens per session scan A b476411a284c

Subscribe to this mod's changes

evaluating-candidates is a skill published in the GitHub repository cnfeat/top-pm-skills (48 stars, last pushed 3mo ago), licensed MIT. It adds 47 tokens to every session and 970 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.