Individual skill
service-itsm-agentic-setup-agent-runtime-access-assign
Grant a user the runtime permissions an activated ITSM agent's actions need so the actions do not fail on permission errors. After a Fulfiller or Employee agent is activated, this skill detects which platform feature permission sets are provisioned (Prompt Templates, Data Cloud, Unified Catalog), lets you pick a tier (user/agent vs admin) per feature and which user(s) to assign, then assigns them (license first when license-gated). It also creates a custom "Agent Access" permission set granting the activated agents you choose and assigns it to the user — all via the Salesforce CLI. Use to grant a user access to an activated agent, to assign prompt-template, data-cloud, or unified-catalog access, or to create an Agent Access permission set. DO NOT TRIGGER for enabling Agentforce for IT Service toggles, creating or activating an agent, the Fulfiller activation action-surfacing gap (service-itsm-agentic-setup-itsm-agentforce-permset-assign), CMDB access, or generic permission-set assignment.
skills/service-itsm-agentic-setup-agent-runtime-access-assign/SKILL.md
Source commit a8a18ce1e4ba12e69b4073eab98ce31bfbd8271e
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 4, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 1,151
- Repository last updated
- Nov 6, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- data Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 21,848 bytesSKILL.mdcore · 21,848 bytesSKILL.mdcore · 21,848 bytesSKILL.mdcore · 21,848 bytesSKILL.mdcore · 21,848 bytesSKILL.mdcore · 21,848 bytesSKILL.mdcore · 21,848 bytesSKILL.mdcore · 21,848 bytesSKILL.mdcore · 21,848 bytesSKILL.mdcore · 21,848 bytesreferences/cli-invocation.mddoc · 9,890 bytesreferences/helper-contracts.mddoc · 10,866 bytesreferences/permset-topology.mddoc · 7,538 bytesscripts/classify-activated-agents.mjsruns · 4,454 bytesscripts/classify-agent-access-state.mjsruns · 5,509 bytesscripts/classify-assignment-state.mjsruns · 4,794 bytesscripts/classify-platform-permset-availability.mjsruns · 6,429 bytesscripts/gate-unified-catalog-tiers.mjsruns · 4,799 bytesscripts/rank-candidate-users.mjsruns · 4,839 bytesscripts/resolve-target-user.mjsruns · 3,029 bytes
Read excerpt
# Grant Runtime Access for an Activated ITSM Agent
An ITSM agent (Fulfiller or Employee) can be created and activated, yet **fail the moment it's opened** — its actions call platform features the **user** can't execute. This skill closes that gap after activation via two write-capable steps behind one confirmation:
1. **Runtime action-execution permissions.** Detect which **feature permission sets** are provisioned, let the user pick a **tier per feature** (user/agent vs admin) and which **user(s)** to grant, then assign — **license first** when license-gated.
2. **A custom "Agent Access" permission set.** Create (or reuse) **Agent Access**, grant the **activated agents** the user chooses (one `SetupEntityAccess` per agent), then assign it to the same user(s).
The verified feature → tier → permset matrix lives in `references/permset-topology.md`. **No org has all three features** — assign only what is provisioned and report the rest as unavailable, never failing on an absent feature.
Every read and write runs through the **Salesforce CLI (`sf`)** — no metadata XML, no token extraction, no MCP.
## Scope
- **In scope**: detecting which platform feature permsets are provisioned; per-feature tier selection; asking which user(s) to grant (running user offered, never silent) and resolving them; PSL-then-permset assignment (license-gated tiers) idempotently; creating/reusing the custom `Agent_Access` permission set; adding a `SetupEntityAccess` grant per chosen **activated** agent; assigning `Agent_Access` to the user(s); verifying assignments by read-back.