[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CBH86PDEF2644B4BSQP9QQ":3,"skill-same:01M7CBH86PDEF2644B4BSQP9QQ":51},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":29,"commitSha":30,"skillDirectory":31,"forksCount":32,"repositoryHtmlUrl":33,"repositoryHomepageUrl":6,"ownerHtmlUrl":34,"ownerBlogUrl":6,"ownerDescription":35,"updatedAt":36,"install":37,"resources":50},"01M7CBH86PDEF2644B4BSQP9QQ","sf-permissions",null,"Permission Set analysis, hierarchy viewer, and access auditing. TRIGGER when: user asks \"who has access to X?\", analyzes permission sets\u002Fgroups, or touches .permissionset-meta.xml \u002F .permissionsetgroup-meta.xml files. DO NOT TRIGGER when: creating new metadata (use sf-metadata), deploying permission sets (use sf-deploy), or Apex sharing logic (use sf-apex).","om-scogo\u002Fskillsh-scraper","om-scogo","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160466840?v=4","01M79AWB6DFVCQ7RK70CS34B96","Om Achrekar","01M79AWB6ZM9SKR8KDH1WSSM22",0,"MIT","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fjaganpro-sf-skills\u002Fsf-permissions\u002Fskills\u002Fsf-permissions\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: sf-permissions\ndescription: >\n  Permission Set analysis, hierarchy viewer, and access auditing.\n  TRIGGER when: user asks \"who has access to X?\", analyzes permission sets\u002Fgroups,\n  or touches .permissionset-meta.xml \u002F .permissionsetgroup-meta.xml files.\n  DO NOT TRIGGER when: creating new metadata (use sf-metadata), deploying\n  permission sets (use sf-deploy), or Apex sharing logic (use sf-apex).\nlicense: MIT\nmetadata:\n  version: \"1.1.0\"\n  author: \"Jag Valaiyapathy\"\n  inspiration: \"PSLab by Oumaima Arbani (github.com\u002FOumArbani\u002FPSLab)\"\n---\n\n# sf-permissions\n\nUse this skill when the user needs **permission analysis and access auditing**: Permission Set \u002F Permission Set Group hierarchy views, “who has access to X?” investigations, user-permission analysis, or permission-set metadata review.\n\n## When This Skill Owns the Task\n\nUse `sf-permissions` when the work involves:\n- permission set \u002F permission set group analysis\n- user access investigation\n- finding which permission grants object \u002F field \u002F Apex \u002F flow \u002F tab \u002F custom-permission access\n- auditing or exporting permission configuration\n- reviewing permission metadata impacts\n\nDelegate elsewhere when the user is:\n- creating new metadata definitions → [sf-metadata](..\u002Fsf-metadata\u002FSKILL.md)\n- deploying permission sets → [sf-deploy](..\u002Fsf-deploy\u002FSKILL.md)\n- analyzing Apex-managed sharing logic → [sf-apex](..\u002Fsf-apex\u002FSKILL.md)\n\n---\n\n## Required Context to Gather First\n\nAsk for or infer:\n- target org alias\n- whether the question is about an object, field, Apex class, flow, tab, custom permission, or specific user\n- whether the goal is hierarchy visualization, access detection, export, or metadata generation\n- whether the output should be terminal-focused or documentation-friendly\n\n---\n\n## Recommended Workflow\n\n### 1. Classify the request\n| Request shape | Default capability |\n|---|---|\n| “who has access to X?” | permission detector |\n| “what does this user have?” | user analyzer |\n| “show me the hierarchy” | hierarchy viewer |\n| “export this permset” | exporter |\n| “generate metadata from analysis” | generator or handoff |\n\n### 2. Connect to the correct org\nVerify `sf` auth before running permission analysis.\n\n### 3. Use the narrowest useful query\nPrefer focused analysis over broad org-wide scans unless the user explicitly wants a full audit.\n\nWhen choosing identifiers, prefer stable metadata names first:\n- `PermissionSet.Name`\n- `PermissionSetGroup.DeveloperName`\n- `CustomPermission.DeveloperName`\n- object and field API names such as `Account` or `Account.AnnualRevenue`\n- `Assignee.Username` \u002F email for user-centric checks\n\nUse Salesforce record IDs only when:\n- the underlying object model requires `ParentId` or `SetupEntityId`, or\n- you are drilling into records returned by a prior read-only query in the same investigation\n\n### 4. Render findings clearly\nUse:\n- ASCII tree or table output for terminal work\n- Mermaid only when documentation benefit is clear\n- concise summaries of which permission source grants access\n\n### 5. Hand off creation or deployment work\nUse:\n- [sf-metadata](..\u002Fsf-metadata\u002FSKILL.md) for richer metadata generation\n- [sf-deploy](..\u002Fsf-deploy\u002FSKILL.md) for deployment\n\n---\n\n## High-Signal Rules\n\n- distinguish direct Permission Set grants from grants via Permission Set Groups\n- prefer `Name` \u002F `DeveloperName` \u002F API names over org-specific record IDs for first-pass investigation queries\n- be explicit about whether access is object-level, field-level, class-level, flow-level, or custom-permission-based\n- use Tooling API where required for setup entities and advanced visibility questions\n- for agent access questions, verify exact agent-name matching in permission metadata\n- when a follow-up child query requires `ParentId` or `SetupEntityId`, resolve the ID from a prior result instead of starting with copied IDs\n\n---\n\n## Output Format\n\nWhen finishing, report in this order:\n1. **What was analyzed**\n2. **Org \u002F subject scope**\n3. **Which permissions grant access**\n4. **Whether access is direct or inherited**\n5. **Recommended follow-up**\n\nSuggested shape:\n\n```text\nPermission analysis: \u003Chierarchy \u002F detect \u002F user \u002F export>\nScope: \u003Corg, user, permission target>\nFindings: \u003Cpermsets \u002F groups \u002F access level>\nSource: \u003Cdirect assignment or via group>\nNext step: \u003Cexport, generate metadata, or deploy changes>\n```\n\n---\n\n## Cross-Skill Integration\n\n| Need | Delegate to | Reason |\n|---|---|---|\n| generate or modify permission metadata | [sf-metadata](..\u002Fsf-metadata\u002FSKILL.md) | metadata authoring |\n| deploy permission changes | [sf-deploy](..\u002Fsf-deploy\u002FSKILL.md) | rollout |\n| identify Apex classes needing grants | [sf-apex](..\u002Fsf-apex\u002FSKILL.md) | implementation context |\n| bulk user assignment analysis | [sf-data](..\u002Fsf-data\u002FSKILL.md) | larger data operations |\n\n---\n\n## Reference Map\n\n### Start here\n- [references\u002Fpermission-model.md](references\u002Fpermission-model.md)\n- [references\u002Fsoql-reference.md](references\u002Fsoql-reference.md)\n- [references\u002Fworkflow-examples.md](references\u002Fworkflow-examples.md)\n\n### Specialized analysis\n- [references\u002Fagent-access-guide.md](references\u002Fagent-access-guide.md)\n- [references\u002Fusage-examples.md](references\u002Fusage-examples.md)\n\n---\n\n## Score Guide\n\n| Score | Meaning |\n|---|---|\n| 90+ | strong permission analysis with clear access sourcing |\n| 75–89 | useful audit with minor gaps |\n| 60–74 | partial visibility only |\n| \u003C 60 | insufficient evidence; expand analysis |\n","# sf-permissions\n\nUse this skill when the user needs **permission analysis and access auditing**: Permission Set \u002F Permission Set Group hierarchy views, “who has access to X?” investigations, user-permission analysis, or permission-set metadata review.\n\n## When This Skill Owns the Task\n\nUse `sf-permissions` when the work involves:\n- permission set \u002F permission set group analysis\n- user access investigation\n- finding which permission grants object \u002F field \u002F Apex \u002F flow \u002F tab \u002F custom-permission access\n- auditing or exporting permission configuration\n- reviewing permission metadata impacts\n\nDelegate elsewhere when the user is:\n- creating new metadata definitions → [sf-metadata](..\u002Fsf-metadata\u002FSKILL.md)\n- deploying permission sets → [sf-deploy](..\u002Fsf-deploy\u002FSKILL.md)\n- analyzing Apex-managed sharing logic → [sf-apex](..\u002Fsf-apex\u002FSKILL.md)\n\n---\n\n## Required Context to Gather First\n\nAsk for or infer:\n- target org alias\n- whether the question is about an object, field, Apex class, flow, tab, custom permission, or specific user\n- whether the goal is hierarchy visualization, access detection, export, or metadata generation\n- whether the output should be terminal-focused or documentation-friendly\n\n---\n\n## Recommended Workflow\n\n### 1. Classify the request\n| Request shape | Default capability |\n|---|---|\n| “who has access to X?” | permission detector |\n| “what does this user have?” | user analyzer |\n| “show me the hierarchy” | hierarchy viewer |\n| “export this permset” | exporter |\n| “generate metadata from analysis” | generator or handoff |\n\n### 2. Connect to the correct org\nVerify `sf` auth before running permission analysis.\n\n### 3. Use the narrowest useful query\nPrefer focused analysis over broad org-wide scans unless the user explicitly wants a full audit.\n\nWhen choosing identifiers, prefer stable metadata names first:\n- `PermissionSet.Name`\n- `PermissionSetGroup.DeveloperName`\n- `CustomPermission.DeveloperName`\n- object and field API names such as `Account` or `Account.AnnualRevenue`\n- `Assignee.Username` \u002F email for user-centric checks\n\nUse Salesforce record IDs only when:\n- the underlying object model requires `ParentId` or `SetupEntityId`, or\n- you are drilling into records returned by a prior read-only query in the same investigation\n\n### 4. Render findings clearly\nUse:\n- ASCII tree or table output for terminal work\n- Mermaid only when documentation benefit is clear\n- concise summaries of which permission source grants access\n\n### 5. Hand off creation or deployment work\nUse:\n- [sf-metadata](..\u002Fsf-metadata\u002FSKILL.md) for richer metadata generation\n- [sf-deploy](..\u002Fsf-deploy\u002FSKILL.md) for deployment\n\n---\n\n## High-Signal Rules\n\n- distinguish direct Permission Set grants from grants via Permission Set Groups\n- prefer `Name` \u002F `DeveloperName` \u002F API names over org-specific record IDs for first-pass investigation queries\n- be explicit about whether access is object-level, field-level, class-level, flow-level, or custom-permission-based\n- use Tooling API where required for setup entities and advanced visibility questions\n- for agent access questions, verify exact agent-name matching in permission metadata\n- when a follow-up child query requires `ParentId` or `SetupEntityId`, resolve the ID from a prior result instead of starting with copied IDs\n\n---\n\n## Output Format\n\nWhen finishing, report in this order:\n1. **What was analyzed**\n2. **Org \u002F subject scope**\n3. **Which permissions grant access**\n4. **Whether access is direct or inherited**\n5. **Recommended follow-up**\n\nSuggested shape:\n\n```text\nPermission analysis: \u003Chierarchy \u002F detect \u002F user \u002F export>\nScope: \u003Corg, user, permission target>\nFindings: \u003Cpermsets \u002F groups \u002F access level>\nSource: \u003Cdirect assignment or via group>\nNext step: \u003Cexport, generate metadata, or deploy changes>\n```\n\n---\n\n## Cross-Skill Integration\n\n| Need | Delegate to | Reason |\n|---|---|---|\n| generate or modify permission metadata | [sf-metadata](..\u002Fsf-metadata\u002FSKILL.md) | metadata authoring |\n| deploy permission changes | [sf-deploy](..\u002Fsf-deploy\u002FSKILL.md) | rollout |\n| identify Apex classes needing grants | [sf-apex](..\u002Fsf-apex\u002FSKILL.md) | implementation context |\n| bulk user assignment analysis | [sf-data](..\u002Fsf-data\u002FSKILL.md) | larger data operations |\n\n---\n\n## Reference Map\n\n### Start here\n- [references\u002Fpermission-model.md](references\u002Fpermission-model.md)\n- [references\u002Fsoql-reference.md](references\u002Fsoql-reference.md)\n- [references\u002Fworkflow-examples.md](references\u002Fworkflow-examples.md)\n\n### Specialized analysis\n- [references\u002Fagent-access-guide.md](references\u002Fagent-access-guide.md)\n- [references\u002Fusage-examples.md](references\u002Fusage-examples.md)\n\n---\n\n## Score Guide\n\n| Score | Meaning |\n|---|---|\n| 90+ | strong permission analysis with clear access sourcing |\n| 75–89 | useful audit with minor gaps |\n| 60–74 | partial visibility only |\n| \u003C 60 | insufficient evidence; expand analysis |\n",{"name":5,"license":15,"metadata":24,"description":28},{"author":25,"version":26,"inspiration":27},"Jag Valaiyapathy","1.1.0","PSLab by Oumaima Arbani (github.com\u002FOumArbani\u002FPSLab)","Permission Set analysis, hierarchy viewer, and access auditing. TRIGGER when: user asks \"who has access to X?\", analyzes permission sets\u002Fgroups, or touches .permissionset-meta.xml \u002F .permissionsetgroup-meta.xml files. DO NOT TRIGGER when: creating new metadata (use sf-metadata), deploying permission sets (use sf-deploy), or Apex sharing logic (use sf-apex).\n","main","8859218955d9504cd18b59e7892100718039d3b4","data\u002Fskills\u002Fjaganpro-sf-skills\u002Fsf-permissions\u002Fskills\u002Fsf-permissions",1,"https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper","https:\u002F\u002Fgithub.com\u002Fom-scogo","SDE-1 @ Scogo ","2026-07-18 12:22:46",{"source":8,"skillName":5,"commands":38,"prompt":48,"zipAvailable":49},[39,42,45],{"tool":40,"command":41},"npx","npx skills add om-scogo\u002Fskillsh-scraper --skill sf-permissions",{"tool":43,"command":44},"bunx","bunx skills add om-scogo\u002Fskillsh-scraper --skill sf-permissions",{"tool":46,"command":47},"pnpm","pnpm dlx skills add om-scogo\u002Fskillsh-scraper --skill sf-permissions","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fjaganpro-sf-skills\u002Fsf-permissions\u002Fskills\u002Fsf-permissions\u002FSKILL.md",true,[],[52,59,64,71,76,83],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":19},"01M7D6MC9FAAEV4CMNYX8W7JTG","arxiv-search","Search arXiv physics, math, and computer science preprints using natural language queries. Powered by Valyu semantic search.","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fyorkeccak-scientific-skills\u002Farxiv-search\u002Fskills\u002Farxiv-search\u002FSKILL.md",[],[],{"skillNo":60,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":19},"01M7D6M85CKKN87TA98VCQV4H7","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fyorkeccak-scientific-skills\u002Farxiv-search\u002FSkill.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":19},"01M7D4ZTCS4DR3CE4JY06X84T2","working-with-legacy-code","Safely change and test untested codebases using Feathers' \"Working Effectively with Legacy Code\". Use when the user mentions \"legacy code\", \"no tests\", \"untested codebase\", \"how do I test this\", \"seams\", \"characterization tests\", \"golden master\", \"sprout method\", \"afraid to change this code\", \"monster method\", \"dependency breaking\", or \"inherited a messy codebase\". Also trigger when changing code without tests safely, getting a class under test when constructors, statics, or singletons block it, adding features to tangled modules, or planning incremental test coverage for an old codebase. Covers the legacy-code change algorithm, seams, characterization tests, sprout\u002Fwrap, and dependency-breaking techniques. For refactoring code that already has tests, see refactoring-patterns. For day-to-day code quality, see clean-code.","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fwondelai-skills\u002Fworking-with-legacy-code\u002Fworking-with-legacy-code\u002FSKILL.md",[],[],{"skillNo":72,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M7D4ZHZKJD2RSNGAF63V14P4","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fwondelai-skills\u002Fworking-with-legacy-code\u002FSkill.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M7D4ZB4CJBFW5JE67CPH2QRV","web-typography","Select, pair, and implement typefaces for web projects. Use when the user mentions \"font pairing\", \"which typeface\", \"line height\", \"responsive typography\", \"web font loading\", \"type hierarchy\", \"variable fonts\", \"FOUT\u002FFOIT\", \"typographic scale\", or \"the text is hard to read\". Also trigger when choosing between system fonts and web fonts, optimizing font-loading performance, or designing readable long-form content. Covers readability evaluation, CSS implementation, and performance optimization. For overall UI design systems, see refactoring-ui. For dramatic typographic experiences, see top-design.","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fwondelai-skills\u002Fweb-typography\u002Fweb-typography\u002FSKILL.md",[],[],{"skillNo":84,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M7D4Z4MVYVY3NMJ18BNV6WNA","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fwondelai-skills\u002Fweb-typography\u002FSkill.md",[],[]]