From jaganpro-sf-skills-7
Analyzes Salesforce Permission Sets and Groups for hierarchy views, access auditing, user-permission reviews, and 'who has access to X?' queries on objects, fields, and metadata.
npx claudepluginhub jaganpro/sf-skillsThis skill uses the workspace's default tool permissions.
Use this skill when the user needs **permission analysis and access auditing**: Permission Set / Permission Set Group hierarchy views, “who has access to X?” investigations, user-permission analysis, or permission-set metadata review.
CREDITS.mdLICENSEREADME.mdreferences/agent-access-guide.mdreferences/permission-model.mdreferences/soql-reference.mdreferences/usage-examples.mdreferences/workflow-examples.mdrequirements.txtscripts/__init__.pyscripts/auth.pyscripts/cli.pyscripts/hierarchy_viewer.pyscripts/metadata_fetcher.pyscripts/permission_detector.pyscripts/permission_exporter.pyscripts/renderers/__init__.pyscripts/renderers/ascii_tree.pyscripts/renderers/mermaid.pyscripts/tooling_api.pyConfigures Salesforce Profiles, Permission Sets, Roles, OWD, and Sharing Rules for enterprise RBAC including SSO integration.
Audits table permissions on Power Pages sites against site code and Dataverse metadata. Generates HTML report with severity-grouped findings (critical, warning, info, pass) and fix suggestions.
Generates Salesforce metadata XML for custom objects, fields, validation rules, record types, layouts, profiles; queries org schema via sf CLI. For .object-meta.xml and related files.
Share bugs, ideas, or general feedback.
Use this skill when the user needs permission analysis and access auditing: Permission Set / Permission Set Group hierarchy views, “who has access to X?” investigations, user-permission analysis, or permission-set metadata review.
Use sf-permissions when the work involves:
Delegate elsewhere when the user is:
Ask for or infer:
| Request shape | Default capability |
|---|---|
| “who has access to X?” | permission detector |
| “what does this user have?” | user analyzer |
| “show me the hierarchy” | hierarchy viewer |
| “export this permset” | exporter |
| “generate metadata from analysis” | generator or handoff |
Verify sf auth before running permission analysis.
Prefer focused analysis over broad org-wide scans unless the user explicitly wants a full audit.
When choosing identifiers, prefer stable metadata names first:
PermissionSet.NamePermissionSetGroup.DeveloperNameCustomPermission.DeveloperNameAccount or Account.AnnualRevenueAssignee.Username / email for user-centric checksUse Salesforce record IDs only when:
ParentId or SetupEntityId, orUse:
Use:
Name / DeveloperName / API names over org-specific record IDs for first-pass investigation queriesParentId or SetupEntityId, resolve the ID from a prior result instead of starting with copied IDsWhen finishing, report in this order:
Suggested shape:
Permission analysis: <hierarchy / detect / user / export>
Scope: <org, user, permission target>
Findings: <permsets / groups / access level>
Source: <direct assignment or via group>
Next step: <export, generate metadata, or deploy changes>
| Need | Delegate to | Reason |
|---|---|---|
| generate or modify permission metadata | sf-metadata | metadata authoring |
| deploy permission changes | sf-deploy | rollout |
| identify Apex classes needing grants | sf-apex | implementation context |
| bulk user assignment analysis | sf-data | larger data operations |
| Score | Meaning |
|---|---|
| 90+ | strong permission analysis with clear access sourcing |
| 75–89 | useful audit with minor gaps |
| 60–74 | partial visibility only |
| < 60 | insufficient evidence; expand analysis |