platform-permission-set-generate

Generates deployable Salesforce PermissionSet XML metadata with object, field, user, and app permissions.

Updated Jul 2, 2026
One-click install
npx skills add https://github.com/padjei/SF_Build --skill platform-permission-set-generate-padjei
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: platform-permission-set-generate
Source: https://github.com/padjei/SF_Build/tree/main/.claude/skills/platform-permission-set-generate
Command: npx skills add https://github.com/padjei/SF_Build --skill platform-permission-set-generate-padjei

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing Salesforce permission set XML by hand is error-prone: incorrect API names, field-level security on required fields, and wrong tab naming all cause deployment failures. This Skill guides the generation of correct, deployable PermissionSet metadata covering object CRUD, FLS, user permissions, tab visibility, and more. ## Core Features & Use Cases - Complete PermissionSet XML Generation: Produces metadata covering object permissions, field-level security, user permissions, app and tab visibility, Apex/Visualforce access, record types, and Agentforce agent access. - Deployment Failure Prevention: Enforces rules such as never granting FLS on required fields, using the __c suffix for custom tabs, and the standard- prefix for standard object tabs. - Use Case: An admin needs a permission set granting sales managers read/edit access to Accounts, visibility of a custom tab, and API access. The Skill outputs a validated PermissionSet XML file ready to deploy via Salesforce CLI. ## Quick Start Generate a Salesforce permission set named Sales_Manager_Access with read and edit access on Account, visibility for the Sales console app, and API enabled user permission.

Frequently Asked Questions about platform-permission-set-generate

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a Salesforce permission set in XML?▼

Define a PermissionSet XML file with fullName, label, and description, then add objectPermissions, fieldPermissions, userPermissions, and tabSettings blocks as needed. Deploy the file using Salesforce CLI against Metadata API v60.0 or later.

How to set field-level security in a Salesforce permission set?▼

Add a fieldPermissions block with the field in ObjectName.FieldName format, setting readable and editable flags. Never include required fields, since the platform rejects FLS on them and the deployment will fail.

Why does my permission set deployment fail?▼

Common causes are field permissions on required fields, incorrect API names, and missing __c suffixes on custom objects, fields, or tabs. Verify each field exists in object metadata and is not marked required before adding it.

What tab visibility values does Salesforce support?▼

Tab settings support Visible, Available, and None. Custom object tabs must use the API name with the __c suffix, while standard object tabs use the standard- prefix such as standard-Account.

Can a permission set grant access to Apex classes and Visualforce pages?▼

Yes, use classAccesses with the apexClass name and pageAccesses with the apexPage name, each with an enabled flag. This grants users assigned the permission set access to the specified custom code.