Skill
A Skill in Salesforce is a standard object that represents a specific competency, certification, or capability, such as an HVAC certification, fluency in Spanish, or a security clearance.
Definition
A Skill in Salesforce is a standard object that represents a specific competency, certification, or capability, such as an HVAC certification, fluency in Spanish, or a security clearance. Salesforce defines the Skill object as a category or group of agents or service resources used in Field Service, Omni-Channel routing, and Workforce Engagement. The object is lightweight: each record mainly stores a label, an API name, and an optional description.
Skills become useful when you attach them to work and to people. A work item (a service appointment or a case) declares which skills are required, and a person (a service resource or an agent) declares which skills they hold. The matching engine then assigns the work only to qualified people. This is the backbone of skills-based scheduling in Field Service and skills-based routing in Omni-Channel.
How the Skill object connects work to qualified people
One vocabulary, two assignment engines
The Skill object itself is deliberately simple. It is a shared dictionary of competency names that two different Salesforce features draw from. Field Service uses skills to schedule on-site work to the right technician. Omni-Channel uses skills to route digital work, like cases and chats, to the right agent. The object became available in API version 24.0, originally to route live chats, and its role expanded as Field Service and Workforce Engagement matured. Because the Skill object is standard, you create records once and reference them everywhere. A skill named Electrical Wiring can gate a service appointment for a field technician and also route an inbound case to an agent who specializes in electrical products. The two engines read the same skill names, so your competency model stays consistent across phone, chat, and the field. That consistency matters for reporting. When the same skill drives both digital and on-site assignment, leaders can ask one question (how much demand do we have for Electrical work) and trust the answer spans every channel rather than living in separate silos.
ServiceResourceSkill: who holds which skill, and when
In Field Service and Salesforce Scheduler, you do not store a skill directly on a person. You create a ServiceResourceSkill record, a junction between a Service Resource and a Skill. This object, available since API version 38.0, is where the real-world detail lives. It carries a SkillLevel value and an effective date range (EffectiveStartDate and EffectiveEndDate). The date range is the feature most teams overlook. Certifications expire, and a technician who was qualified last quarter may not be qualified today. Instead of deleting the skill, you set an end date. The scheduling engine only considers a ServiceResourceSkill whose effective window covers the appointment time. So when an HVAC license lapses, you close the record on the expiry date and the optimizer stops matching that person for HVAC work automatically. No cleanup of in-flight appointments is needed. SkillLevel in Field Service accepts a value from 0 to 99.99, so you are free to model proficiency on whatever scale your business already uses, whether that is a simple 1 to 5 or a granular percentage.
Required skills on work orders and the Match Skills rule
For a skill to gate a service appointment, the work has to declare what it needs. In Field Service you add required skills to a Work Order, a Work Order Line Item, or a Work Type, and you can attach a minimum skill level to each requirement. A Work Type acts as a template, so adding required skills there means every work order created from that type inherits them without manual entry. The enforcement happens through a scheduling work rule called Match Skills. When the optimizer or the scheduling logic evaluates candidates, the Match Skills rule filters out any resource who lacks a required skill or whose SkillLevel falls below the minimum. A required skill with a minimum level of 70 means a technician at level 60 is never offered the appointment, even if they are the closest available person. This is how you protect customer experience on complex jobs while still letting junior staff handle routine work. Pair the requirement with the effective date logic and you get a system that respects both proficiency and currency of certification at the same time.
Skills-based routing in Omni-Channel
Omni-Channel reuses the same Skill object but routes differently. Instead of optimizing a schedule, it picks the best available agent for a live or queued work item. You enable skills-based routing, create your skills in Setup, and assign skills to agents (who are themselves Service Resources in this model). When a work item needs routing, a skill requirement is attached to it and Salesforce writes a PendingServiceRouting record that holds the requirements while it searches for a match. There are two ways to attach the requirements. Skills-based routing rules let you map work-item field values to skills declaratively. For example, a case with Product equal to Solar Panel can automatically pick up the Solar skill. The other way is an Omni-Channel flow, where you use an Add Skill Requirement action to build the requirements with whatever logic you need before a Route Work action sends the item on. The underlying SkillRequirement object represents a skill needed to complete a task, and Salesforce reuses it across Field Service, Omni-Channel, Salesforce Scheduler, and Workforce Engagement.
A worked example across both worlds
Picture a solar installer that runs both a contact center and a field crew. The team defines one skill, Solar Installation, plus a language skill, Spanish. On the digital side, a skills-based routing rule maps any case where Product Family equals Solar to the Solar Installation skill, and a second rule maps Preferred Language equals Spanish to the Spanish skill. An inbound Spanish case about a solar product now routes only to bilingual solar agents through Omni-Channel. On the field side, the same two skills appear on a Work Type called Solar Panel Service, with Solar Installation set to a minimum level of 60. Technicians carry ServiceResourceSkill records: a senior installer holds Solar Installation at level 90 with no end date, while a trainee holds it at level 40. When a service appointment is generated from that work type, the Match Skills rule offers it to the senior installer and skips the trainee, whose level is below the threshold. One competency vocabulary, defined once, now governs who answers the phone and who shows up at the door, with proficiency and certification windows respected on both paths.
Governance: keeping a skills model honest
A skills taxonomy decays if no one tends it. Rosters change, certifications expire, and new product lines introduce new competencies. A stale model fails quietly. Work still routes, but it routes to the wrong people, and there is rarely an obvious error to alert you. That makes periodic auditing a real operational task, not a nice-to-have. Treat the master skill list as a governed asset. Keep it short and unambiguous so two admins never create near-duplicate skills like Spanish and Spanish Language that split your matching pool. Review ServiceResourceSkill records on a regular cadence to catch lapsed certifications and to add skills for newly trained staff. If you run both Field Service and Omni-Channel, agree on one canonical name for each competency and apply it in both feature areas so cross-channel reports line up. Document who owns the taxonomy and what triggers a change, such as a new certification program or a product launch. The Skill object is cheap to create and easy to neglect, and the cost of neglect shows up as mis-assigned work rather than a hard failure.
How to set up and use a Skill
Skills are created and managed in Setup, then attached to work and to people. These steps cover the common path: defining a skill and wiring it into skills-based routing for Omni-Channel. The Field Service path is similar, except you assign the skill through ServiceResourceSkill records and reference it on work orders or work types.
- Enable skills-based routing
In Setup, open Omni-Channel Settings and enable skills-based routing. This unlocks the skill creation and assignment screens used by the routing engine.
- Create the skill
Go to Skills in Setup and create a record with a clear label and API name. Keep the name specific and unique so it is not confused with a near-duplicate later.
- Assign the skill to people
Assign the skill to the agents or service resources who hold that competency. In Field Service, this assignment is stored as a ServiceResourceSkill record with a skill level and effective dates.
- Attach skill requirements to work
Use a skills-based routing rule to map a work-item field value to the skill, or build the requirement in an Omni-Channel flow with an Add Skill Requirement action before routing.
- Test with real records
Route a sample case or generate a service appointment and confirm it reaches only qualified people. Adjust minimum skill levels until the assignment behavior matches your intent.
A proficiency value (0 to 99.99 in Field Service) that lets you require a minimum competency, so complex work skips less experienced people.
Start and end dates on a ServiceResourceSkill that scope when a person counts as qualified, handling certification expirations without manual cleanup.
Skills-based routing rules map fields to skills declaratively; an Omni-Channel flow gives programmatic control through an Add Skill Requirement action.
- Field Service skills and Omni-Channel skills draw on the same Skill object but are assigned and enforced differently, so confirm you are configuring the right feature path.
- A required skill with no qualified, available person leaves work unassigned. Always confirm coverage before turning on a strict minimum skill level.
- Near-duplicate skill names silently split your matching pool. Govern the master list so the same competency is not created twice under slightly different labels.
Trust & references
Cross-checked against the following references.
Straight from the source - Salesforce's reference material on Skill.
Hands-on resources to go deeper on Skill.
About the Author
Dipojjal Chakrabarti is a B2C Solution Architect with 29 Salesforce certifications and over 13 years in the Salesforce ecosystem. He runs salesforcedictionary.com to help admins, developers, architects, and cert/interview candidates sharpen their fundamentals. More about Dipojjal.
Discussion
Loading discussion…