← Search

Sharing rules generator
Developer tools 🧪 Install ran in our test sandbox · Nov 11, 2026 📌 Pinned version: commit e5164d9
Install test only, on the date shown. This does not guarantee the code is safe.
⚙ Needs: a Salesforce org with sharing rules to manage…

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

At a glance
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.

Version:

Quick answer

Sharing rules generator is a free skill from @forcedotcom for record-level access beyond org-wide defaults. It gets, creates, edits and deletes sharingCriteriaRules, sharingOwnerRules and sharingGuestRules metadata in four phases: retrieve the rules first, pick operation and rule type, execute, then write and verify. Strict rules apply: one sharingRules file per object, guest rules using guestUser, deletion requiring a destructive deployment.

⌁

Install

Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 11, 2026📌 Pinned version: commit e5164d9

Step 0 — before installing anything: read this install prompt, summarize in a few lines what this build does and what installing it involves, then ask me to confirm before you proceed. 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://raw.githubusercontent.com/forcedotcom/sf-skills/e5164d94d7511c00fa02a5b8b60754b2361e178f/plugins/builder/salesforce-development/skills/platform-sharing-rules-generate/SKILL.md Pinned version: install the code at commit e5164d94d7511c00fa02a5b8b60754b2361e178f exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder 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.

🔒 Security, provenance and what this touches
🧭 What this touches
Based on the install prompt we scanned, this skill does not run commands, make third-party network calls, install packages, write files, or ask for API keys.
Install prompt analysis · 2026-10-13
🔒 Security and provenance
📌 Pinned version: commit e5164d9 · 2026-10-13
🧪 Install ran in our test sandbox · Nov 11, 2026
👁 Observed during the install test · Nov 11, 2026 : no network contact
🔎 Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Wanna be extra careful?

The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?

How to check a skill before installing →

✓

Verification certificate

Dated facts about what was checked for this listing, and how. This is not a safety certification.

Pinned version
e5164d9 · 2026-10-13
Sandbox install test
Install ran in our test sandbox · Nov 11, 2026
Creator identity
Not verified
Fingerprint watch
Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
Install prompt analysis
2026-10-13 : No commands, network calls, packages, file writes or API keys detected.

Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify

?

Questions

How do I install a skill?

Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill 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 skill before installing it.