What problem does it solve? Working with Salesforce Revenue Cloud (RLM) requires knowing which of its 263 platform objects, 4,252 fields, and 674 relationships to use, and release-to-release schema changes (like the 262 to 264 delta) silently break queries and integrations built on outdated assumptions. ## Core Features & Use Cases - Schema Lookup: Query object fields, relationships, and domain membership on demand with the query_erd.py script, including relationship paths between any two objects. - Per-Domain References: Load detailed field and relationship documentation for PCM, Pricing, Rates, Configurator, Transactions, DRO, Usage, Billing, and Approvals domains. - Release Delta Tracking: Review verified 260 to 262 and 262 to 264 schema diffs, including removed fields and their replacement binding sites such as ProductUsageResourcePolicy. - Use Case: When writing a SOQL query to resolve overage chargeability for a usage entitlement, use this Skill to learn that TransactionUsageEntitlement.ChargeForOverage was removed in 264 and the value now comes from UsageOveragePolicy via ProductUsageResourcePolicy. ## Quick Start Ask the agent to explain how products, pricing, and usage grants relate in Revenue Cloud, citing the domain reference files it uses.