Workday Bundle

Enterprise recruiting operations on Workday — with Claude for judgment, and your tenant for truth. This bundle helps teams work from exports, RaaS, and guarded API paths so you can search and report on recruiting data, score applicants against briefs, draft requisitions from intake notes, and produce compliance-oriented workbooks—without pretending every Workday tenant exposes the same REST or SOAP surface.

Why this bundle exists

Workday Recruiting sits inside a full HCM platform. Field names, pipeline stages, integrations, and permissions differ by customer. Generic “connectors” fail in production because they guess endpoints and ignore business processes. This bundle is deliberately conservative: it prioritizes file and RaaS paths, ships dry-run defaults for writes, and keeps SOAP/REST write paths off until your Workday team confirms the exact operations your tenant allows.

How you benefit

• Same scoring rubric across exports — score candidates from an XLSX export with explicit evidence notes.
• Pipeline packs for leadership — export multi-tab workbooks for requisition aging and stage conversion from report data.
• Safer change management — stage updates and requisition payloads are previewed before anyone touches production.

Example prompts

When Claude has access to your Workday data through this bundle (with your keys and approved exports), you can ask in plain language—for example:

• Take this Workday candidate export and find senior Java engineers in Germany; explain which filters were client-side.
• Score everyone in this export against this requisition brief and keep write-back in dry-run.
• Analyze this recruiting report for bottlenecks and recruiter workload; put the metrics and narrative in one Excel file.

Full power (easy to miss)

• Start with validate-connection and file_only using --input report paths.
• Maintain _context/workday_mapping.yml so stage and ID columns match your tenant’s reports.
• Never disable dry-run for writes until a Workday administrator confirms business process impact.

What you get

Digital download: a ZIP produced by package-bundle.sh containing skills, _lib, _context templates, and documentation.

Included skills

Skill	What it does
validate-connection	Validate environment variables and light read probes
search-candidates	Search/filter candidates from reports or RaaS
score-candidates	AI score + optional dry-run feedback text
write-feedback	Structure interview notes; optional dry-run write-back
export-requisition-pipeline	Multi-tab pipeline export from a combined report
create-job-requisition	Intake notes → draft payload (dry-run default)
update-application-stage	Plan spreadsheet-driven stage updates (dry-run default)
sync-candidate-attachments	Manifest workflow for attachment sync (tenant-gated)
analyze-recruiting-report	Metrics + Claude narrative
generate-compliance-report	Operational audit workbook (not legal advice)
export-workday-data	Re-export to CSV/JSON/Excel or ATS-shaped CSV

How it works

1. Unzip the bundle into your Claude Code project.
2. Configure .env at the project root with the variables for your chosen auth mode.
3. Map tenant columns in _context/workday_mapping.yml.
4. Run read-only skills first; keep writes in dry-run until your Workday admin approves.

Requirements

• WORKDAY_TENANT, WORKDAY_BASE_URL, WORKDAY_AUTH_MODE for API-oriented workflows (optional for pure file flows).
• ANTHROPIC_API_KEY for Claude-powered skills.
• Additional variables per mode — see ats/workday/.env.example.

Compatibility

Works with macOS and Windows (run.sh / run.ps1). Designed for Claude Code and similar assistants.

Support & updates

Technical reference: CLAUDE.md and per-skill README files. Release history is mirrored below from CHANGELOG.md.

Workday Bundle Changelog

1.0.0 (2026-05-15)

Initial release: Workday Recruiting bundle with ten skills plus validate-connection, shared _lib adapters for SOAP, REST, RaaS, and file modes, _context/workday_mapping.yml template, and conservative dry-run defaults for writes.