Sharing rules generator
Get, create, edit or delete Salesforce sharing rules metadata — criteria-based, owner-based and guest-user rules — with per-type verification checklists
- What
- Get, create, edit or delete Salesforce sharing rules metadata — criteria-based, owner-based and guest-user rules — with per-type verification checklists
- Cost
- Free
- Needs
- a Salesforce org with sharing rules to manage (authenticate with `sf org login web --alias <alias>`); the sf CLI (>=2.0.0); a Salesforce DX project with sfdx-project.json; org on API v60.0+
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — @forcedotcom's sharing-rules generator for record-level access beyond org-wide defaults: get, create, edit and delete `sharingCriteriaRules`, `sharingOwnerRules` and `sharingGuestRules` metadata with a four-phase workflow — always retrieve the latest rules from the org first (never trust a stale local file), pick the operation and rule type, execute, then write and verify. Strict platform rules are encoded: one `.sharingRules-meta.xml` file per object, guest rules must use `<guestUser>` (never `<role>`/`<group>`), Account rules require `<accountSettings>`, `sharedTo`/`sharedFrom` cannot be edited in place (delete + create instead), owner rules only support editing `accessLevel`, and rule deletion requires a destructive deployment (a normal deploy is additive and will not remove the rule). Verification checklists per rule type included, with example case files. By @forcedotcom, listed here with credit to its creator. Honest caveats: requires the sf CLI and an org on API v60.0+; does NOT change org-wide defaults, create Experience Sites, or configure permission sets/profiles; deleting the last rule removes the file entirely; editing against a stale file can recreate deleted rules or overwrite concurrent changes. Apache-2.0 licensed. Skill Harbor never reviews the code, review it yourself before use. Discovered via skills.sh.
Version:
Install
Prerequisites: a Salesforce org with sharing rules to manage (authenticate with `sf org login web --alias <alias>`); the sf CLI (>=2.0.0); a Salesforce DX project with sfdx-project.json; org on API v60.0+ Install "Sharing rules generator" for me. It teaches the agent @forcedotcom's four-phase workflow to manage sharing rules metadata: discover (resolve the SFDX project path, always retrieve the latest <ObjectName>.sharingRules-meta.xml from the org first), determine the operation (get/create/edit/delete) and rule type (criteria/owner/guest), execute the matching branch with the per-type XML schema from references/rule-types.md, then write and verify with the checklists — delegating rule deletion to the destructive-deploy pattern with the correct metadata type. Repository: https://github.com/forcedotcom/sf-skills/blob/main/plugins/builder/salesforce-development/skills/platform-sharing-rules-generate/SKILL.md 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "platform-sharing-rules-generate". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. confirm the org alias and the target object API name, and tell the agent which operation and rule type I need). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.