Agent skill

Platform Permission Set Generate

Generates correct, deployable Salesforce permission set metadata (PermissionSet XML) with object, field, user, and app permissions.

Apache-2.0Auto-check passedSales & Support

Install Platform Permission Set Generate

skills CLI

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

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install forcedotcom/sf-skills platform-permission-set-generate --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/forcedotcom/sf-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/platform-permission-set-generate .claude/skills/platform-permission-set-generate && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "platform-permission-set-generate" agent skill from https://github.com/forcedotcom/sf-skills/tree/main/skills/platform-permission-set-generate into .claude/skills/platform-permission-set-generate/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "platform-permission-set-generate", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/forcedotcom/sf-skills/tree/main/skills/platform-permission-set-generate

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add forcedotcom/sf-skills --skill platform-permission-set-generate -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install forcedotcom/sf-skills platform-permission-set-generate --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/forcedotcom/sf-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/platform-permission-set-generate .agents/skills/platform-permission-set-generate && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "platform-permission-set-generate" agent skill from https://github.com/forcedotcom/sf-skills/tree/main/skills/platform-permission-set-generate into .agents/skills/platform-permission-set-generate/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "platform-permission-set-generate", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add forcedotcom/sf-skills --skill platform-permission-set-generate -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install forcedotcom/sf-skills platform-permission-set-generate --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/forcedotcom/sf-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/platform-permission-set-generate .cursor/skills/platform-permission-set-generate && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "platform-permission-set-generate" agent skill from https://github.com/forcedotcom/sf-skills/tree/main/skills/platform-permission-set-generate into .cursor/skills/platform-permission-set-generate/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "platform-permission-set-generate", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/forcedotcom/sf-skills.git --path skills/platform-permission-set-generate

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add forcedotcom/sf-skills --skill platform-permission-set-generate -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install forcedotcom/sf-skills platform-permission-set-generate --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/forcedotcom/sf-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/platform-permission-set-generate .gemini/skills/platform-permission-set-generate && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "platform-permission-set-generate" agent skill from https://github.com/forcedotcom/sf-skills/tree/main/skills/platform-permission-set-generate into .gemini/skills/platform-permission-set-generate/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "platform-permission-set-generate", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install forcedotcom/sf-skills platform-permission-set-generate

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add forcedotcom/sf-skills --skill platform-permission-set-generate -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/forcedotcom/sf-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/platform-permission-set-generate .github/skills/platform-permission-set-generate && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "platform-permission-set-generate" agent skill from https://github.com/forcedotcom/sf-skills/tree/main/skills/platform-permission-set-generate into .github/skills/platform-permission-set-generate/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "platform-permission-set-generate", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add forcedotcom/sf-skills --skill platform-permission-set-generate -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install forcedotcom/sf-skills platform-permission-set-generate --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/forcedotcom/sf-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/platform-permission-set-generate .opencode/skills/platform-permission-set-generate && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "platform-permission-set-generate" agent skill from https://github.com/forcedotcom/sf-skills/tree/main/skills/platform-permission-set-generate into .opencode/skills/platform-permission-set-generate/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "platform-permission-set-generate", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: platform-permission-set-generate
GitHub stars: 1.1k
Token cost: ~1.5k tokens
SKILL.md length: 498 words
Files: 1
Skills in repo: 251
Repo updated: Oct 7, 2026
First seen: Oct 7, 2026
Licence: Apache-2.0

At a glance

Generates correct, deployable Salesforce permission set metadata (PermissionSet XML) with object, field, user, and app permissions.

Works in 8 steps: Define Core Properties → Configure Object Permissions → Set Field-Level Security → …
Editing permission set metadata
SKILL.md covers When to Use This Skill, Step 1: Define Core Properties, Step 2: Configure Object… and Step 3: Set Field-Level Security, plus 8 more sections
Reaches soap.sforce.com

What it does

Platform Permission Set Generate is an agent skill from forcedotcom/sf-skills. Generates correct, deployable Salesforce permission set metadata (PermissionSet XML) with object, field, user, and app permissions. Use this skill when creating or editing permission set metadata, object permissions, field-level security (FLS), tab visibility, or deploying permission sets.

Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Sales & Support, covering CRM management. It works with Salesforce. The repository describes itself as: Salesforce's curated collection of agent skills for building applications. Optimized for Agentforce Vibes, compatible with all AI tools. The licence is Apache-2.0.

When your agent uses it

Editing permission set metadata
Object permissions
Field-level security (FLS)
Deploying permission sets

Example prompts

“Use the platform-permission-set-generate skill to generate correct, deployable Salesforce permission set metadata (PermissionSet XML) with object…”
“/platform-permission-set-generate”

Workflow steps

8 steps, taken from the step headings in SKILL.md.

Define Core Properties
Configure Object Permissions
Set Field-Level Security
Grant User Permissions
Configure App and Tab Visibility
Add Apex and Visualforce Access (Optional)
Set License and Record Type Settings (Optional)
Set Agent Access (Optional)

What it can do on your machine

Read from SKILL.md and the folder at commit e5164d9. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are xml).
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
- soap.sforce.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Platform Permission Set Generate loads about 1.5k tokens when it runs. Until then it costs about 81 tokens; SKILL.md has 498 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~81
When it runs · the whole SKILL.md, loaded when a task matches: ~1.5k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from forcedotcom/sf-skills at commit e5164d9, republished under its Apache-2.0 licence (© forcedotcom). 498 words, ~1,502 tokens.

Download SKILL.mdSave it as .claude/skills/platform-permission-set-generate/SKILL.md (or your agent's skills folder).

name: platform-permission-set-generate
description: Generates correct, deployable Salesforce permission set metadata (PermissionSet XML) with object, field, user, and app permissions. Use this skill when creating or editing permission set metadata, object permissions, field-level security (FLS), tab visibility, or deploying permission sets.
metadata.version: 1.0
metadata.domains: Platform
metadata.minApiVersion: 60.0

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:

xml

<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:

xml

<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>

Step 3: Set Field-Level Security

Define field permissions for sensitive or custom fields:

xml

<fieldPermissions>
    <editable>true</editable>
    <readable>true</readable>
    <field>Account.SSN__c</field>
</fieldPermissions>

Important:

Required fields must NEVER appear in list of field permissions. Granting field-level security on required fields is not allowed by the platform and will cause deployment failure.
Before adding any field, confirm from the object metadata that the field exists and is not required
A field is required when its metadata contains <required>true</required>:
Formula fields cannot be editable
Master-detail fields are required fields on the child (detail) object

xml

<fields>
    <fullName>FieldName__c</fullName>
    <required>true</required>
</fields>

Use format ObjectName.FieldName for field references
Set both readable and editable to true when the user needs edit access; editable implies readable
If all fields should be visible, can alternatively enable the "viewAllFields" object permission

Step 4: Grant User Permissions

Add system-level permissions for features and capabilities:

xml

<userPermissions>
    <enabled>true</enabled>
    <name>ApiEnabled</name>
</userPermissions>
<userPermissions>
    <enabled>true</enabled>
    <name>RunReports</name>
</userPermissions>

Common permissions:

ApiEnabled: API access
ViewSetup: View Setup menu
ManageUsers: User management
RunReports: Report execution

Security review required for:

ViewAllData: Read all records
ModifyAllData: Edit all records
ManageUsers: User administration

Step 5: Configure App and Tab Visibility

Make applications and tabs visible to users:

xml

<applicationVisibilities>
    <application>Sales_Console</application>
    <visible>true</visible>
</applicationVisibilities>
<tabSettings>
    <tab>CustomTab__c</tab>
    <visibility>Visible</visibility>
</tabSettings>

Application visibility options:

<visible> can be true or false

Tab visibility options:

Visible: The tab is available on the All Tabs page and appears in the visible tabs for its associated app. Can be customized.
Available: The tab is available on the All Tabs page. Individual users can customize their display to make the tab visible in any app
None: Not visible

CRITICAL - Tab Naming:

Custom object tabs: MUST include the __c suffix (e.g., MyCustomObject__c)
Standard object tabs: Use the object name with "standard-" prefix (e.g., standard-Account, standard-Contact)
The tab name matches the object's API name exactly

Show full SKILL.md (172 more words)Show less

Step 6: Add Apex and Visualforce Access (Optional)

Grant access to custom code:

xml

<classAccesses>
    <apexClass>CustomController</apexClass>
    <enabled>true</enabled>
</classAccesses>
<pageAccesses>
    <apexPage>CustomPage</apexPage>
    <enabled>true</enabled>
</pageAccesses>

Step 7: Set License and Record Type Settings (Optional)

Specify license requirements and record type visibility:

xml

<license>Salesforce</license>
<hasActivationRequired>false</hasActivationRequired>
<recordTypeVisibilities>
    <recordType>Account.Business</recordType>
    <visible>true</visible>
    <default>true</default>
</recordTypeVisibilities>

Step 8: Set Agent Access (Optional)

Enable access to Agentforce Employee Agents for users assigned to this permission set:

<agentAccesses>
    <agentName>Sales_Assistant_Agent</agentName>
    <enabled>true</enabled>
</agentAccesses>

Field requirements:

agentName (Required): The developer name of the employee agent
enabled (Required): Set to true to grant access, false to deny

Important:

Agent names must match existing Agentforce Employee Agent developer names

Validation Checklist

Before deploying, verify:

fullName, label, description set
Permissions follow least privilege
No required fields in <fieldPermissions>
No duplicate permissions
No lengthy comments

What Causes Deployment Failure

Field permissions on required fields: Any required field in <fieldPermissions> fails deployment. Required fields cannot have FLS; omit them entirely. Always confirm from object/field metadata that a field exists and is not required—never assume.
Incorrect API names: Using the wrong name or missing suffixes (e.g. missing __c for custom objects, fields, tabs) cause failure.

Deployment

Deploy using Salesforce CLI

Files

Just SKILL.md in skills/platform-permission-set-generate of forcedotcom/sf-skills.

Open the folder on GitHubat commit e5164d9

Compare with similar skills

Platform Permission Set Generate next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Platform Permission Set Generate compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Platform Permission Set Generate this skillforcedotcom/sf-skills	1.1k	—	~1.5k	Automated safety check: Pass	Apache-2.0	2 days ago
Soql Lib Query Builderbeyond-the-cloud-dev/soql-lib	154	—	~4.3k	Automated safety check: Pass	MIT	6 days ago
Sf DatacloudJaganpro/sf-skills	424	—	~2.7k	Automated safety check: Pass	MIT	5 mo ago
Soql Lib Selectorbeyond-the-cloud-dev/soql-lib	154	—	~2k	Automated safety check: Pass	MIT	6 days ago
Dev SetupPortwood-Global-Solutions/Portwood	126	—	~1.1k	Automated safety check: Pass	Apache-2.0	today
Sf FlowJaganpro/sf-skills	424	—	~1.8k	Automated safety check: Pass	MIT	5 mo ago

Similar skills

Soql Lib Query Builder
beyond-the-cloud-dev/soql-lib
Builds Salesforce SOQL queries using the SOQL Lib fluent builder API (SOQL.cls).
154 GitHub stars~4.3k tokensUpdated 6 days ago
Sales & SupportAuto-check passed
Sf Datacloud
Jaganpro/sf-skills
Salesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows.
424 GitHub stars~2.7k tokensUpdated 5 mo ago
Sales & SupportAuto-check passed
Soql Lib Selector
beyond-the-cloud-dev/soql-lib
Creates Salesforce Apex selector classes using the SOQL Lib selector pattern.
154 GitHub stars~2k tokensUpdated 6 days ago
Sales & SupportAuto-check passed
Dev Setup
Portwood-Global-Solutions/Portwood
Get from a fresh clone of Portwood to a working, fully-tested Salesforce org.
126 GitHub stars~1.1k tokensUpdated today
Sales & SupportAuto-check passed
Sf Flow
Jaganpro/sf-skills
Creates and validates Salesforce Flows with 110-point scoring.
424 GitHub stars~1.8k tokensUpdated 5 mo ago
Sales & SupportAuto-check passed
Google Maps Export
gmapsscraper/google-maps-agent-skills
Export Google Maps business data to CSV, JSON, or CRM format (HubSpot, Pipedrive, Salesforce).
132 GitHub stars~1.2k tokensUpdated 4 mo ago
Sales & SupportAuto-check passed

Questions about Platform Permission Set Generate

What does Platform Permission Set Generate do?

Generates correct, deployable Salesforce permission set metadata (PermissionSet XML) with object, field, user, and app permissions. Platform Permission Set Generate is an agent skill from forcedotcom/sf-skills. Generates correct, deployable Salesforce permission set metadata (PermissionSet XML) with object, field, user, and app permissions.

When should I use Platform Permission Set Generate?

Platform Permission Set Generate fits situations like: editing permission set metadata; object permissions; field-level security (FLS); deploying permission sets.

How do I install Platform Permission Set Generate in Claude Code?

Run `npx skills add forcedotcom/sf-skills --skill platform-permission-set-generate -a claude-code`. Or copy the skill folder (skills/platform-permission-set-generate in forcedotcom/sf-skills) into .claude/skills/platform-permission-set-generate in your project. Claude Code loads it when a task matches its description.

How do I install Platform Permission Set Generate in Codex?

Run `npx skills add forcedotcom/sf-skills --skill platform-permission-set-generate -a codex`. Or copy the skill folder (skills/platform-permission-set-generate in forcedotcom/sf-skills) into .agents/skills/platform-permission-set-generate in your project. Codex loads it when a task matches its description.

Can I use Platform Permission Set Generate in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add forcedotcom/sf-skills --skill platform-permission-set-generate -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/platform-permission-set-generate, .gemini/skills/platform-permission-set-generate, .github/skills/platform-permission-set-generate and .opencode/skills/platform-permission-set-generate in your project.

What does Platform Permission Set Generate need to run?

SKILL.md names no scripts, command-line tools or credentials: Platform Permission Set Generate is instructions for the agent only.

Does Platform Permission Set Generate access the network?

SKILL.md names 1 domain. In commands or code: soap.sforce.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.

Is Platform Permission Set Generate safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Platform Permission Set Generate use?

Platform Permission Set Generate is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Platform Permission Set Generate use?

About 1.5k tokens (SKILL.md is roughly 6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Platform Permission Set Generate?

Skills that share tags, products or a category with Platform Permission Set Generate: Soql Lib Query Builder (beyond-the-cloud-dev/soql-lib, 154 stars), Sf Datacloud (Jaganpro/sf-skills, 424 stars), Soql Lib Selector (beyond-the-cloud-dev/soql-lib, 154 stars) and Dev Setup (Portwood-Global-Solutions/Portwood, 126 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Platform Permission Set Generate?

forcedotcom (a GitHub organization) maintains it in forcedotcom/sf-skills, which has 1,065 GitHub stars. The repository holds 251 skills in this directory. The repository was last updated on October 7, 2026.

Source: forcedotcom/sf-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Platform Permission Set Generate

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

When to Use This Skill

Step 1: Define Core Properties

Step 2: Configure Object Permissions

Step 3: Set Field-Level Security

Step 4: Grant User Permissions

Step 5: Configure App and Tab Visibility

Step 6: Add Apex and Visualforce Access (Optional)

Step 7: Set License and Record Type Settings (Optional)

Step 8: Set Agent Access (Optional)

Validation Checklist

What Causes Deployment Failure

Deployment

Files

Compare with similar skills

Similar skills

More from forcedotcom/sf-skills

Related

Questions about Platform Permission Set Generate