Token导航 LogoToken导航

Agent Skill · 研究检索

developer-recruiting-strategy(开发者招募策略)

developer-recruiting-strategy 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

developer-recruiting-strategy 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为需要联网;许可证为 MIT,暂无第三方扫描结果,按安装量在研究检索类的 73,675 个 Skill 里排第 65,745。

总安装 275周安装 11GitHub Stars 公开资料未说明下载 89核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
MIT

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:developer-recruiting-strategy(开发者招募策略)
来源仓库:https://github.com/clous-ai/agents
仓库路径:skills/developer-recruiting-strategy
安装命令:
npx skills add clous-ai/agents --skill "developer-recruiting-strategy"
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

AgentSkills.tonpx skills
npx skills add clous-ai/agents --skill "developer-recruiting-strategy"

这个 Skill 是做什么的

研究检索类 Skill 主要解决「找资料、核对事实、把来源整理清楚」的问题,通常会让助手先检索再总结。

用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

通过 npx skills add clous-ai/agents --skill "developer-recruiting-strategy" 安装。适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

来源仓库内路径:skills/developer-recruiting-strategy

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add clous-ai/agents --skill "developer-recruiting-strategy";命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它需要需要联网,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

developer-recruiting-strategy 怎么安装?

在终端执行 npx skills add clous-ai/agents --skill "developer-recruiting-strategy"。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

developer-recruiting-strategy 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

developer-recruiting-strategy 需要什么权限?

权限级别是需要联网。该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

developer-recruiting-strategy 是免费的吗?

来源标注的许可证是 MIT。本站不代收任何费用,也不托管安装包;能否商用、要不要署名,以许可证原文为准。

developer-recruiting-strategy 用的人多吗?

公开数据是累计安装 275 次,近一周安装 11 次,下载 89 次。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

developer-recruiting-strategy 安全吗?

没有查到第三方扫描结果,安全性无法从公开资料判断,安装前请自行审查源码、依赖和命令行为。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 许可证明确为 MIT,商用和分发边界好判断。

先想清楚的地方

  • 没有第三方扫描结果,安全性只能靠自己读源码判断。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理研究检索类任务、又不想每次都手写提示词的人。

不太适合

  • 要求有安全扫描结论才肯安装的团队。
  • 需要厂商级技术支持和 SLA 的生产系统。

研究检索类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
find-skills

寻找技能 · Codex、Claude

31,199,81316,486操作浏览器MIT有提醒
self-improving-agent

自我改进 Agent · OpenClaw

16,464,0023,396接触敏感数据MIT-0通过
soultrace

灵魂追踪 · Codex、Claude

7,588,94412需要联网未明确有提醒
self-improving

自我完善 · OpenClaw

6,829,2841,046需要联网MIT-0通过
microsoft-foundry

微软代工厂 · Codex、Claude

6,614,144764调用外部服务未明确有提醒
developer-recruiting-strategy

开发者招募策略 · 本页

275—需要联网MIT未收录

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

name
developer-recruiting-strategy
description
This skill should be used when the user asks to "create a recruiting strategy", "plan sourcing channels", "define role scorecard", "build hiring plan", "identify must-haves vs nice-to-haves", or "create talent acquisition plan". Transforms hiring intake into actionable recruiting strategy with sourcing channels, scorecard, and execution plan.
version
0.1.0
license
MIT

Developer Recruiting Strategy

Convert hiring intake documents into comprehensive recruiting strategies that maximize candidate quality while minimizing time-to-hire.

Purpose

This skill creates data-driven recruiting strategies for engineering roles. A strong strategy defines clear must-haves (non-negotiable) vs nice-to-haves (differentiators), identifies optimal sourcing channels, and establishes a realistic execution plan.

When to Use

Invoke this skill when:

  • Hiring intake is approved and ready for execution
  • Need to define role scorecard for recruiters and hiring managers
  • Planning multi-channel sourcing approach
  • Establishing pass/fail criteria for candidates
  • Creating recruiting team briefing document

Core Process

1. Build Role Scorecard

Transform intake requirements into prioritized scorecard:

Must-Have Criteria (Pass/Fail):

  • Extract from intake "must_have" requirements
  • Make each criterion measurable and observable
  • Define minimum acceptable evidence for each
  • Ensure criteria are job-related (legal compliance)

Nice-to-Have Criteria (Differentiators):

  • Extract from intake "nice_to_have" requirements
  • Assign point values or tier ranking
  • Use for candidate comparison, not screening

Scoring Framework:

Must-Haves: Binary (Yes/No) - candidate must pass ALL
Nice-to-Haves: Weighted (0-5 points each)
  - 5: Exceptional strength
  - 3-4: Clear evidence
  - 1-2: Some evidence
  - 0: No evidence

Example Scorecard:

CriterionTypeEvidence RequiredPoints
5+ years backend experienceMust-haveResume + referencesPass/Fail
Python production expertiseMust-haveCode review or take-homePass/Fail
Distributed systemsMust-haveSystem design interviewPass/Fail
Kubernetes experienceNice-to-haveResume + discussion0-5
Open source contributionsNice-to-haveGitHub profile0-5

2. Define Sourcing Channels

Identify optimal channels based on role, urgency, and budget:

Active Sourcing (Proactive Outreach):

  • LinkedIn Recruiter (best for senior+ engineers)
  • GitHub (for open source contributors, technical roles)
  • Stack Overflow Jobs/Talent (technical credibility signal)
  • Conferences and meetups (niche specializations)
  • Employee referrals (highest conversion, cultural fit)

Passive Sourcing (Job Postings):

  • Company careers page (employer brand showcase)
  • LinkedIn Jobs (broad reach, professional network)
  • AngelList/Wellfound (startup ecosystem)
  • Hacker News Who's Hiring (engineering-focused audience)
  • Specialized job boards (e.g., RemoteOK for remote roles)

Channel Selection Matrix:

Role LevelUrgencyRecommended ChannelsExpected Conversion
Junior-MidMediumJob postings, referrals, LinkedIn15-20% screen → offer
SeniorHighActive sourcing, referrals, GitHub10-15% screen → offer
Staff+CriticalExecutive recruiting, warm intros5-10% screen → offer

Budget Considerations:

  • Employee referral bonus: $1,000-$5,000 (highest ROI)
  • LinkedIn Recruiter: $8,000-$12,000/year
  • External recruiter: 20-30% of first-year salary
  • Job board postings: $200-$1,000 per posting

3. Craft Compelling Role Pitch

Create messaging that attracts target candidates:

Value Proposition Elements:

  • Technical Challenge: What interesting problems will they solve?
  • Impact: How does their work affect customers/business?
  • Growth: Career development opportunities
  • Team: Who will they work with? (highlight strong team members)
  • Tech Stack: Modern, exciting technologies
  • Culture: Remote flexibility, work-life balance, learning culture
  • Compensation: Competitive range (required in many states)

Messaging Framework:

## The Opportunity

[Company] is solving [important problem] for [customer type].
As [Role Title], you'll [key responsibility] to [business outcome].

## What You'll Do

- [Impactful project 1]
- [Technical challenge 2]
- [Leadership opportunity 3]

## What You'll Bring

- [Must-have 1]
- [Must-have 2]
- [Must-have 3]

Nice to have: [Differentiators]

## Why Join Us

- Work on [interesting technical challenge]
- [Growth opportunity]
- [Company momentum/traction]
- Compensation: [Range] + equity

[Apply link]

Avoid Common Mistakes:

  • "Rockstar/Ninja/Guru" titles (unprofessional)
  • Laundry list of 20+ requirements
  • Vague responsibilities ("build cool stuff")
  • No compensation information (illegal in many states)

4. Plan Execution Timeline

Create realistic timeline with milestones:

Typical Engineering Hiring Timeline:

StageDurationCumulativeActivities
Sourcing1-2 weeksWeek 2Post jobs, active outreach, referrals
Phone screens1-2 weeksWeek 4Initial qualification calls
Technical screens1-2 weeksWeek 6Coding challenges, tech conversations
Onsite/Virtual onsites1-2 weeksWeek 8Full interview loops
Offer & negotiation0.5-1 weekWeek 9Extend offer, negotiate, close
Total6-9 weeksScreen to signed offer

Accelerated Timeline (Critical Roles):

  • Collapse sourcing + screening: Week 1-2
  • Fast-track promising candidates
  • Reduce to 4-6 weeks total
  • Risk: May sacrifice candidate quality

Extended Timeline (Pipeline Building):

  • Ongoing sourcing (no urgency)
  • More thorough evaluation
  • 10-12 weeks acceptable
  • Benefit: Higher quality bar

Capacity Planning:

Required: [X] interview slots/week
Available: [Y] interviewers × [Z] hours/week
Bottleneck: [Identify constraint]
Mitigation: [Add interviewers or reduce loop]

5. Define Success Metrics

Establish measurable goals for recruiting process:

Funnel Metrics:

  • Sourced candidates → Applications: X candidates
  • Applications → Phone screen: Y% pass rate
  • Phone screen → Technical: Y% pass rate
  • Technical → Onsite: Y% pass rate
  • Onsite → Offer: Y% pass rate
  • Offer → Accept: Y% acceptance rate

Quality Metrics:

  • Average interview scorecard rating: ≥ 3.5/5
  • Must-have pass rate: 100%
  • Diversity of candidate pipeline: X% underrepresented groups
  • Referral rate: X% of hires from referrals

Time Metrics:

  • Time to first interview: ≤ 1 week
  • Time to offer: ≤ 6-8 weeks
  • Offer acceptance time: ≤ 1 week

Cost Metrics:

  • Cost per hire: $X,000
  • Recruiter hours per hire: X hours
  • ROI by channel: $ spent / hire made

6. Generate Strategy Document

Produce comprehensive recruiting strategy:

Output Structure:

{
  "role_summary": {
    "title": "string",
    "level": "string",
    "team": "string",
    "target_start_date": "YYYY-MM-DD"
  },
  "scorecard": {
    "must_haves": [
      {
        "criterion": "string",
        "evidence_required": "string",
        "assessment_stage": "resume|screen|technical|onsite"
      }
    ],
    "nice_to_haves": [
      {
        "criterion": "string",
        "points": 5,
        "assessment_stage": "string"
      }
    ]
  },
  "sourcing_strategy": {
    "primary_channels": ["array"],
    "secondary_channels": ["array"],
    "estimated_outreach": {
      "linkedin_messages": 100,
      "referral_asks": 20,
      "job_posting_reach": 5000
    },
    "budget": {
      "total": "$X,000",
      "breakdown": {}
    }
  },
  "value_proposition": {
    "technical_challenge": "string",
    "impact": "string",
    "growth_opportunity": "string",
    "team_strength": "string"
  },
  "timeline": {
    "milestones": [
      {
        "stage": "string",
        "target_date": "YYYY-MM-DD",
        "deliverable": "string"
      }
    ],
    "estimated_weeks_to_hire": 8
  },
  "success_metrics": {
    "target_applications": 50,
    "target_phone_screens": 20,
    "target_onsites": 8,
    "target_offers": 2,
    "acceptance_rate_target": "50%"
  }
}

Save to strategy-{role}-{date}.json.

7. Brief Recruiting Team

Create recruiter briefing document:

Briefing Contents:

  • Role overview (from intake)
  • Scorecard (must-haves, nice-to-haves)
  • Ideal candidate profile
  • Sourcing channels and messaging
  • Disqualification criteria (red flags)
  • Selling points (why join)
  • Interview process overview
  • Timeline and urgency

Use template at templates/recruiter-brief.md.

Using Supporting Resources

Templates

  • templates/scorecard-template.json - Role scorecard schema
  • templates/sourcing-plan.md - Channel strategy template
  • templates/recruiter-brief.md - Recruiter onboarding doc

References

  • references/sourcing-channels.md - Detailed channel comparison, conversion rates
  • references/messaging-best-practices.md - Job description writing, outreach templates
  • references/diversity-sourcing.md - Strategies for diverse candidate pipelines

Scripts

  • scripts/validate-scorecard.py - Check scorecard completeness
  • scripts/estimate-funnel.py - Model hiring funnel metrics
  • scripts/channel-roi.py - Calculate ROI by sourcing channel

Example Workflow

User: "Create recruiting strategy for the senior backend role we just defined"

Steps:

  1. Load hiring intake JSON
  2. Extract must-haves → Build scorecard criteria
  3. Assess role level + urgency → Select sourcing channels
  4. Draft value proposition highlighting technical challenges
  5. Plan 8-week timeline with capacity constraints
  6. Define success metrics (50 applies → 2 offers)
  7. Generate strategy JSON + recruiter brief
  8. Validate with scorecard script

Output: Complete recruiting strategy ready for execution

Next Steps

After strategy is complete:

  1. Use developer-interview-loop-design to build interview process
  2. Share strategy with recruiting team
  3. Launch sourcing campaigns
  4. Track metrics weekly
  5. Adjust strategy based on early funnel performance

Progressive Disclosure: Detailed sourcing channel data, messaging templates, and diversity recruiting strategies are in references/. Core strategy framework above handles standard use cases.

平台分布

Codex

29.04%
按下载量换算26

Claude Code

21.18%
按下载量换算19

Gemini CLI

18.46%
按下载量换算16

windsurf

12.25%
按下载量换算11

OpenCode

6.9%
按下载量换算6

Cursor

2.99%
按下载量换算3

安全审计

暂无安全审计结果可展示。

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills