platform-agentexchange-partner-offers-configure

de forcedotcom

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).

Resumen

SKILL.mdLeída en abb06a4

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

Query the current preference value by running:
```
 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).
Resolve the org's package directory to determine where to write metadata. Run this and use its output as <packageDir>:
```
 jq -r '.packageDirectories[0].path // "force-app/main/default"' sfdx-project.json
```

Phase 2 — Apply the preference

Write the TransactableMarketplacePrivateOfferSettings metadata file — load assets/org-pref-template.md for the exact XML structure, then write the file at:
```
 <packageDir>/settings/TransactableMarketplacePrivateOffer.settings
```
Set <enableTransactableMarketplaceReceivePartnerOffers>true</enableTransactableMarketplaceReceivePartnerOffers> (or false if disabling).
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
```
 sf project deploy start --metadata TransactableMarketplacePrivateOfferSettings --target-org <alias>
```

Phase 3 — Verify

Confirm the change by re-running the Tooling API query from step 1 and verifying the Value column matches the desired state.
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:

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

Archivos 3 archivos

Instálala a mano

Deska ejecuta esto por ti, para cada agente que elijas. Para ejecutarlo tú en una terminal:

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

Más de forcedotcom

platform-apex-generate forcedotcomPrimary Apex authoring skill for class generation, refactoring, and review. ALWAYS ACTIVATE when the user mentions Apex, .cls, triggers, or asks to create/refactor a class (service, selector, domain, batch, queueable, schedulable, invocable, DTO, utility, interface, abstract, exception, REST resource). Use this skill for requests involving SObject CRUD, mapping collections, fetching related records, scheduled jobs, batch jobs, trigger design, @AuraEnabled controllers, @RestResource endpoints, custom REST APIs, or code review of existing Apex.6,700 instalaciones en skills.sh0
platform-apex-test-generate forcedotcomUse to generate and validate Apex test classes with TestDataFactory patterns, bulk testing (251+ records), mocking, assertions, and disciplined test-fix loops. Use when creating Apex test classes (for triggers, services, controllers, batch jobs, queueables, and callouts), improving coverage, debugging or fixing failing Apex tests, or running test/coverage analysis. Triggers on *Test.cls files, sf apex run test, coverage reports. Do NOT trigger for production Apex (use platform-apex-generate) or Jest/LWC tests.6,600 instalaciones en skills.sh0
platform-apex-test-run forcedotcomApex test execution, coverage analysis, and test-fix loops with 120-point scoring. Use when the user runs Apex tests, checks code coverage, fixes failing tests, or touches *Test.cls / *_Test.cls files. DO NOT TRIGGER when writing Apex production code (use platform-apex-generate), Agentforce agent testing (use agentforce-test), or Jest/LWC tests (use experience-lwc-generate).6,500 instalaciones en skills.sh0
platform-apex-logs-debug forcedotcomSalesforce debug log analysis and troubleshooting with 100-point scoring. TRIGGER when: user analyzes debug logs, hits governor limits, reads stack traces, or touches .log files from Salesforce orgs. DO NOT TRIGGER when: running Apex tests (use platform-apex-test-run), generating or fixing Apex code (use platform-apex-generate), or Agentforce session tracing (use agentforce-observe).6,400 instalaciones en skills.sh0
platform-metadata-deploy forcedotcomSalesforce DevOps automation using sf CLI v2. TRIGGER when: user deploys metadata, creates/manages scratch orgs or sandboxes, sets up CI/CD pipelines, or troubleshoots deployment errors with sf project deploy. DO NOT TRIGGER when: writing Apex code (use platform-apex-generate), building LWC components (use experience-lwc-generate), creating metadata definitions (use platform-custom-object-generate or platform-custom-field-generate), or querying org data (use platform-data-manage).6,300 instalaciones en skills.sh0

Todas las skills de forcedotcom