revenue-cloud-docs

Grounds Revenue Cloud product claims against captured Salesforce Help and Developer Guide snapshots.

33|12|Updated Sep 24, 2024
One-click install
npx skills add https://github.com/bgaldino/rlm-base-dev --skill revenue-cloud-docs-bgaldino
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: revenue-cloud-docs
Source: https://github.com/bgaldino/rlm-base-dev/tree/main/.cursor/skills/revenue-cloud-docs
Command: npx skills add https://github.com/bgaldino/rlm-base-dev --skill revenue-cloud-docs-bgaldino

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI agents and writers often assert how Salesforce Revenue Cloud features work from memory, which risks stale or wrong claims after renames and release changes. This Skill provides grep-friendly, per-article markdown snapshots of the Salesforce Help portal and Developer Guide so every product claim can be verified against the current release's documentation before being written or accepted. ## Core Features & Use Cases - Claim grounding: Verify object names, field labels, feature behavior, and terminology for Billing, Pricing, Quoting, Orders, Contracts, Assets, Usage, and DRO against captured Help articles at docs/salesforce/{release}/help/. - Developer reference: Ground object/field API names, Business APIs, Apex, Metadata/Tooling types, and Constraint Modeling Language (CML) syntax against the atlas Developer Guide snapshots at docs/salesforce/{release}/dev-guide/ and dev-guide-industries/. - Snapshot refresh: Re-capture Help and Dev Guide content for new Salesforce releases via the snapshot_{area}help{release} and snapshot_dev_guide CCI tasks, with discovery validation and cross-release diffs. - Use Case: Before authoring a Trailhead module passage claiming how Billing Arrangements work, grep the snapshot for the term, read the matching article, and cite the article ID from its frontmatter in the Resources section. ## Quick Start Ask the agent to verify a Revenue Cloud feature claim by grepping the Help snapshot under docs/salesforce/264/help/articles/ and reading the matching article before writing.

Frequently Asked Questions about revenue-cloud-docs

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify a Salesforce Revenue Cloud feature claim before writing documentation?

Grep the Help snapshot under docs/salesforce/{release}/help/articles/ for the feature's key terms, then read the matching article for full context. Confirm your claim matches the article's wording and cite the article ID from its YAML frontmatter rather than guessing a URL.

What is the difference between the Help snapshot and the Developer Guide snapshot?

The Help snapshot covers how admins and sellers use features, while the Developer Guide snapshot covers objects, fields, Business APIs, Apex, and CML syntax that developers build against. Ground admin claims in docs/salesforce/{release}/help/ and developer claims in docs/salesforce/{release}/dev-guide/.

How do I refresh the Salesforce Help snapshot for a new release?

Run the matching CCI task, for example cci task run snapshot_billing_help_264 -o mode discover to list articles, then run it without the mode override to capture. Validate the manifest counts and commit the resulting markdown files.

Can I use the snapshot to look up object schemas and data model fields?

Not reliably for thin Data Model articles under about 300 bytes, which are image-based ERDs where only the headline sentence is captured. Use the revenue-cloud-data-model skill for object schemas instead.

Why does a discovery run report zero articles for a Help area?

A zero-article discovery raises an error and means either the root article ID is wrong or the ID prefix no longer matches the portal's sidebar. Read the Discovered line in the task output: zero total before prefix filter indicates a bad root, while nonzero total with zero kept indicates a prefix mismatch.

Where do I find documentation for Agentforce Revenue Management subagents?

Grep across all captured snapshots, not just the ind.rev_agent_* prefix. The dedicated agents snapshot holds topic-reference articles, while setup steps and use cases live under each functional area's prefix such as ind.qocal_agentforce_* or ind.billing_agentforce_*.