service-omni-attribute-routing-configure
About service-omni-attribute-routing-configure
A Salesforce skill for managing the lifecycle of WorkSkillRouting rules and WorkSkillRoutingAttribute mappings through the Tooling API. It supports multi-mapping workflows, controlled activation, and deletion, while refusing writes in production customer orgs.
Key features
- 01List and retrieve routing rules
- 02Create rules in inactive state
- 03Add and reuse skill mappings
- 04Activate rules after mappings exist
- 05Delete attributes and rules with confirmation
Use cases
- 01Configure routing rules with multiple skill mappings
- 02Keep a rule inactive while adding mappings
- 03Activate a mapped rule and verify it
- 04Remove an attribute or routing rule
Install
Copy the command and run it in a terminal.
npx skills add https:/ / github.com/ forcedotcom/ sf-skills --skill service-omni-attribute-routing-configureAfter installing, type/service-omni-attribute-routing-configurein Claude Code to confirm it loaded.
Bundled files
References and scripts installed along with SKILL.md.
references/api-notes.mdscripts/configure-and-report.shscripts/tests/test_attribute_routing_contracts.pyDetails
From the project READMEservice-omni-attribute-routing-configure
Manage the full WorkSkillRouting and WorkSkillRoutingAttribute lifecycle using the approved Tooling API contract. Create rules inactive, add all mappings, and activate only after at least one mapping exists.
Usage
bash scripts/configure-and-report.sh <org> list
bash scripts/configure-and-report.sh <org> get <rule-id>
bash scripts/configure-and-report.sh <org> create <developer-name> <label> <related-entity>
bash scripts/configure-and-report.sh <org> add-attribute <rule-id> <Entity.Field> <value> <skill-id> <level> <related-entity> [additional] [priority]
bash scripts/configure-and-report.sh <org> set-active <rule-id> true|false
CONFIRM_DELETE=1 bash scripts/configure-and-report.sh <org> delete-attribute <attribute-id>
CONFIRM_DELETE=1 bash scripts/configure-and-report.sh <org> delete-rule <rule-id>
Safety and behavior
- Reads require View Setup. Writes require Customize Application and are refused on production customer orgs.
- Omni-Channel and Skills-Based Routing must be enabled, and referenced
Skillrecords must already exist. - Creation always starts inactive. Activation reads the complete Metadata compound, preserves all mappings, removes the read-only
urlsmember, changes onlyisActive, and verifies with a cold read. - The script rejects activation without mappings, invalid skill levels, invalid additional-skill priorities, and deletion without
CONFIRM_DELETE=1. - Existing identical mappings are reused.
Boundaries
Use service-omni-work-skill-routing-configure for the simpler one-mapping Metadata API workflow. Use this skill when the user explicitly needs Tooling CRUD, multiple mappings, activation control, or deletion.
Reference
Read references/api-notes.md before changing the payload or compound Metadata handling.