Platform Permission Set Generate

Generates Salesforce permission set XML with proper object CRUD, field-level security, user permissions, and tab visibility. The real value is in the guardrails: it won't let you add required fields to fieldPermissions (a common deployment killer), handles the annoying tab naming conventions (custom object tabs need __c suffixes, standard ones need the standard- prefix), and structures the metadata correctly for API v60.0+. If you've ever had a permission set fail deployment because you accidentally included a master-detail field or botched the XML structure, this keeps you from making those mistakes again.

skills.sh installs: 6.8K
GitHub stars: 1.2K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add forcedotcom/sf-skills --skill platform-permission-set-generate --agent claude-code

Installs into .claude/skills of the current project.

Files

When to Use This Skill

Use when generating or editing permission set metadata, or when granting object, field, user, and app permissions.

Step 1: Define Core Properties

Start by defining the required permission set properties:

<PermissionSet xmlns="http://soap.sforce.com/2006/04/metadata">
    <fullName>YourPermissionSetName</fullName>
    <label>Display Name for Administrators</label>
    <description>Clear description of purpose and intended audience</description>
</PermissionSet>

Naming conventions:

Use descriptive API names (e.g., Sales_Manager_Access)

Step 2: Configure Object Permissions

Add CRUD permissions for standard and custom objects:

<objectPermissions>
    <allowCreate>true</allowCreate>
    <allowRead>true</allowRead>
    <allowEdit>true</allowEdit>
    <allowDelete>false</allowDelete>
    <modifyAllRecords>false</modifyAllRecords>
    <viewAllRecords>false</viewAllRecords>
    <viewAllFields>false</viewAllFields>
    <object>Account</object>
</objectPermissions>