Revenue Cloud Skills Library

Skills, implementation patterns, and tools from Revenue Cloud Base Foundations.

Give your coding agent Revenue Cloud knowledge, implementation patterns, and tools to build, configure, and maintain Salesforce environments. The library brings together skills grounded in documentation, metadata, and code, supported by deployment automation and example datasets.

Browse the skills · Explore the documentation · Build an environment

This branch: Release 264 (Winter '27), API v68.0. See branch information before choosing an org or release.

Start with a skill

1. Clone or download this repository and open it in your coding agent’s workspace.
2. Give the agent a task. Start with the prompt below or pick a capability from the table.
3. Follow the selected skill. It links to the relevant references, tools, and verification steps.

Read AGENTS.md and the skill catalog in .cursor/skills/README.md.
Choose the relevant skill, then use the repository's references to explain
how products, pricing, and usage grants relate. Cite the files you use.

The skills are Markdown guides that any coding agent with repository-file access can read. They live under .cursor/skills/ for historical reasons. Use the prompt above with Cursor, Claude Code, Codex, GitHub Copilot, or another file-capable agent; native skill discovery varies by tool (setup and verified clients). AGENTS.md provides the shared project instructions and safety rules.

You can explore the checked-in guides and references without connecting a Salesforce org. Running scripts or changing an org requires the tools and access described by the selected skill. Keep the full repository available: skills reference files outside their own folders.

For more workflows, including decision tables, ramped quotes, renewal assets, and data loading, see the complete skill catalog.

What this repository provides

Revenue Cloud Base Foundations combines the skills library with automation for Revenue Cloud, formerly Revenue Lifecycle Management (RLM):

• Knowledge foundation: checked-in Salesforce documentation, API references, data-model diagrams, metadata, and code to ground the agent’s work.
• Skills and tools: task guides, scripts, and validation tools for building, configuring, troubleshooting, and maintaining environments.
• Implementation patterns: QuantumBit example datasets, constraint models, context mappings, metadata, and UX templates to inspect and adapt to your needs.

Examples and tools cover product catalogs, pricing, billing, tax, contract lifecycle management (CLM), rating, and more. Browse the data plans and skill catalog.

Skills guide the agent; the repository’s tools execute the work. The main CumulusCI flow, prepare_rlm_org, coordinates deployment, data loading, configuration, activation, and checks. Feature flags select the capabilities to include. See the build-process guide for sequencing and dependencies, or the repository map to locate the source files.

Build and configure an org

Choose the setup path that fits your workstation:

Building requires a Salesforce org with Revenue Cloud licenses and appropriate metadata-deployment permissions; scratch-org creation also requires a Dev Hub. The data-loading toolchain requires SFDMU v5.6.4 or later. See the complete prerequisites.

Once your tools and org connection are ready, use the org quick start. For repeatable builds with progress reporting and resume support, use the build harness.

macOS Environment Setup

Follow the local installation guide for the step-by-step macOS setup referenced by the contributing guide.

Documentation

Contributing

Contributions go through a fork and a pull request — see CONTRIBUTING.md for the full workflow: environment setup, the validation commands to run before pushing, commit/PR conventions, and how review rounds are handled.

When contributing to this project:

1. Follow the existing code structure and patterns
2. Document custom tasks in cumulusci.yml and create example documentation
3. Test changes with appropriate scratch org configurations
4. Update this README if adding new prerequisites or workflows
5. Add detailed READMEs for new data plans
6. Register new tasks and flows in cumulusci.yml

Participation is governed by the Code of Conduct. Report security vulnerabilities privately through the process in SECURITY.md — never through a public GitHub issue.

Branch Information

• main: Salesforce Release 264 (Winter '27, API v68.0) — the current published line, promoted from the 264 branch. 264 is preview / pre-GA (no v68.0 GA certification yet); a live 264 org remains ground truth.
• 264: The Release 264 development branch, in sync with main following the promotion.
• 262: Salesforce Release 262 (Summer '26, API v67.0) — active maintenance branch for remaining 262 patches through 262 GA; at the final 262 release tip.
• release/262: Frozen Release 262 GA reference, snapshotted from the pre-cutover main at 49a494de.
• release/260: Salesforce Release 260 (Spring '26, GA) — prior GA reference.
• Other branches exist for different release scenarios and preview features.

main now carries the 264 line; the 262 branch receives any remaining Release 262 patches until 262 GA. This promotion mirrors how 262 was promoted into main via PR #208.

Project Governance & Support

• License — Apache License, Version 2.0
• Code of Conduct — Salesforce Open Source Community Code of Conduct
• Contributing — fork, branch, validate, pull request
• Security — report vulnerabilities privately, never through a public issue
• Review Guide — how pull requests are reviewed in this repository

For questions or problems, open an issue or a pull request in this repository.

License

This project is licensed under the Apache License, Version 2.0 — see LICENSE.txt for the full text.

Copyright (c) 2026 Salesforce, Inc.
All rights reserved.