Skip to content
KiweelyKiweelyKiweely

Claude Code Skills for Workday Extend: What Belongs in a Skill vs a Prompt

Skills should encode durable Extend workflow rules. Tenant field inventories and client secrets stay in the project, not in a shared skill others will reuse.

  • By Kiweely
  • Updated
  • 1 min read
On this page

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.

Your Workday work, done by AI.

Kiweely Vine is the AI agent that builds, deploys and tests Extend apps as real people, makes changes in any Workday task screen, answers from your real tenant and builds reports.

Get the next one in your inbox.

One email a month for Workday teams: what’s changing in Workday and what to retest, one tip tried in a real tenant, and what’s new at Kiweely.

We’ll email you once to confirm. Unsubscribe in one click from any issue.