Inputs
Provide these when prompted. The skill asks for anything missing before it runs.
Required
- A job description
Optional
- Must-have vs nice-to-have skills
- Locations or work authorization
- Target companies
Agent Skill
Recruiting Sourcing Planner
Convert a job description into a structured candidate-sourcing workflow.
Version 1.0 Updated June 2026 SKILL.md MIT 6 min read
Overview
What this skill does
A vague job description leads to scattered sourcing and inconsistent screening, with great candidates missed and weak ones advanced.
This skill turns the role into a sourcing workflow: clear candidate criteria, target profile types, search terms, where to source, screening fields, exclusion criteria, and a review process — all based on professional criteria, never sensitive attributes.
When to use it
Best used for
- Kicking off a new requisition
- Turning a role into Boolean search terms
- Choosing where to source candidates
- Standardizing first-pass screening
Know the limits
When not to use this skill
- You have no job description or criteria
- You want to filter on protected characteristics (never do this)
- You need the sourcing executed now
Outputs
A sourcing workflow with a consistent, inspectable schema.
candidate_criteriaThe professional bar for the role.
target_profile_typesBackgrounds likely to fit.
search_termsBoolean/keyword terms to source.
source_recommendationsWhere to find candidates.
screening_fieldsWhat to capture per candidate.
exclusion_criteriaProfessional disqualifiers.
review_processHow to screen consistently.
Example
Example
A plan for a backend role.
Input
Role: Senior Backend Engineer (Go, distributed systems), remote EU.Output
candidate_criteria: 5+ yrs backend; Go; distributed systems; EU remote
target_profile_types: Platform/infra engineers at SaaS firms
search_terms: "Go" AND ("distributed systems" OR microservices) AND EU
source_recommendations: Team pages; engineering communities; profile search
screening_fields: Years, Go evidence, systems scope, location
exclusion_criteria: No backend evidence; outside EU
review_process: Screen against required criteria; flag gapsThe role becomes an executable sourcing plan with professional criteria and Boolean terms, and no reliance on sensitive attributes.
Setup
How to use the skill
General steps first, then notes for specific clients where verified.
- 1Download the file using the button below, or copy the Markdown.
- 2Place it in a directory named after the skill (e.g. skill-name/).
- 3Make sure the filename stays exactly SKILL.md.
- 4Add any references or assets included with the package.
- 5Load the skill into a compatible agent and provide the required inputs.
Claude Code
- 1Create a folder for the skill and save SKILL.md inside it.
- 2Place the folder where your project's skills are discovered.
- 3Reference the skill when you want it applied to your data.
Other compatible clients
- 1Confirm the client supports the open Agent Skills format.
- 2Load the SKILL.md file as instructed by that client.
- 3If skills are not auto-loaded, paste the Markdown as instructions.
Source
Full SKILL.md source
Read the rendered skill or copy the complete Markdown. The download is generated from this exact source.
Version 1.0 SKILL.md ~2 KB MIT
Recruiting Sourcing Planner
Purpose
Convert a job description into a structured candidate-sourcing workflow.
When to use this skill
- Kicking off a new requisition
- Turning a role into Boolean search terms
- Choosing where to source candidates
- Standardizing first-pass screening
When not to use this skill
- You have no job description or criteria
- You want to filter on protected characteristics (never do this)
- You need the sourcing executed now
Required inputs
- A job description
Optional inputs
- Must-have vs nice-to-have skills
- Locations or work authorization
- Target companies
Rules
- Base criteria and terms on professional requirements only.
- Do not infer health, religion, ethnicity, sexual orientation, political affiliation, or other sensitive personal attributes.
- Make exclusion criteria professional and explicit.
- Recommend accessible, public sources.
- Keep screening consistent across candidates.
Process
- Parse the job description.
- Define candidate criteria and profile types.
- Draft search terms.
- Recommend sources and screening fields.
- Define exclusions and a review process.
Output format
Return a sourcing workflow with the following fields:
- candidate_criteria
- targetprofiletypes
- search_terms
- source_recommendations
- screening_fields
- exclusion_criteria
- review_process
Validation
- Confirm criteria are professional, not personal.
- Confirm search terms reflect requirements.
- Confirm the review process is consistent.
Limitations
- Sourcing plans depend on candidate availability.
- Search terms may need iteration per platform.
Before you rely on it
Safety and limitations
- Sourcing plans depend on candidate availability.
- Search terms may need iteration per platform.
- Review the output before acting on it.
- Do not upload confidential datasets to an external model without authorization.
- Outputs depend on the model and the source data and are not guaranteed to be accurate.
History
Changelog
- v1.0June 2026
- Initial release.
Questions
Agent Skill FAQ
What does it need to build the plan?
A job description. It turns the role’s must-haves into search terms, sources to check, and screening steps — the plan, not the candidates themselves.
Does it source candidates automatically?
No. It produces the plan and search terms; use ProfileSpider to extract candidate profiles from the sources it recommends.
Do I need ProfileSpider to use this skill?
No. The skill works on any compatible data. ProfileSpider is one convenient way to produce that structured input.
Does running this skill send data to ProfileSpider?
No. Downloading or copying the file does not send any data to ProfileSpider. What happens afterward depends on the AI service you load it into.
Are Agent Skills the same as prompts?
No. A skill is a structured, reusable package — task, inputs, rules, process, and output format — so the workflow runs consistently and can be shared, versioned, and edited.