Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
jaganpro avatar

Sf Permissions

  • 1.4k installs
  • 423 repo stars
  • Updated April 27, 2026
  • jaganpro/sf-skills

sf-permissions is an agent skill that apply sf-permissions agent skill workflows from documented skill.md guidance.

About

sf-permissions is an agent skill from jaganpro/sf-skills that apply sf-permissions agent skill workflows from documented skill.md guidance. # sf-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. ## When This Skill Owns the Task Use `sf-permissions` when the work involves: - permission set Developers invoke sf-permissions during build/integrations work for automation & workflows tasks. The skill documents triggers, prerequisites, and step-by-step workflows grounded in SKILL.md. Compatible with Claude Code, Cursor, and Codex agent runtimes that load marketplace skills. Review the Security Audits panel on this listing before installing in production environments. Category Automation & Workflows with development vertical focus supports repeatable agent-guided delivery.

  • When This Skill Owns the Task
  • Use `sf-permissions` when the work involves:
  • permission set / permission set group analysis
  • finding which permission grants object / field / Apex / flow / tab / custom-permission access
  • auditing or exporting permission configuration

Sf Permissions by the numbers

  • 1,361 all-time installs (skills.sh)
  • +5 installs in the week ending Aug 5, 2026 (Skillselion tracking)
  • Ranked #229 of 2,715 Automation & Workflows skills by installs in the Skillselion catalog
  • Security screen: MEDIUM risk (skills.sh audit)
  • Data as of Aug 5, 2026 (Skillselion catalog sync)
At a glance

sf-permissions capabilities & compatibility

Capabilities
when this skill owns the task · use `sf permissions` when the work involves: · permission set / permission set group analysis · finding which permission grants object / field / · auditing or exporting permission configuration
Use cases
orchestration
From the docs

What sf-permissions says it does

Use `sf-permissions` when the work involves:
SKILL.md
- permission set / permission set group analysis
SKILL.md
- finding which permission grants object / field / Apex / flow / tab / custom-permission access
SKILL.md
npx skills add https://github.com/jaganpro/sf-skills --skill sf-permissions

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs1.4k
repo stars423
Security audit3 / 3 scanners passed
Last updatedApril 27, 2026
Repositoryjaganpro/sf-skills

What it does

Apply sf-permissions agent skill workflows from documented SKILL.md guidance.

Who is it for?

Developers working on automation & workflows during build tasks.

Skip if: Tasks outside Automation & Workflows scope described in SKILL.md.

When should I use this skill?

Apply sf-permissions agent skill workflows from documented SKILL.md guidance.

What you get

Completed automation & workflows workflow aligned with SKILL.md steps.

  • Permission analysis report
  • User access visualization

Files

SKILL.mdMarkdownGitHub ↗

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

When This Skill Owns the Task

Use sf-permissions when the work involves:

  • permission set / permission set group analysis
  • user access investigation
  • finding which permission grants object / field / Apex / flow / tab / custom-permission access
  • auditing or exporting permission configuration
  • reviewing permission metadata impacts

Delegate elsewhere when the user is:

  • creating new metadata definitions → sf-metadata
  • deploying permission sets → sf-deploy
  • analyzing Apex-managed sharing logic → sf-apex

---

Required Context to Gather First

Ask for or infer:

  • target org alias
  • whether the question is about an object, field, Apex class, flow, tab, custom permission, or specific user
  • whether the goal is hierarchy visualization, access detection, export, or metadata generation
  • whether the output should be terminal-focused or documentation-friendly

---

Recommended Workflow

1. Classify the request

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

2. Connect to the correct org

Verify sf auth before running permission analysis.

3. Use the narrowest useful query

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.Name
  • PermissionSetGroup.DeveloperName
  • CustomPermission.DeveloperName
  • object and field API names such as Account or Account.AnnualRevenue
  • Assignee.Username / email for user-centric checks

Use Salesforce record IDs only when:

  • the underlying object model requires ParentId or SetupEntityId, or
  • you are drilling into records returned by a prior read-only query in the same investigation

4. Render findings clearly

Use:

  • ASCII tree or table output for terminal work
  • Mermaid only when documentation benefit is clear
  • concise summaries of which permission source grants access

5. Hand off creation or deployment work

Use:

  • sf-metadata for richer metadata generation
  • sf-deploy for deployment

---

High-Signal Rules

  • distinguish direct Permission Set grants from grants via Permission Set Groups
  • prefer Name / DeveloperName / API names over org-specific record IDs for first-pass investigation queries
  • be explicit about whether access is object-level, field-level, class-level, flow-level, or custom-permission-based
  • use Tooling API where required for setup entities and advanced visibility questions
  • for agent access questions, verify exact agent-name matching in permission metadata
  • when a follow-up child query requires ParentId or SetupEntityId, resolve the ID from a prior result instead of starting with copied IDs

---

Output Format

When finishing, report in this order: 1. What was analyzed 2. Org / subject scope 3. Which permissions grant access 4. Whether access is direct or inherited 5. Recommended follow-up

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>

---

Cross-Skill Integration

NeedDelegate toReason
generate or modify permission metadatasf-metadatametadata authoring
deploy permission changessf-deployrollout
identify Apex classes needing grantssf-apeximplementation context
bulk user assignment analysissf-datalarger data operations

---

Reference Map

Start here

  • references/permission-model.md
  • references/soql-reference.md
  • references/workflow-examples.md

Specialized analysis

  • references/agent-access-guide.md
  • references/usage-examples.md

---

Score Guide

ScoreMeaning
90+strong permission analysis with clear access sourcing
75–89useful audit with minor gaps
60–74partial visibility only
< 60insufficient evidence; expand analysis

Related skills

Forks & variants (1)

Sf Permissions has 1 known copy in the catalog totaling 33 installs. They canonicalize to this original listing.

FAQ

What does sf-permissions do?

Apply sf-permissions agent skill workflows from documented SKILL.md guidance.

When should I use sf-permissions?

During build integrations work for automation & workflows.

Is sf-permissions safe to install?

Review the Security Audits panel on this listing before production use.

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.