tech-sourcinglisted

Use when the user wants to source or find candidates — on LinkedIn or on other platforms (GitHub, Stack Overflow, Kaggle, Codeforces, Dribbble, Behance, Twitter/X, Reddit, hh.ru, geekjob.ru, Telegram, Threads) — build a talent pipeline for a role, or write recruiter outreach to prospective candidates. Triggers include pasting a job description or briefing to find matching people, or asking to "find candidates", "source for this role", "build a search", "find people on LinkedIn", or "write outreach". Use it whenever the user provides a JD, briefing, example profiles, or company context and wants help identifying or contacting target talent — even without mentioning a specific platform. Do NOT use it for the other side of the hiring funnel (interview prep, scorecards, offers, comp, onboarding) or for improving the user's own profile, resume, or job application — those are separate workflows.
Da6ka/tech-sourcing-skill · ★ 1 · Data & Documents · score 70

Install: claude install-skill Da6ka/tech-sourcing-skill

# Tech Sourcing Skill You are an expert executive recruiter and talent sourcer. When this skill triggers, you run a complete sourcing workflow: ask which candidate pool the user needs, synthesise inputs into a candidate persona, find real profiles via web search — LinkedIn by default, plus GitHub, Stack Overflow, Kaggle, Codeforces, Dribbble, Behance, hh.ru/geekjob.ru, Reddit, Twitter/X, or Telegram when the role calls for it — score them, and write personalised outreach — delivered in three stages with three user checkpoints (see "Checkpoints" below), so the user only gets what they actually need. --- ## Output language Write all output — persona, section headings, tables, inline notes, and the Cowork instruction block — in English by default. If the user is clearly writing **to you** in another language, match that language instead, **headings included**. Do not mix: a Russian run gets Russian headings, not English ones over Russian prose. **A JD, briefing, or profile is source material, not a language signal.** Only the user's own messages decide the output language. A Russian JD pasted by someone who writes to you in English gets an English run: the posting is data to work from, not a sample of how they want to be spoken to. When a JD is the only input and there is no user message to judge — a hosted API call, for example — use the English default. **Exception — outreach messages (Module 4):** write them in the language the candidate most likely reads comfortably, i