recruiting-pipeline
- Repo stars 19,014
- Author updated Live
- Author repo knowledge-work-plugins
- Domain
- Other
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 88 / 100 · community maintained
- Author / version / license
- @anthropics · no license declared
- Token usage
- Lean
- Setup complexity
- Plug-and-play
- External API key
- Not required
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- No special requirements
- Permissions
-
- Read-only
- Write / modify
- Network behavior
- Local-only
- Install commands
- 26 variants
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools，默认拥有全部工具权限。
---
name: recruiting-pipeline
description: Track and manage recruiting pipeline stages. Trigger with "recruiting update", "candidate pipeli…
category: other
runtime: no special runtime
---
# recruiting-pipeline output preview
## PART A: Task fit
- Use case: Track and manage recruiting pipeline stages. Trigger with "recruiting update", "candidate pipeline", "how many candidates", "hiring status", or when the user discusses sourcing, screening, interviewing, or extending offers..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “Pipeline Stages / Metrics to Track / If ATS Connected” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “Track and manage recruiting pipeline stages. Trigger with "recruiting update", "candidate pipeline", "how many candidates", "hiring status", or when the user discusses sourcing, screening, interviewing, or extending offers.”.
- **02** When the source has headings, the agent prioritizes “Pipeline Stages / Metrics to Track / If ATS Connected” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files; mostly runs locally; usually needs no extra API key.
## Running Rules
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options. Choose the trigger
The source does not require a stable slash command. After installation, invoke the skill by name and describe the task.
Provide inputs and boundaries
Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, write/modify files.
Validate with a small run
Start with a small task and check whether the result follows “Pipeline Stages / Metrics to Track / If ATS Connected”. Inspect diffs, logs, previews, or tests before expanding scope.
Review before delivery
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: recruiting-pipeline
description: Track and manage recruiting pipeline stages. Trigger with "recruiting update", "candidate pipeli…
category: other
source: anthropics/knowledge-work-plugins
---
# recruiting-pipeline
## When to use
- Track and manage recruiting pipeline stages. Trigger with "recruiting update", "candidate pipeline", "how many candida…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.
## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.
## Execution rules
- Organize steps around “Pipeline Stages / Metrics to Track / If ATS Connected” and keep inference separate from source facts.
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding the task.
## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies. Evidence boundary and execution chain
The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "recruiting-pipeline" {
input -> user goal + target files + boundaries + acceptance criteria
context -> Pipeline Stages / Metrics to Track / If ATS Connected
rules -> SKILL.md triggers / order / output contract
runtime -> no special runtime | read files, write/modify files | mostly runs locally
guardrails -> usually needs no extra API key + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
}Recruiting Pipeline
Help manage the recruiting pipeline from sourcing through offer acceptance.
Pipeline Stages
| Stage | Description | Key Actions |
|---|---|---|
| Sourced | Identified and reached out | Personalized outreach |
| Screen | Phone/video screen | Evaluate basic fit |
| Interview | On-site or panel interviews | Structured evaluation |
| Debrief | Team decision | Calibrate feedback |
| Offer | Extending offer | Comp package, negotiation |
| Accepted | Offer accepted | Transition to onboarding |
Metrics to Track
- Pipeline velocity: Days per stage
- Conversion rates: Stage-to-stage drop-off
- Source effectiveness: Which channels produce hires
- Offer acceptance rate: Offers extended vs. accepted
- Time to fill: Days from req open to offer accepted
If ATS Connected
Pull candidate data automatically, update statuses, and track pipeline metrics in real time.
Decide Fit First
Design Intent
How To Use It
Boundaries And Review