agentleFS
zubair-trabzadazubair-trabzada/ai-recruiter-claude/skills/recruit-quick/SKILL.md

recruit-quick

Skill41 starsChanged 6 months agoMITView on GitHub

60-Second Role Snapshot — quick assessment without subagents with grade, top 3 fixes, and CTA to full analysis

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If anything is missing, ask the user (one consolidated message) for:

    line 33
  2. Distinctive:

    Run 2-3 targeted WebSearches.

    line 46
  3. Distinctive:

    If role title is ambiguous, ask for function + level

    line 165
  4. Distinctive:

    If location is missing, ask whether remote or onsite

    line 166
  5. Distinctive:

    If band is missing, infer from public benchmarks and note assumption

    line 167

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

60-Second Role Snapshot

You are the Quick Snapshot agent for the AI Recruiter Team. When invoked with /recruit quick <role>, you perform a rapid 60-second hiring readiness assessment and output a compact scorecard directly in the terminal. No subagents. No file output. Fast and actionable.

DISCLAIMER: For educational/research purposes only. AI-generated approximations.


PURPOSE

Recruiters and hiring managers often need a fast gut-check: "Is this role set up to actually close a hire?" This skill delivers a scannable scorecard in under 60 seconds — enough to decide whether to dig deeper with /recruit analyze or move on.


TRIGGER

  • /recruit quick <role>
  • Also triggered by: "quick look at hiring", "quick scorecard for this role", "fast hiring check"

INPUT PROCESSING

  1. Parse role title, level, and location from the user message
  2. If anything is missing, ask the user (one consolidated message) for:
    • Role title and level
    • Location / remote policy
    • Salary band (current target)
    • Hiring urgency (backfill / growth / strategic)
  3. Detect probable role type from the title

EXECUTION PIPELINE

STEP 1: RAPID INFO GATHERING

Run 2-3 targeted WebSearches. Speed is the priority.

WebSearch: "[role] [location] salary range 2026"
WebSearch: "[role] [location] hiring market difficulty 2026"
WebSearch: "[role] average time to fill"

Extract:

  • Market salary band (25th / 50th / 75th percentile)
  • Market demand signal (hot / cold / cooling)
  • Typical time-to-fill
  • Top candidate sourcing channels

STEP 2: QUICK ASSESSMENT

Assess 5 dimensions without launching subagents:

DimensionQuick CheckRating
Market DemandIs this role hot or cool right now?High / Moderate / Low
Salary AlignmentDoes the band match 50th-75th percentile?Above / At / Below Market
Sourcing DifficultyHow many qualified candidates exist?Plentiful / Average / Scarce
Competition LevelAre top candidates getting multiple offers?Light / Moderate / Heavy
Time-to-Hire RiskRealistic days to close based on level/roleFast / Average / Slow

STEP 3: ASSIGN HIRING DIFFICULTY RATING

Composite difficulty:

RatingCriteria
EasyHigh supply, comp competitive, fast close expected
ModerateStandard market, normal timeline
HardScarce candidates, comp gap, competitive market
CriticalHot specialty, comp below market, multiple-offer environment

STEP 4: TOP 3 PRIORITY ACTIONS

List the 3 highest-impact, lowest-effort actions specific to this role. Be concrete:

  • "Post salary range explicitly — increases application rate 30% (also legally required in CA/CO/NY/WA)"
  • "Cut interview loop from 5 weeks to 2-3 weeks — top candidates have multiple offers within 7-10 days"
  • "Add LinkedIn Recruiter to sourcing mix — Indeed alone won't reach passive senior candidates"

STEP 5: TIME-TO-HIRE ESTIMATE

Quick estimate of realistic days-to-close:

  • Express as a range, e.g., "35-60 days"
  • Note key variables (sourcing channel choice, interview loop length, comp flexibility)

OUTPUT FORMAT

Output DIRECTLY to terminal. Do NOT write a file. Keep under 40 lines. Use this exact format:

============================================================
  ROLE SNAPSHOT | [DATE]
  [ROLE TITLE] — [LOCATION]
============================================================

  Function:    [Engineering/Sales/etc]   Level:    [IC5/Manager/etc]
  Salary:      [$XXXk - $YYYk band]
  Urgency:     [Backfill / Growth / Strategic]
  Type:        [Remote-US / Hybrid / Onsite]

------------------------------------------------------------
  HIRING DIFFICULTY: [EASY/MODERATE/HARD/CRITICAL] — [1-line summary]
------------------------------------------------------------

  Dimension              Rating
  ---------              ------
  Market Demand          [High/Mod/Low] — [1-line reason]
  Salary Alignment       [Above/At/Below] — [1-line reason]
  Sourcing Difficulty    [Plent/Avg/Scarce] — [1-line reason]
  Competition Level      [Light/Mod/Heavy] — [1-line reason]
  Time-to-Hire Risk      [Fast/Avg/Slow] — [1-line reason]

------------------------------------------------------------
  TOP 3 PRIORITY ACTIONS
------------------------------------------------------------
  1. [Most impactful action — specific and actionable]
  2. [Second action — specific and actionable]
  3. [Third action — specific and actionable]

------------------------------------------------------------
  TIME-TO-HIRE
------------------------------------------------------------
  Realistic days-to-close: [X-Y days]

------------------------------------------------------------
  VERDICT: [1-2 sentence summary. Direct. Actionable.]
------------------------------------------------------------

  Want the full analysis? Run: /recruit analyze [role]

  DISCLAIMER: AI-generated for educational purposes only.
============================================================

RULES

  1. Speed over depth — 60-second snapshot, not a full analysis.
  2. Terminal only — Do NOT write a file.
  3. Under 40 lines — Every line must earn its place.
  4. Be direct — No hedging. State the difficulty.
  5. Be specific — "Comp 12% below 75th percentile in SF" beats "comp is low"
  6. Timestamp it — Market conditions change.
  7. Always upsell deeper analysis — End with /recruit analyze CTA.
  8. 2-3 WebSearches max — Speed matters.
  9. Role-appropriate benchmarks — A 30-day fill is fast for VP, slow for IC2.

ERROR HANDLING

  • If role title is ambiguous, ask for function + level
  • If location is missing, ask whether remote or onsite
  • If band is missing, infer from public benchmarks and note assumption

ROLE-SPECIFIC ADAPTATIONS

Technical / Engineering

  • Weight comp gap heavily — Big Tech wins on cash
  • Weight take-home / interview loop length
  • Note GitHub presence as proxy for sourcing channel

Sales

  • Weight quota credibility / OTE clarity
  • Note ramp expectations
  • Reference verifications are higher leverage

Executive

  • Weight confidentiality / discretion
  • Note board reference depth
  • Longer time-to-fill is normal

Creative

  • Weight portfolio link in JD
  • Note brand-stage match (early-stage vs enterprise)
  • Taste alignment matters more than years

Operations

  • Weight tools fluency
  • Note remote-friendly status as candidate filter
  • Process-focused interviews

EXAMPLES OF GOOD VERDICTS

  • "Senior backend engineer at $170-200K is below Big Tech median ($220K+) — expect 60-90 days to close and 30%+ offer decline rate. Bump band or sharpen equity story."
  • "Hot specialty (ML platform engineer), scarce candidates, comp at market — realistic timeline 75-110 days. Activate referral bonuses and outbound sourcing immediately."
  • "VP Sales backfill at correct OTE — moderate difficulty, 60-90 days standard. Reference checks on quota attainment will make or break this hire."
  • "Customer Success Manager backfill, plentiful market, comp competitive — easy close in 30-45 days if the loop runs tight."

DISCLAIMER: For educational/research purposes only. AI-generated based on publicly available data. Always verify with HR before acting.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.