---
title: "Claude Code Skills for Workday Extend: What Belongs in a…"
description: "Put stable WDCLI and review rules in a skill; keep tenant-specific field names out of shared skills."
url: https://kiweely.com/blog/claude-code-skills-for-workday-extend
---

# 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
-   November 15
-   Updated November 16
-   1 min read

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.

## Read next

[All posts](https://kiweely.com/blog)

-   [November 15 ### FDE Playbook: First 30 Days on a Workday Extend and Studio Account](https://kiweely.com/blog/fde-playbook-first-30-days-workday-extend-studio)
-   [November 15 ### Claude Code vs Codex for Workday Extend: What Each Can Reach Today](https://kiweely.com/blog/claude-code-vs-codex-for-workday-extend)
-   [November 15 ### Workday Extend vs. External Pass-Through Screens: Which Architecture Fits Your Workflow?](https://kiweely.com/blog/workday-extend-vs-external-pass-through-apps-decision-guide)

### More guides on Extend apps and pages

[All 97 guides](https://kiweely.com/guides#extend)

-   [Install Ready but model components missing: refresh the Extend cache](https://kiweely.com/guides/workday-extend-refresh-model-components-cache)
-   [When must I promote Extend model components before the Friday update?](https://kiweely.com/guides/workday-extend-model-component-promotion-deadlines)
-   [When should you not add Workday Extend model components?](https://kiweely.com/guides/when-not-to-add-workday-extend-model-components)
-   [Workday Extend Model Components and the Weekly Update](https://kiweely.com/guides/workday-extend-model-components-weekly-update)
-   [The Validate and Deploy Proof Ladder for Workday Extend](https://kiweely.com/guides/workday-extend-validate-deploy-proof-ladder)
-   [Promote a Workday Extend App Past Development](https://kiweely.com/guides/workday-extend-promote-past-development-beginners)
-   [Use the Workday Extend App Catalog as an AI Jump Start](https://kiweely.com/guides/workday-extend-app-catalog-ai-jump-start)
-   [AMD vs PMD in Workday Extend, for Beginners](https://kiweely.com/guides/workday-extend-amd-vs-pmd-beginners)

## 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.

[Start for free](https://kiweely.com/download) [See how it works](https://kiweely.com/vine/how-it-works)

## 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.
