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

Sf Permissions

  • 33 installs
  • 423 repo stars
  • Updated April 27, 2026
  • jaganpro/claude-code-sfskills

This is a copy of sf-permissions by jaganpro - installs and ranking accrue to the original listing.

Helps with ai & agent building tasks.

About

sf-permissions is a Claude Code skill for ai & agent building. It helps solo builders move faster with AI-assisted development.

  • sf-permissions
  • AI & Agent Building
  • AI-coding skill

Sf Permissions by the numbers

  • 33 all-time installs (skills.sh)
  • Data as of Aug 2, 2026 (Skillselion catalog sync)
npx skills add https://github.com/jaganpro/claude-code-sfskills --skill sf-permissions

Add your badge

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

Listed on Skillselion
Installs33
repo stars423
Last updatedApril 27, 2026
Repositoryjaganpro/claude-code-sfskills

What it does

Helps with ai & agent building tasks.

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.

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

---

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

This week in AI coding

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

unsubscribe anytime.