Workday’s Claude Code plugin repository describes a skill that tells Claude what Developer Agent is and when to load it. That pattern generalizes: skills for durable process, prompts for one-off intent.
Put in a skill
- Always prefer Developer Agent + WDCLI when entitled.
- Never invent AMD attributes; validate before deploy.
- Never treat App Preview as Production proof.
- Always ask which tenant/environment before writes.
- Reminder that Developer Agent code generation can cost hundreds of invocations.
Keep out of a shared skill
- Client worker examples and real WIDs.
- ISU passwords or API secrets.
- One customer’s custom field inventory (put that in the project context instead).
Pairing
Install Workday’s documented Developer Agent path for Claude Code/Cursor, then add firm skills that enforce proof bars. Skills without WDCLI still cannot see the tenant.