Agent Skillsmohitagw15856/pm-claude-skills › sourcing-strategy

sourcing-strategy

GitHub

为难以填补的职位构建人才寻访策略,包括理想候选人画像、聚集地分析、渠道优先级排序、外展方式及漏斗数学模型。通过明确的每周计划和量化目标,确保主动且高效的招聘执行,而非被动等待投递。

plugins/pm-recruiting/skills/sourcing-strategy/SKILL.md mohitagw15856/pm-claude-skills

Trigger Scenarios

创建寻访策略 制定候选人寻访计划 确定招聘渠道方案 寻找特定角色候选人

Install

npx skills add mohitagw15856/pm-claude-skills --skill sourcing-strategy -g -y
More Options

Non-standard path

npx skills add https://github.com/mohitagw15856/pm-claude-skills/tree/main/plugins/pm-recruiting/skills/sourcing-strategy -g -y

Use without installing

npx skills use mohitagw15856/pm-claude-skills@sourcing-strategy

指定 Agent (Claude Code)

npx skills add mohitagw15856/pm-claude-skills --skill sourcing-strategy -a claude-code -g -y

安装 repo 全部 skill

npx skills add mohitagw15856/pm-claude-skills --all -g -y

预览 repo 内 skill

npx skills add mohitagw15856/pm-claude-skills --list

SKILL.md

Frontmatter
{
    "name": "sourcing-strategy",
    "description": "Build a talent sourcing strategy for a hard-to-fill role. Use when asked to create a sourcing strategy, a candidate sourcing plan, a channel plan for hiring, or to figure out where to find candidates for a role. Produces a strategy — the ideal-candidate profile and where they are, prioritised sourcing channels, outreach approach, a pipeline target with funnel math, and a weekly plan — so sourcing is deliberate, not just posting and praying."
}

Sourcing Strategy Skill

Hard roles aren't filled by posting a job and waiting — they're filled by knowing who you need, where they are, and how to reach enough of them to fill the funnel. This skill builds that plan: the target profile, the channels ranked by where the talent actually concentrates, and the pipeline math so you know how many to source to make one hire.

Working from a brief

Given "we can't fill our staff ML engineer role", build the strategy anyway — infer the candidate profile, where they cluster, and a realistic funnel, labelling assumptions. Use funnel ratios with a worked example rather than inventing exact numbers. Never withhold for missing detail.

Required Inputs

Ask for these only if they aren't already provided (else infer and label):

  • The role — what it is, the must-have skills, level, and what's hard about filling it.
  • Constraints — location/remote, comp band, timeline, and any visa/relocation limits.
  • Selling points — why a strong candidate would want it (and any known weaknesses to counter).
  • What's been tried — current pipeline, channels used, and where it's stalling.

Output Format

Sourcing Strategy: [role]

1. Ideal candidate profile — the realistic must-haves vs. nice-to-haves, the adjacent profiles worth considering (to widen the pool), and the signals that identify a strong fit.

2. Where they are — where this talent concentrates: companies to source from (and avoid), communities, platforms, events, and content they engage with.

3. Channel plan — sourcing channels ranked by likely yield for this role:

Channel Why it fits Effort Approach
Direct sourcing (LinkedIn/GitHub) high boolean + personalized outreach
Referrals low targeted ask to the team
Communities / events med
Job posts / inbound low only part of the mix

4. Outreach approach — the message angle and cadence (pairs with recruiter-outreach and boolean-search-builder).

5. Pipeline target & funnel — how many to source to make the hire: a funnel with ratios + a worked example (e.g. sourced → replied → screened → onsite → offer → hire), so weekly activity is sized to the goal.

6. Weekly plan — the concrete cadence (X sourced, Y outreach, Z screens per week) and how you'll track it.

Quality Checks

  • Starts from a clear candidate profile, including adjacent profiles to widen the pool
  • Names specific places the talent actually concentrates — not just "LinkedIn"
  • Channels are prioritised by likely yield for this role, with effort noted
  • Pipeline is sized with funnel ratios + a worked example, not invented totals
  • There's a concrete weekly activity plan tied to the hire target
  • Selling points and objections are addressed; criteria stay job-related

Anti-Patterns

  • Do not rely on a job post and inbound for a hard role — lead with proactive sourcing
  • Do not define the profile so narrowly that no one qualifies — include adjacent talent
  • Do not invent exact funnel numbers — use ratios and a worked example
  • Do not list channels without prioritisation — say where to spend effort first
  • Do not skip the weekly cadence — strategy without activity targets doesn't fill the role

Based On

Talent-sourcing strategy practice — profile-first sourcing, channel prioritisation by talent concentration, funnel/pipeline math, and a measurable weekly cadence.

Version History

  • a38bc30 Current 2026-07-05 11:26

Same Skill Collection

exports/openclaw/360-feedback-template/SKILL.md
exports/openclaw/401k-plan-decoder/SKILL.md
exports/openclaw/ab-test-planner/SKILL.md
exports/openclaw/ab-test-readout/SKILL.md
exports/openclaw/accessibility-audit/SKILL.md
exports/openclaw/account-plan/SKILL.md
exports/openclaw/acquirer-red-team/SKILL.md
exports/openclaw/ad-copy/SKILL.md
exports/openclaw/aeo-optimizer/SKILL.md
exports/openclaw/agenda-or-cancel/SKILL.md
exports/openclaw/agent-design-review/SKILL.md
exports/openclaw/agent-observability-spec/SKILL.md
exports/openclaw/agent-spec/SKILL.md
exports/openclaw/ai-ethics-review/SKILL.md
exports/openclaw/ai-eval-plan/SKILL.md
exports/openclaw/ai-feature-prd/SKILL.md
exports/openclaw/ai-product-canvas/SKILL.md
exports/openclaw/air-quality/SKILL.md
exports/openclaw/altitude-shifter/SKILL.md
exports/openclaw/ambiguity-resolver/SKILL.md
exports/openclaw/analyst-relations-brief/SKILL.md
exports/openclaw/announcement-card/SKILL.md
exports/openclaw/api-docs-writer/SKILL.md
exports/openclaw/api-test-plan/SKILL.md
exports/openclaw/api-versioning-strategy/SKILL.md
exports/openclaw/apology-letter/SKILL.md
exports/openclaw/architecture-decision-record/SKILL.md
exports/openclaw/architecture-diagram/SKILL.md
exports/openclaw/archive-strategy/SKILL.md
exports/openclaw/assumption-bounty/SKILL.md
exports/openclaw/assumption-mapper/SKILL.md
exports/openclaw/async-update-format/SKILL.md
exports/openclaw/auto-repair-estimate-decoder/SKILL.md
exports/openclaw/autopilot-charter/SKILL.md
exports/openclaw/benefits-decoder/SKILL.md
exports/openclaw/bid-tender-review/SKILL.md
exports/openclaw/board-deck-narrative/SKILL.md
exports/openclaw/board-minutes/SKILL.md
exports/openclaw/board-pre-read/SKILL.md
exports/openclaw/bom-cost-review/SKILL.md
exports/openclaw/bookkeeping-categorization/SKILL.md
exports/openclaw/boolean-search-builder/SKILL.md
exports/openclaw/brag-doc/SKILL.md
exports/openclaw/brainstorming/SKILL.md
exports/openclaw/brief-builder/SKILL.md
exports/openclaw/briefing-note/SKILL.md
exports/openclaw/budget-builder/SKILL.md
exports/openclaw/budget-variance-analysis/SKILL.md
exports/openclaw/bug-diagnosis/SKILL.md
exports/openclaw/bug-report/SKILL.md

Metadata

Files
0
Version
471c606
Hash
2420b0c0
Indexed
2026-07-05 11:26

- 위키
Copyright © 2011-2026 iteam. Current version is 2.155.2. UTC+08:00, 2026-07-30 23:11
浙ICP备14020137号-1 $방문자$