BuilderIO/pipeline-workflow
templates/recruiting/.agents/skills/pipeline-workflow/SKILL.md
Pipeline stages and candidate progression in Greenhouse. Use when advancing, moving, or rejecting candidates. Critical: applicationId (not candidateId) is used for all pipeline moves.
$ install --global
skillsauthnpx skillsauth add BuilderIO/agent-native pipeline-workflowInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 16, 2026, 7:47 PM20.5s1 file scanned
SKILL.md
- name:
- pipeline-workflow
- description:
- >-
- moving, or rejecting candidates. Critical:
- applicationId (not candidateId)
Pipeline Workflow
Critical Concept: applicationId vs candidateId
All pipeline moves use applicationId, NOT candidateId. A candidate can have multiple applications (one per job). Each application tracks its own stage progression.
To find the applicationId:
get-candidate --id <candidateId>— returnsapplicationsarray- Each application has:
id(applicationId),current_stage,jobs,status
Viewing the Pipeline
pnpm action get-pipeline --jobId 123 [--compact]
Returns candidates grouped by stage for a specific job. Each stage shows its applications with candidate names.
Advancing a Candidate
pnpm action advance-candidate --applicationId 789 --fromStageId 100
Advances the application to the next stage in the pipeline. Requires the current fromStageId to prevent race conditions.
Moving to a Specific Stage
pnpm action move-candidate --applicationId 789 --fromStageId 100 --toStageId 200
Moves the application to a specific stage (can skip stages or move backward).
Rejecting a Candidate
pnpm action reject-candidate --applicationId 789 [--notes "Not a fit for this role"]
Finding Stage IDs
get-pipeline --jobId <id>— shows all stages with IDsget-candidate --id <candidateId>— showscurrent_stagefor each application
Common Workflow
1. User asks "advance Sarah to the next stage"
2. view-screen → get current context
3. get-candidate → find applicationId and current fromStageId
4. advance-candidate --applicationId=X --fromStageId=Y
5. refresh-data
After Mutations
Always run pnpm action refresh-data after advancing, moving, or rejecting candidates.
Related Skills
- candidate-management — Finding candidates and their applicationIds
- interview-scheduling — Scheduling interviews at specific stages
Related Skills
BuilderIO/booker
tools
VerifiedTrustedCommunity
Public booking flow — the state machine, animations, and URL/app-state sync.
108SKILL.mdUpdated Apr 19, 2026
BuilderIO/workflows
tools
VerifiedTrustedCommunity
Trigger-based automations — reminders, follow-ups, webhooks — across the booking lifecycle.
46SKILL.mdUpdated Apr 19, 2026
BuilderIO/team-scheduling
tools
VerifiedTrustedCommunity
Team event types, round-robin assignment, collective bookings, host weights, and no-show calibration.
46SKILL.mdUpdated Apr 19, 2026
BuilderIO/slot-engine
development
VerifiedTrustedCommunity
The pure `computeAvailableSlots` function — inputs, outputs, invariants, and debugging guide.
46SKILL.mdUpdated Apr 19, 2026