Structured hiring framework from 94 product leaders to make stronger candidate decisions.
Works with
Apply 12 core principles covering reference checks, work trials, agency assessment, and T-shaped hiring to evaluate candidates systematically
Use diagnostic questions to understand hiring stage, team gaps, and whether decisions are based on structured rubrics or intuition alone
Challenge common biases like pedigree shortcuts, gut-feel-only decisions, and unicorn hiring; prioritize references, pa
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionevaluating-candidatesExecute the skills CLI command in your project's root directory to begin installation:
Fetches evaluating-candidates from refoundai/lenny-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate evaluating-candidates. Access via /evaluating-candidates in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
616
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
616
stars
Help the user make stronger hiring decisions using battle-tested frameworks from 94 product leaders.
When the user asks for help evaluating candidates:
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.
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.
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.
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.
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.
Ben Horowitz: "We're investing in strength, not lack of weakness. Does this person have a world-class strength that can beat anybody? Surround them with people who cover their gaps."
Adam Grenier: "Comfort with chaos and willingness to do things they haven't done in 15 years are huge signals. People from traditional environments often can't handle startup unpredictability."
Adam Grenier: "Every senior hire has a T-shaped career. Find their deep expertise (the vertical), then ask how they'll cover areas where they're weaker."
Albert Cheng: "High agency shows up outside formal interviews—the questions they ask, whether they've actually tried your product, the energy in their scheduling emails."
Austin Hay: "School prestige or resume gaps are bad shortcuts. Investigate gaps—they may represent intense self-directed learning."
Bill Carr (Amazon): "Have someone outside the hiring manager's chain run the debrief meeting with veto power. This counteracts urgency bias and keeps the bar high."
Brian Tolkin: "Match the candidate's specific background to the product's needs. A technical product needs a technical PM. Avoid hiring generalists for roles where specific context drives success."
Bangaly Kaba: "Ask candidates to stack-rank five skills from strongest to weakest. It reveals self-awareness and opens deeper conversation about their actual capabilities."
Benjamin Mann (Anthropic): "People stay when they're mission-oriented. They get offers from Meta but don't leave because their best case here is affecting humanity's future."
Use these to diagnose where they need help:
For all 151 insights from 94 guests, see references/guest-insights.md
Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
mattpocock/skills
We added evaluating-candidates from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Registry listing for evaluating-candidates matched our evaluation — installs cleanly and behaves as described in the markdown.
evaluating-candidates fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
I recommend evaluating-candidates for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
evaluating-candidates reduced setup friction for our internal harness; good balance of opinion and flexibility.
evaluating-candidates fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
We added evaluating-candidates from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Keeps context tight: evaluating-candidates is the kind of skill you can hand to a new teammate without a long onboarding doc.
Useful defaults in evaluating-candidates — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
evaluating-candidates has been reliable in day-to-day use. Documentation quality is above average for community skills.
showing 1-10 of 57