What problem does it solve? Salesforce Revenue Cloud Context Definitions are the canonical data layer that pricing, expression sets, the configurator, DocGen, and billing bind to at runtime, but authoring, extending, activating, and debugging them involves a confusing split between Connect API and SObject REST endpoints, silent failure modes, and pilot-gated runtime APIs. This Skill gives an AI agent the routing rules, gotchas, helper scripts, and reference docs to perform those operations correctly. ## Core Features & Use Cases - Design-time authoring and lifecycle: Extend standard contexts, apply additive attribute/tag/mapping plans, validate plans offline, diff definitions across orgs, and deploy tracked contextDefinitions metadata via CCI tasks. - Runtime instance lifecycle: Build hydration payloads, hydrate instances from records, query values by tag, and persist attribute values back to mapped SObjects, with guidance on request-scoped contextIds and the Apex/Flow path for GA orgs. - Inspection and debugging: Describe, trace, diff, and export live definitions; diagnose blocked deactivations, phantom hydration writes, FLS-hidden bindings, and silently destructive PATCH behavior. - Use Case: You need to surface a new custom field to a pricing procedure. The Skill routes you to add an attribute plus tag plus mapping on the extended Sales Transaction context, lint the plan offline, dry-run it against the org, and verify with describe_context.py. ## Quick Start Ask the agent to inspect the RLM_SalesTransactionContext definition on your org and trace how a specific Quote field maps to a context tag using the helper scripts.
