← Search

Generate Salesforce PermissionSet XML: object, field, user and app permissions
Development 🧪 Install ran in our test sandbox · Nov 11, 2026 📌 Pinned version: commit e5164d9
Install test only, on the date shown. This does not guarantee the code is safe.
⚙ Needs: Salesforce org access (a free Developer Edition org…

Generate Salesforce PermissionSet XML: object, field, user and app permissions

Generate deployable Salesforce permission set metadata — CRUD object permissions, field-level security, user permissions, app/tab visibility, Apex/Visualforce access, Agentforce agent access — with least-privilege validation rules

At a glance
What
Generate deployable Salesforce permission set metadata — CRUD object permissions, field-level security, user permissions, app/tab visibility, Apex/Visualforce access, Agentforce agent access — with least-privilege validation rules
Cost
Free
Needs
Salesforce org access (a free Developer Edition org works) and the Salesforce CLI for deployment — the skill is guidance the agent follows, not software to install
Install
Copy the installer prompt below into your Muse — your agent does the rest.

Version:

Quick answer

Generate Salesforce PermissionSet XML is a free Muse skill for generating deployable Salesforce PermissionSet XML through an 8-step workflow: core properties with descriptive API names, CRUD object permissions, field-level security, user permissions, app and tab visibility, Apex and Visualforce access, and Agentforce agent access, with least-privilege validation rules. Its hard rule is that required fields must never appear in fieldPermissions.

⌁

Install

Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 11, 2026📌 Pinned version: commit e5164d9

Step 0 — before installing anything: read this install prompt, summarize in a few lines what this build does and what installing it involves, then ask me to confirm before you proceed. Prerequisites: Salesforce org access (a free Developer Edition org works) and the Salesforce CLI for deployment — the skill is guidance the agent follows, not software to install Install "Generate Salesforce PermissionSet XML: object, field, user and app permissions" for me. It teaches my agent @forcedotcom's permission-set workflow: core properties with descriptive API names; CRUD object permissions; field-level security (required fields NEVER in fieldPermissions — confirm from object metadata; formula fields not editable); user permissions with the security-review flag on ViewAllData/ModifyAllData/ManageUsers; app/tab visibility with exact tab naming; optional Apex/Visualforce access, license and record-type settings, and Agentforce agent access. IMPORTANT: permission sets GRANT ACCESS — always review before deploying and test in a sandbox first; follow least privilege. Apache-2.0 licensed. Repository: https://raw.githubusercontent.com/forcedotcom/sf-skills/e5164d94d7511c00fa02a5b8b60754b2361e178f/plugins/builder/salesforce-development/skills/platform-permission-set-generate/SKILL.md Pinned version: install the code at commit e5164d94d7511c00fa02a5b8b60754b2361e178f exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "platform-permission-set-generate". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. hand the agent the access requirements for the permission set; review the generated XML, deploy with the Salesforce CLI to a sandbox first, and verify least privilege before any production deployment). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.

🔒 Security, provenance and what this touches
🧭 What this touches
Based on the install prompt we scanned, this skill does not run commands, make third-party network calls, install packages, write files, or ask for API keys.
Install prompt analysis · 2026-10-13
🔒 Security and provenance
📌 Pinned version: commit e5164d9 · 2026-10-13
🧪 Install ran in our test sandbox · Nov 11, 2026
👁 Observed during the install test · Nov 11, 2026 : no network contact
🔎 Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Wanna be extra careful?

The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?

How to check a skill before installing →

✓

Verification certificate

Dated facts about what was checked for this listing, and how. This is not a safety certification.

Pinned version
e5164d9 · 2026-10-13
Sandbox install test
Install ran in our test sandbox · Nov 11, 2026
Creator identity
Not verified
Fingerprint watch
Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
Install prompt analysis
2026-10-13 : No commands, network calls, packages, file writes or API keys detected.

Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify

?

Questions

How do I install a skill?

Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill up for you — no manual configuration.

Where does my money go?

Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.

What does the ✓ next to a creator’s name mean?

It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a skill before installing it.