Skill Metadata Type for Omni-Channel & Field Service

Why the Skill Metadata Type Powers Intelligent Routing#

When simple queue membership is too rigid—for example, when a single Case requires Spanish Language + Enterprise Billing + AWS Certification—creating a separate Queue for every permutation leads to “queue explosion.” Instead, Skill (skills/<Name>.skill-meta.xml) defines discrete capabilities that are dynamically matched across:

1. Omni-Channel Skills-Based Routing: Matching SkillRequirement records created by an Omni-Channel Flow or SkillMappingConfig against online agents’ ServiceResourceSkill records.
2. Salesforce Field Service (FSL): Matching technician certifications (ServiceResourceSkill) with WorkOrder and WorkType skill requirements.
3. Salesforce Scheduler: Matching customer appointment topics to qualified bankers, clinicians, or advisors.

Key Metadata Fields on Skill#

Real-World XML Example (skills/Enterprise_Cloud_Architecture.skill-meta.xml)#

<?xml version="1.0" encoding="UTF-8"?>
<Skill xmlns="http://soap.sforce.com/2006/04/metadata">
    <description>Certified to troubleshoot multi-region enterprise cloud infrastructure and VPN peering.</description>
    <label>Enterprise Cloud Architecture</label>
</Skill>

Querying Skill, ServiceResourceSkill, and SkillRequirement via SOQL#

In Apex and Omni-Channel Flows, you regularly query Skill to look up SkillId values and inspect which agents (ServiceResource) hold active certifications.

1. List All Skills Configured in the Org#

SELECT Id, DeveloperName, MasterLabel, Description, LastModifiedDate
FROM Skill
ORDER BY MasterLabel ASC

2. Query Active Agents and Their Skill Proficiency Levels (ServiceResourceSkill)#

SELECT Id, ServiceResource.Name, ServiceResource.RelatedRecord.Username,
       Skill.DeveloperName, Skill.MasterLabel, SkillLevel,
       EffectiveStartDate, EffectiveEndDate
FROM ServiceResourceSkill
WHERE ServiceResource.IsActive = true
  AND (EffectiveEndDate = null OR EffectiveEndDate >= TODAY)
ORDER BY Skill.MasterLabel, SkillLevel DESC

3. Inspect Pending Omni-Channel Skill Requirements in Queue#

SELECT Id, RelatedRecordId, Skill.DeveloperName, SkillLevel, IsAdditionalSkill, SkillPriority
FROM SkillRequirement
ORDER BY CreatedDate DESC
LIMIT 50

Senior Architect Best Practices#

• Use ServiceResourceSkill Instead of <assignments>: Do not assign users to skills via the Metadata API <assignments> block inside .skill-meta.xml. That legacy mechanism only applies to Classic Live Agent chat; Omni-Channel Skills-Based Routing, Field Service, and Scheduler all evaluate ServiceResourceSkill records!

Frequently asked questions

Where is the Skill metadata type used in Salesforce?

The Skill metadata type is shared across Omni-Channel Skills-Based Routing, Salesforce Field Service (WorkOrder and WorkType SkillRequirements), and Salesforce Scheduler (matching appointment topics to ServiceResourceSkill records).

Why should you avoid deploying user and profile assignments inside Skill metadata files?

While Skill metadata supports an assignments block for profiles and users, modern Omni-Channel and Field Service implementations assign skills dynamically using ServiceResource and ServiceResourceSkill records rather than hardcoded metadata usernames.

What is the skillType field on Skill metadata?

Added in API version 58.0, skillType links a Skill to a parent SkillType category (for example, grouping Spanish, French, and German under a Language SkillType) to organize large skill catalogs.

How do you query Skills and agent skill proficiencies using SOQL?

You query the Skill object for DeveloperName and MasterLabel, query ServiceResourceSkill to inspect which agents hold each skill and their SkillLevel (0 to 99.99), and query SkillRequirement on PendingServiceRouting or WorkOrder.