
hiring-recruitment
Master hiring processes, interviewing, candidate assessment, and building strong engineering teams
- Installs
- 162
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/pluginagentmarketplace/custom-plugin-engineering-manager --skill hiring-recruitment- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads hiring-recruitment automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Hiring & Recruitment Skill
Purpose
Provide engineering managers with comprehensive hiring frameworks, interview templates, and assessment tools for building strong engineering teams.
Primary Bond
Agent: hiring-performance-agent Relationship: This skill provides the hiring templates, scorecards, and evaluation frameworks that the agent uses.
Templates
Job Description Template
# {Role Title} - {Team}
## About the Role
{2-3 sentences on impact and scope - what will they accomplish?}
## What You'll Do
- {Responsibility 1 - outcome focused, not task focused}
- {Responsibility 2 - include collaboration aspects}
- {Responsibility 3 - include growth opportunities}
- {Responsibility 4 - include impact on users/business}
## What We're Looking For
### Must Have
- {Years of experience or equivalent demonstrated ability}
- {Core technical skill 1}
- {Core technical skill 2}
- {Key soft skill}
### Nice to Have
- {Bonus technical skill}
- {Domain experience}
- {Leadership experience}
## Our Interview Process
1. **Recruiter Screen** (30 min) - Background and mutual fit
2. **Technical Screen** (60 min) - Coding and problem-solving
3. **System Design** (60 min) - Architecture thinking
4. **Team Fit** (45 min) - Collaboration and values
5. **Hiring Manager** (45 min) - Final discussion
Expected timeline: 2-3 weeks
## What We Offer
- {Compensation range if public}
- {Key benefits}
- {Growth opportunities}
- {Culture highlights}
Interview Scorecard
interview_scorecard:
candidate: "{Name}"
role: "{Role}"
interviewer: "{Name}"
date: "{Date}"
interview_type: "{Technical | Design | Behavioral | Final}"
competencies:
technical_skills:
weight: 30%
score: null # 1-5
evidence: ""
strong_signals: []
concerns: []
problem_solving:
weight: 25%
score: null
evidence: ""
strong_signals: []
concerns: []
communication:
weight: 15%
score: null
evidence: ""
strong_signals: []
concerns: []
collaboration:
weight: 15%
score: null
evidence: ""
strong_signals: []
concerns: []
growth_mindset:
weight: 15%
score: null
evidence: ""
strong_signals: []
concerns: []
overall:
weighted_score: null
recommendation: null # Strong Hire | Hire | No Hire | Strong No Hire
summary: ""
next_steps: ""
scoring_guide:
5: "Exceptional - top 5% of candidates seen"
4: "Strong - clearly above bar"
3: "Meets bar - solid hire"
2: "Below bar - significant concerns"
1: "Far below bar - clear no hire"
Behavioral Interview Guide (STAR)
star_framework:
situation:
prompt: "Tell me about a time when..."
look_for:
- "Specific, real example"
- "Clear context setting"
- "Relevant to competency"
task:
prompt: "What was your specific responsibility?"
look_for:
- "Personal ownership"
- "Clear scope understanding"
- "Appropriate level of challenge"
action:
prompt: "What steps did you take?"
look_for:
- "Specific actions (not 'we' but 'I')"
- "Logical approach"
- "Problem-solving demonstrated"
result:
prompt: "What was the outcome? What did you learn?"
look_for:
- "Measurable impact"
- "Self-reflection"
- "Learning demonstrated"
sample_questions:
problem_solving:
- "Tell me about a time you solved a problem with incomplete information"
- "Describe a situation where you had to make a difficult trade-off"
- "Tell me about a technical decision you later regretted"
collaboration:
- "Tell me about a time you had a conflict with a teammate"
- "Describe a situation where you had to influence without authority"
- "Tell me about receiving critical feedback"
leadership:
- "Tell me about a time you mentored someone"
- "Describe a situation where you drove a significant change"
- "Tell me about a time you had to make an unpopular decision"
Hiring Pipeline Metrics
hiring_metrics:
funnel_metrics:
applications_to_screen: "{X}%"
screen_to_interview: "{X}%"
interview_to_offer: "{X}%"
offer_to_accept: "{X}%"
time_metrics:
time_to_first_response: "{X} days"
time_to_offer: "{X} days"
time_to_hire: "{X} days"
quality_metrics:
new_hire_90_day_retention: "{X}%"
new_hire_performance_rating: "{X}/5"
hiring_manager_satisfaction: "{X}/5"
targets:
time_to_hire: "<45 days"
offer_acceptance: ">80%"
90_day_retention: ">95%"
diversity_pipeline: ">40%"
red_flags:
time_to_hire: ">60 days"
offer_acceptance: "<60%"
90_day_retention: "<85%"
Decision Trees
Hire / No-Hire Decision
Scorecard Complete
|
+-- Any Strong No Hire?
| +-- Yes -> No Hire (single strong no is veto)
| +-- No -> Continue
|
+-- Weighted score >= 3.0?
| +-- No -> No Hire
| +-- Yes -> Continue
|
+-- Any critical competency < 3?
| +-- Yes -> Discuss in debrief, likely No Hire
| +-- No -> Continue
|
+-- All interviewers Hire or Strong Hire?
| +-- Yes -> Make offer
| +-- No -> Debrief discussion, address concerns
Offer Negotiation
Candidate requests higher comp
|
+-- Within approved range?
| +-- Yes -> Can approve, consider value
| +-- No -> Continue
|
+-- Top candidate for role?
| +-- Yes -> Escalate for exception
| +-- No -> Continue
|
+-- Can we offer other value?
| +-- Yes -> Negotiate (signing bonus, equity, title, start date)
| +-- No -> Explain our position, give time to decide
Anti-Patterns
anti_patterns:
culture_fit_trap:
symptom: "Hiring people just like us"
remedy:
- "Define 'culture add' not 'culture fit'"
- "Diverse interview panels"
- "Structured evaluation criteria"
halo_effect:
symptom: "One great answer overshadows all else"
remedy:
- "Structured scorecards for each competency"
- "Multiple interviewers for same competency"
- "Calibration before debrief"
urgency_hire:
symptom: "We need someone NOW"
remedy:
- "Bad hire costs more than waiting"
- "Consider contractors for immediate needs"
- "Never lower the bar"
confirmation_bias:
symptom: "Looking for evidence to confirm first impression"
remedy:
- "Document evidence before scoring"
- "Score independently before debrief"
- "Assign devil's advocate in debrief"
Quick Reference Cards
Interview Debrief Structure
1. Scores submitted independently (before meeting)
2. Go around - each interviewer shares (2 min each)
- Overall recommendation
- Key evidence (specific examples)
- Top concern
3. Discussion of disagreements
4. Hiring manager makes final call
5. Document decision and reasoning
Red Flags to Watch
red_flags:
technical:
- "Cannot explain their own code"
- "No questions about the codebase"
- "Blames others for past failures"
behavioral:
- "Uses 'we' exclusively (no personal ownership)"
- "No examples of learning from mistakes"
- "Dismissive of questions"
cultural:
- "Badmouths previous employers"
- "No interest in team dynamics"
- "Unwilling to receive feedback"
Candidate Experience Checklist
candidate_experience:
before:
- "Clear job description"
- "Fast initial response (<48h)"
- "Interview prep materials sent"
during:
- "Interviewers prepared and on time"
- "Candidate can ask questions"
- "Respectful, welcoming atmosphere"
after:
- "Timeline communicated"
- "Feedback provided (if rejected)"
- "Offer delivered promptly"
Troubleshooting
| Problem | Root Cause | Solution |
|---|---|---|
| Not enough candidates | Poor JD, wrong channels | Revise JD, expand sourcing |
| High drop-off after screen | Process too slow, poor experience | Speed up, improve communication |
| Offers declined | Comp, culture, opportunity | Exit survey, adjust offer |
| Bad hires | Weak interview process | Structured interviews, calibration |
Validation Rules
input_validation:
role_level:
type: enum
values: [junior, mid, senior, staff, principal, manager, director]
required: true
urgency:
type: enum
values: [low, medium, high, critical]
default: medium
team_context:
type: object
properties:
size: { type: integer }
current_gaps: { type: array }
required: false
Resources
Books:
- Who: The A Method for Hiring - Geoff Smart
- The Effective Hiring Manager - Mark Horstman
- Work Rules! - Laszlo Bock
Tools:
- Structured interview training
- Unconscious bias training
- Calibration session templates
FAQ
What does the hiring-recruitment skill do?
Master hiring processes, interviewing, candidate assessment, and building strong engineering teams
How do I install hiring-recruitment?
Run npx skills add https://github.com/pluginagentmarketplace/custom-plugin-engineering-manager --skill hiring-recruitment in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/hiring-recruitment/ (personal) or .claude/skills/hiring-recruitment/ (project).
Which AI agents can use hiring-recruitment?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is hiring-recruitment safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains hiring-recruitment?
It is published by pluginagentmarketplace in pluginagentmarketplace/custom-plugin-engineering-manager. It has 162 recorded installs.
Popular business & finance skills
sales-enablement
coreyhaines31/marketingskills
When the user wants to create sales collateral, pitch decks, one-pagers, objection handling docs, or demo scripts. Also use when the user mentions 'sales deck,' 'pitch deck,' 'one-pager,' 'leave-behind,' 'objection handling,' 'deal-specific ROI analysis,' 'demo script,' 'talk track,' 'sales playbook,' 'proposal template,' 'buyer persona card,' 'battle card,' 'battlecard,' 'competitive one-pager,' 'win-loss analysis,' 'why are we losing deals,' 'loss reasons,' 'how do I respond to this objection,' 'prospect just said,' 'help my sales team,' 'sales materials,' or 'what should I give my sales reps,' 'cold call script,' or 'voicemail script.' Use this for any document or asset that helps a sales team close deals. For public competitor comparison pages, see competitors. For running buyer interviews or churn research, see customer-research. For marketing website copy, see copywriting. For cold outreach emails, see cold-email. For the offer being sold (bonuses, guarantees, pricing structure),
revops
coreyhaines31/marketingskills
When the user wants help with revenue operations, lead lifecycle management, or marketing-to-sales handoff processes. Also use when the user mentions 'RevOps,' 'revenue operations,' 'lead scoring,' 'outbound pipeline stages,' 'lead routing,' 'MQL,' 'SQL,' 'pipeline stages,' 'deal desk,' 'CRM automation,' 'marketing-to-sales handoff,' 'data hygiene,' 'leads aren't getting to sales,' 'pipeline management,' 'lead qualification,' or 'when should marketing hand off to sales.' Use this for anything involving the systems and processes that connect marketing to revenue. For cold outreach emails, see cold-email. For email drip campaigns, see emails. For pricing decisions, see pricing.
sales-funnel-blueprint
autonnel/autonnel-skills
Turn an offer into a concrete multi-step sales funnel spec - page-by-page structure, price ladder, copy outline and the metrics each step must hit. Use when asked to build a sales funnel, marketing funnel, landing page flow, lead magnet funnel, webinar funnel, tripwire or VSL funnel, when planning a product launch page flow, or when someone asks "what pages do I need" for selling something online.
pricing
coreyhaines31/marketingskills
When the user wants help with pricing decisions, packaging, or monetization strategy. Also use when the user mentions 'pricing,' 'pricing tiers,' 'freemium,' 'free trial,' 'packaging,' 'price increase,' 'value metric,' 'Van Westendorp,' 'willingness to pay,' 'monetization,' 'how much should I charge,' 'my pricing is wrong,' 'pricing page,' 'annual vs monthly,' 'per seat pricing,' 'should I offer a free plan,' 'pricing page teardown,' 'pricing page audit,' 'is my pricing page AI-readable,' or 'can AI read my pricing.' Use this whenever someone is figuring out what to charge, how to structure their plans, or wants to audit a pricing page (for humans and for the AI agents that shortlist tools). For in-app upgrade screens, see paywalls. For offer construction (bonuses, guarantees, value framing, naming) on services/courses/coaching/high-ticket B2B, see offers.
cross-border-ecommerce
nexscope-ai/ecommerce-skills
Cross-border e-commerce expansion advisor. Scores target markets on 8 weighted dimensions (market size, ecommerce penetration, competition, regulatory complexity, logistics infrastructure, payment ecosystem, cultural distance, IP protection), compares 5 fulfillment models with cost and transit data, provides country-by-country tax/duty compliance guides (EU VAT/IOSS, UK VAT, US sales tax, CA GST, AU GST, JP consumption tax), maps local payment preferences by market, and builds a phased expansion roadmap. No API key required.
pricing-strategy
coreyhaines31/marketingskills
When the user wants help with pricing decisions, packaging, or monetization strategy. Also use when the user mentions 'pricing,' 'pricing tiers,' 'freemium,' 'free trial,' 'packaging,' 'price increase,' 'value metric,' 'Van Westendorp,' 'willingness to pay,' 'monetization,' 'how much should I charge,' 'my pricing is wrong,' 'pricing page,' 'annual vs monthly,' 'per seat pricing,' or 'should I offer a free plan.' Use this whenever someone is figuring out what to charge or how to structure their plans. For in-app upgrade screens, see paywall-upgrade-cro.