Skip to main content
skill CX Codex

platform-agentexchange-partner-offers-configure — Claude Code skill

platform-agentexchange-partner-offers-configure turns partner offer reception from the Transactable Marketplace on or off in a Salesforce org by setting enableTransactableMarketplaceReceivePartnerOffers.

Apache-2.0 5,000 installs ★ 1,183 updated 2026-10-23

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add forcedotcom/sf-skills --skill platform-agentexchange-partner-offers-configure -a claude-code
Open on GitHub

What platform-agentexchange-partner-offers-configure does

The skill controls the enableTransactableMarketplaceReceivePartnerOffers preference via Metadata API (TransactableMarketplacePrivateOfferSettings). It queries the current value through the Tooling API, writes an XML settings file to <packageDir>/settings/TransactableMarketplacePrivateOffer.settings, and deploys it to the target org with sf project deploy start.

It checks the existing state before making changes and asks for confirmation before deploying — rolling back a deploy to the wrong org is not straightforward. Requires Salesforce CLI sf ≥2.0.0, jq ≥1.6.0, and API version 67.0 or later — earlier versions do not expose the TransactableMarketplacePrivateOfferSettings type.

The preference is not visible in the Setup UI; the Tooling API query is the only way to verify it. If the deploy succeeds but the value does not change, another TransactableMarketplacePrivateOffer.settings file in the project may override it.

What it helps with

  • enable partner offer reception from the Transactable Marketplace
  • disable enableTransactableMarketplaceReceivePartnerOffers in an org
  • deploy TransactableMarketplacePrivateOfferSettings via Metadata API
  • check the current value of TransactableMarketplaceReceivePartnerOffers through Tooling API

Example prompts for the agent

  • Enable partner offers in the dev-sandbox org
  • Turn off enableTransactableMarketplaceReceivePartnerOffers for staging
  • Check whether TransactableMarketplaceReceivePartnerOffers is enabled in the current org

How to install platform-agentexchange-partner-offers-configure

1Skills CLI (Vercel)

npx skills add forcedotcom/sf-skills --skill platform-agentexchange-partner-offers-configure -a claude-code

2Manually: put the files in place

~/.claude/skills/platform-agentexchange-partner-offers-configure/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/platform-agentexchange-partner-offers-configure/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about platform-agentexchange-partner-offers-configure

How to install platform-agentexchange-partner-offers-configure in Claude Code?

Run npx skills add forcedotcom/sf-skills --skill platform-agentexchange-partner-offers-configure -a claude-code, and the skill will be written to ~/.claude/skills/platform-agentexchange-partner-offers-configure/SKILL.md.

What does platform-agentexchange-partner-offers-configure do?

It enables or disables the enableTransactableMarketplaceReceivePartnerOffers preference via Metadata API, which controls whether a Salesforce org receives partner offers from the Transactable Marketplace.

What does platform-agentexchange-partner-offers-configure require?

Salesforce CLI sf version 2.0.0 or later, jq 1.6.0 or later, and Salesforce API version 67.0 or higher — earlier API versions do not expose the TransactableMarketplacePrivateOfferSettings type.

Source text

SKILL.md · Apache-2.0
---
name: platform-agentexchange-partner-offers-configure
description: "Enable or disable the org preference that controls whether a Salesforce org can receive partner offers from the Transactable Marketplace. Use this skill when the user wants to turn partner offer reception on or off for an org. TRIGGER when: user asks to enable or disable partner offers, configure TransactableMarketplaceReceivePartnerOffers, configure enableTransactableMarketplaceReceivePartnerOffers, set up marketplace partner offer reception, toggle the TM partner offers setting, edit a TransactableMarketplacePrivateOffer.settings file, or configure org preferences related to transactable marketplace. DO NOT TRIGGER when: user needs to create or manage the partner offer records themselves, configure marketplace listing settings, or work with SfdcPartnerOffer objects (use platform-metadata-deploy or platform-apex-generate instead)."
metadata:
  version: "1.0"
  domains: ["Platform"]
  minApiVersion: "67.0"
  relatedSkills:
    - "platform-apex-generate"
    - "platform-metadata-deploy"
  cliTools:
    - tool: ["sf"]
      semver: ">=2.0.0"
    - tool: ["jq"]
      semver: ">=1.6.0"
---

# Enabling Transactable Marketplace Receive Partner Offers Org Preference

This skill configures the `enableTransactableMarketplaceReceivePartnerOffers` org preference via the `TransactableMarketplacePrivateOfferSettings` Metadata API type, which controls whether a Salesforce org is eligible to receive partner offers through the Transactable Marketplace. It is required for subscriber orgs that participate in the TM partner offer flow.

## Scope

- **In scope**: Reading the current value of the pref, enabling or disabling it via Metadata API (`TransactableMarketplacePrivateOfferSettings`), and verifying the change took effect.
- **Out of scope**: Creating or managing partner offer records, configuring marketplace listings, or any Apex/trigger changes related to offer processing.

---

## Required Inputs

- **Target org alias or username**: The org where the pref should be set. Ask if not provided.
- **Desired state**: `true` (enable) or `false` (disable). Default: `true`.

---

## Workflow

### Phase 1 — Check current state

1. **Query the current preference value** by running:
   ```bash
   sf data query -q "SELECT Preference, Value FROM OrgPreference WHERE Preference = 'TransactableMarketplaceReceivePartnerOffers'" --target-org <alias> --use-tooling-api
   ```
   If the record exists and `Value = true`, the pref is already enabled — confirm with the user before proceeding.
   If the query returns no rows, the pref is not yet set (defaults to `false`).

2. **Resolve the org's package directory** to determine where to write metadata. Run this and use its output as `<packageDir>`:
   ```bash
   jq -r '.packageDirectories[0].path // "force-app/main/default"' sfdx-project.json
   ```

### Phase 2 — Apply the preference

3. **Write the TransactableMarketplacePrivateOfferSettings metadata file** — load `assets/org-pref-template.md` for the exact XML structure, then write the file at:
   ```text
   <packageDir>/settings/TransactableMarketplacePrivateOffer.settings
   ```
   Set `<enableTransactableMarketplaceReceivePartnerOffers>true</enableTransactableMarketplaceReceivePartnerOffers>` (or `false` if disabling).

4. **Deploy the metadata** to the target org. Before running the deploy, confirm with the user:
   - [ ] Confirmed the target org alias with the user (deploying to the wrong org is not easily reversible)
   - [ ] Confirmed the desired state (`true`/`false`) matches the user's intent
   ```bash
   sf project deploy start --metadata TransactableMarketplacePrivateOfferSettings --target-org <alias>
   ```

### Phase 3 — Verify

5. **Confirm the change** by re-running the Tooling API query from step 1 and verifying the `Value` column matches the desired state.

6. **Report to the user** — see Output Expectations below.

---

## Rules / Constraints

| Rule | Rationale |
|------|-----------|
| Always query the current value before writing metadata | Avoids unnecessary deploys and detects conflicting changes |
| Use `TransactableMarketplacePrivateOfferSettings` as the metadata type | This is the concrete type registered in the platform for this pref, not the generic `OrgPreferenceSettings` |
| The settings file must be named `TransactableMarketplacePrivateOffer.settings` | Metadata API requires the filename to match the settings node name |
| Do not hardcode `force-app/main/default/` | Always read `sfdx-project.json` for the actual package directory |
| Never deploy without confirming the org alias with the user | Deploying to the wrong org is not easily reversible |

---

## Gotchas

| Issue | Resolution |
|-------|------------|
| Tooling API query returns no rows | Pref is unset (defaults to `false`). Safe to create a new settings file. |
| Deploy fails with `INVALID_TYPE` | The metadata type name is `TransactableMarketplacePrivateOfferSettings` — check the `--metadata` flag value. |
| Deploy succeeds but value doesn't change | Another settings file in the project may be overriding this one. Search for other `TransactableMarketplacePrivateOffer.settings` files in the project. |
| `INSUFFICIENT_ACCESS_OR_READONLY` on deploy | User running the deploy must have the "Modify All Data" or org preference admin permission in the target org. |
| Pref not visible in UI | `enableTransactableMarketplaceReceivePartnerOffers` is not surfaced in Setup UI — the Tooling API query is the only way to verify it. |
| Available from API version 67.0+ only | The type is available from API v67.0 — deploying against an older API version will fail. |

---

## Output Expectations

After completing all phases, report:

```text
Org: <alias>
Preference: enableTransactableMarketplaceReceivePartnerOffers
Previous value: <true|false|unset>
New value: <true|false>
File written: <packageDir>/settings/TransactableMarketplacePrivateOffer.settings
Deploy status: Success
```

---

## Reference File Index

| File | When to read |
|------|-------------|
| `assets/org-pref-template.md` | Phase 2, step 3 — use as the exact XML structure for the settings file |
| `examples/org-preference-settings.xml` | To verify the generated file matches expected format |

© forcedotcom · Apache-2.0 · forcedotcom/sf-skills

Similar skills

All skills for DevOps and infrastructure →

From the same set232

The whole set →
experience-ui-bundle-site-generate experience-ui-bundle-site-generate generates Salesforce Digital Experience Site infrastructure for hosting React UI bundles. Useful when setting up thin site containers, guest access, and locale configs. CX Codex +1 5,100installs data360-schema-get data360-schema-get — a skill for Claude Code and other AI editors that retrieves schema definitions for Data Lake Objects (DLO) and Data Model Objects (DMO) from Salesforce Data Cloud via REST API. CX Codex +1 5,100installs dx-devops-test-failures-analyze dx-devops-test-failures-analyze explains Salesforce DevOps Center test failures and Code Analyzer violations in plain language. It pinpoints offending lines and can log tracked work items. CX Codex +1 5,100installs dx-code-analyzer-custom-rule-create dx-code-analyzer-custom-rule-create is a Claude Code skill that builds custom Salesforce Code Analyzer rules with Regex, PMD, and ESLint for project-specific pattern bans and metadata XML governance. CX Codex +1 5,000installs data360-code-extension-generate The data360-code-extension-generate Claude Code skill creates and develops Data 360 Code Extensions. It activates for PySpark scripts or functions, local testing, and deployment. CX Codex +1 5,000installs experience-cms-brand-apply experience-cms-brand-apply finds existing brands in Salesforce CMS, retrieves their guidelines, and uses them when generating content. Useful when output needs to follow a specific brand. CX Codex +1 5,000installs experience-ui-bundle-agentforce-client-generate experience-ui-bundle-agentforce-client-generate embeds the Agentforce Conversation Client in React and Angular UI Bundle apps: detects the framework, validates agentId, wires the component into a page. CX Codex +1 5,000installs dx-devops-test-suite-run dx-devops-test-suite-run triggers DevOps Center test suites on Salesforce pipeline stages and polls execution until finished. Useful for pre-promotion gates and re-running checks after code coverage fixes. CX Codex +1 5,000installs

Project sponsors

Companies that keep this analytics open