forcedotcom/sf-skills / plugins/builder/service-omni/skills/service-omni-attribute-routing-configure
service-omni-attribute-routing-configure
VerifiedUse to manage Omni-Channel attribute-based routing rules through the Tooling API. TRIGGER when: list attribute-routing rules, inspect a WorkSkillRouting rule, create an inactive routing rule, add a field-to-skill mapping, activate a complete routing rule, deactivate a routing rule, or delete a routing rule or attribute. Do not use to create agent skills or routing flows.
service-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.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |