Transactable Marketplace partner-offers preference
Enable or disable the org preference that controls whether a Salesforce org can receive partner offers through the Transactable Marketplace
- What
- Enable or disable the org preference that controls whether a Salesforce org can receive partner offers through the Transactable Marketplace
- Cost
- Free
- Needs
- a Salesforce org on API v67.0+ (the metadata type is unavailable on older versions); the sf CLI (>=2.0.0) authenticated against the org; a user with "Modify All Data" or org-preference admin permission for the deploy step
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — @forcedotcom's focused playbook for the `enableTransactableMarketplaceReceivePartnerOffers` org preference: read the current value via a Tooling API `OrgPreference` query first, write the `TransactableMarketplacePrivateOffer.settings` metadata file (resolving the package directory from `sfdx-project.json`, never hardcoded), deploy it with `sf project deploy start --metadata TransactableMarketplacePrivateOfferSettings`, then re-query to verify — with a mandatory confirmation gate on both the target org alias and the desired state before any deploy, because deploying to the wrong org is not easily reversible. By @forcedotcom, listed here with credit to its creator. Honest caveats: narrow scope by design — it does NOT create or manage partner offer records, listings, or Apex logic (separate skills); available from API v67.0+ only; the deploy user needs "Modify All Data" or org-preference admin permission; the preference is not surfaced in Setup UI, the Tooling API query is the only way to verify it. 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 on API v67.0+ (the metadata type is unavailable on older versions); the sf CLI (>=2.0.0) authenticated against the org; a user with "Modify All Data" or org-preference admin permission for the deploy step Install "Transactable Marketplace partner-offers preference" for me. It teaches the agent @forcedotcom's three-phase workflow: check the current preference value with a Tooling API OrgPreference query; write the TransactableMarketplacePrivateOffer.settings metadata file at <packageDir>/settings/ (resolved from sfdx-project.json) and deploy it with `sf project deploy start --metadata TransactableMarketplacePrivateOfferSettings` — only after confirming the target org alias and desired state with the user; then verify by re-running the query and report previous value, new value, file written and deploy status. Repository: https://github.com/forcedotcom/sf-skills/blob/main/plugins/builder/dx-isv-partner/skills/platform-agentexchange-partner-offers-configure/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-agentexchange-partner-offers-configure". 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 target org alias and whether I want the preference true or false when invoking). 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.