Skip to content

Instantly share code, notes, and snippets.

@v0lkan

v0lkan/SKILL.md

Created March 4, 2026 10:37
Show Gist options

  • Select an option

    Learn more about clone URLs
  • Save v0lkan/c7e51147c880624fdffe3569be110714 to your computer and use it in GitHub Desktop.

Select an option

Learn more about clone URLs
Save v0lkan/c7e51147c880624fdffe3569be110714 to your computer and use it in GitHub Desktop.
Download ZIP
Recruiter Responder
Raw
SKILL.md
name description
_recruiter-responder
Draft recruiter replies that are crisp, polite, and door-open (or not). Saves a ready-to-edit draft into an outbox folder.

Generate a high-quality reply to a recruiter email, aligned to the user's intent and constraints, then write the draft to an outbox folder so the user can edit and send.

This skill is optimized for repeatability: consistent tone, minimal over-sharing, and zero accidental commitments.

Inputs (What to ask the user for, if missing)

Collect only what’s needed. Default intelligently when absent.

  1. Recruiter message (required) — raw text or quoted email
  2. Intent (optional; default: decline_keep_warm)
  3. Tone (optional; default: neutral)
  4. Length (optional; default: short)
  5. User signature name (optional; default: whatever user commonly uses)

If the recruiter email contains constraints (citizenship/GC, location, onsite, comp, etc.), treat those as context signals but do not echo sensitive details unless it helps clarity.

Core Intents

Pick one. If the user doesn’t specify, infer from their instruction.

  • decline_keep_warm — not right time, door open
  • decline_not_eligible — cannot proceed due to eligibility constraints
  • ask_for_jd — request the full JD / responsibilities / comp band
  • open_to_chat — accept a quick intro call (without over-committing)
  • refer_someone — politely refer another person (only if user provided name)
  • pause_follow_up_later — ask recruiter to ping again in a timeframe
  • stop_contact — firm no / remove from list

Tone Profiles

  • crisp — minimal, direct, no fluff
  • neutral — professional, polite, standard corporate cadence
  • warm — appreciative, relationship-building, still brief

Length Profiles

  • tiny — 2–3 sentences
  • short — 4–7 sentences
  • full — 8–12 sentences (rare; use only if needed)

Safety and Professional Guardrails

Do not introduce risk. Avoid:

  • Salary/comp negotiation unless the user explicitly asks
  • Mentioning internal employer dynamics, “golden handcuffs,” or anything that could be forwarded awkwardly
  • Sharing personal details (visa history, family, health, etc.)
  • Hard promises (“I will join”, “I will interview”, “send me the offer”)
  • Snark, sarcasm, or anything that reads like a dunk

Prefer:

  • Clear, bounded language (“not exploring a move right now”)
  • Door-open phrasing (“happy to stay in touch”)
  • A single call-to-action (optional) like “reach back out later this year”

Output Requirements

Produce:

  1. Subject line (if the recruiter wrote one, preserve Re: ...)
  2. Email body (fully formatted, ready to paste)
  3. Filename + save path (outbox)
  4. 1-line rationale (for the user, not for the recruiter)

Outbox Save Rules

Write the draft to:

  • outbox/recruiters/YYYY-MM-DD__<company_or_recruiter>__<intent>.md

If company is unknown, use:

  • outbox/recruiters/YYYY-MM-DD__recruiter__<intent>.md

Content format inside the saved file:

Subject: <subject>

<body>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment