Skip to content
KiweelyKiweelyKiweely

Why Custom Agent Skills Deployed From the Developer Site Don’t Appear in Agent Management Hub, and ASOR Tenant Prerequisites

When you deploy a Custom Agent with multiple .agentskill files from App Builder, Workday’s Agent System of Record packages all of their tools into a single combined skill registration that starts disabled. Learn how to enable and sync skills in Agent Management Hub and verify ASOR prerequisites.

  • Checked against Workday on
  • Applies to Workday Extend
  • 4 min read
  • Published
  • By Kiweely
On this page

Why four .agentskill files in App Builder appear as a single skill in Agent Management Hub

When you define multiple .agentskill files on a Custom Agent in App Builder—for example, create-equipment-request.agentskill, find-equipment-request.agentskill, edit-equipment-request.agentskill, and view-equipment-request.agentskill referenced under skills: in your .agent file—and click Save and Deploy, opening the agent inside your tenant’s Agent Management Hub shows only one skill row containing the aggregated list of all tools across all four .agentskill files.

This is expected platform behavior, not a failed deployment. As documented in Workday’s Custom Agent architecture (Custom Agents on Workday’s AI Platform):

  • An agent in App Builder can have multiple .agentskill files to modularize instructions, steps, and allowed-tools for the language model at runtime.
  • When you deploy the agent, the Agent System of Record (ASOR) automatically registers the agent and aggregates all tools (tool-wids) across every .agentskill file attached to that .agent into a single combined Skill registration in ASOR.
  • At runtime, the Workday agent runtime still reads your individual .agent and .agentskill files from App Hub to guide the model’s step-by-step reasoning, while ASOR governs user access and tool authorization through that single combined skill entry.

Activating and syncing deployed Custom Agent skills in the tenant

Deploying an agent from App Builder pushes the artifacts to App Hub, but the agent and its skills remain inactive and invisible to end users in Workday Chat until you enable them in ASOR:

  1. In a Development tenant:
    1. Open the Agent Management Hub report and select the Agent Registry tab.
    2. Click your Custom Agent’s name and select Configure Agent.
    3. On the Agent Skill row, switch the Status toggle to enabled.
    4. In the Available To prompt, select the security groups (for example, Employee as Self) that are allowed to invoke the agent.
    5. Check Confirm, click OK, and then click Activate Agent on the agent profile.
  2. In higher environments (Implementation or Sandbox) or after promoting updates: In non-Development environments, promoting the app does not automatically push updated .agentskill tool lists into ASOR. You must trigger the ASOR sync from App Manager:
    1. Open App Manager in the target Workday tenant.
    2. Click Configure on your Agent app (or Extend app containing the Custom Agent).
    3. On the Configuration tab of the App Details page, click Update Agents inside the Agent card to register or refresh the agent definition in ASOR.
    4. In the Update Extend Agents pop-up, select the Confirm check box and click OK, then return to Agent Management Hub > Configure Agent to verify the skill’s Status and Available To security groups.

Also inspect every entry under tool-wids in your .agentskill files in Code Mode: a leading, trailing, or embedded space inside any 32-character wid causes ASOR to silently skip registering that tool.

ASOR tenant prerequisites when Agent Management Hub is inaccessible

If you grant yourself all ASOR security domains in a tenant and still cannot open Agent Management Hub or register agents, check the three layers required for ASOR access:

1. Required ASOR and System security domains

Ensure your security group holds permissions on these domains in the Agent System of Record functional area (plus Activate Pending Security Policy Changes):

  • Agent Management Hub (view the Agent Management Hub and Find Unregistered Workday Agents reports)
  • Manage: Agents (run Configure Agent, Activate Agent, Deactivate Agent, and View Security for Agent Skill)
  • Setup: Agents (register agents and query /asor/v1/agentResourceSearch)
  • Agent Compliance and Reports: Agent Reporting (view compliance and session analytics)
  • Reports: AI Agent Security and Set Up: Tenant Setup - Security in the System functional area

2. Tenant enablement, UMSA, and Innovation Services

Domain permissions alone do not turn on the Agent System of Record runtime if the tenant itself has not been provisioned for Workday AI / ASOR:

  • Subscription Service Agreement (UMSA vs. MSA): Check your organization’s agreement on Workday Community (Profile > organization name > Subscription Service Agreement). Customers on the Universal Main Service Agreement (UMSA) have AI features enabled without Innovation Services tasks. Customers on the Main Service Agreement (MSA) must enable Innovation Services and Machine Learning data contributions. While self-built agents in non-Production tenants do not require a signed UMSA, Workday-built agents require UMSA in both non-Production and Production tenants (plus Workday Flex Credits).
  • Development tenant provisioning: If Agent Management Hub remains unavailable in a Development tenant after activating all domain security policy changes, contact your Workday Customer Success Manager (CSM) or open a Workday Support case to verify that ASOR and Extend AI tenant provisioning are enabled on that environment.

3. Can you add custom skills to Workday-delivered agents?

You cannot attach custom .agentskill files directly to a first-party Workday-built agent (such as the Self-Service Agent); on a Workday-delivered agent, administrators can only enable or disable the skills Workday delivers. To add custom business logic alongside the Self-Service Agent, build a Custom Agent in App Builder (with Agent-Ready Tools and Custom Agent Action orchestrations); once activated in ASOR, your Custom Agent becomes discoverable inside the Workday Self-Service Agent chat panel and Sana.

Verifying the configuration in your tenant

Open Agent Management Hub > Agent Registry, select your Custom Agent, and confirm its status is Active and the skill row shows Enabled with your target security groups in Available To. Click View Security on the Skills tab to run View Security for Agent Skill, verifying that all tools aggregated from your .agentskill files appear in the list and show no Config Required gaps.

Sources checked

Related guides

All guides

Let Workday check the work.

Kiweely writes WQL and builds orchestrations in your own tenant, and Workday, not Kiweely, says whether they passed.

Get the next guide in your inbox.

One email a month with new guides and one Extend tip. Nothing else.

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