qb-demo-script

Generate per-release QuantumBit Revenue Cloud demo walkthrough Markdown for Slack canvases.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Sales engineers and partners need a canonical, per-release Revenue Cloud demo walkthrough, but hand-editing a Slack canvas every Salesforce release is slow and error-prone. This Skill mechanically regenerates the QuantumBit demo script Markdown from grounded scenario references, feature indexes, and Help articles so each release gets an accurate, consistent artifact. ## Core Features & Use Cases - Grounded content generation: Pulls accounts, products, SKUs, bundles, and constraint models strictly from the canonical qb-scenario-reference.md, never inventing demo data. - Release-aware updates: Reads the target release's feature-index.md and Help corpus to annotate new, preview, and deprecated features in talk tracks. - Two modes: Full regeneration for release rollovers (260 to 262) or refresh mode that updates only sections affected by a feature-index delta, backing up the prior file first. - Use Case: When Salesforce release 264 ships, run the skill to produce docs/enablement/264/qb-demo-script.md with updated setup steps, known-bug skeletons, persona blocks, and click-path tables ready for SME review and Slack canvas publishing. ## Quick Start Ask the agent to generate the QuantumBit demo script for release 264 using the scenario reference and feature index in this repository.

Frequently Asked Questions about qb-demo-script

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

FAQPage Schema
How do I generate a Salesforce Revenue Cloud demo script for a new release?

Run the skill with the target release number (e.g., 264). It reads the release's feature-index.md, Help article corpus, and cumulusci.yml feature flags, then writes a complete demo script to docs/enablement/{release}/qb-demo-script.md following the canonical section order.

What is the difference between regenerate and refresh mode?

Regenerate produces the full canvas Markdown from scratch or a prior-release template, used for release rollovers like 262 to 264. Refresh updates only sections affected by a feature-index delta for in-release patches, backing up the prior file to a timestamped .bak first.

Can the demo script include products or personas not in the scenario reference?

No. All accounts, products, SKUs, bundles, and constraint models must come from docs/enablement/master/qb-scenario-reference.md. Personas come from the prior-release canvas source; if that source is absent, the Demo Personas section is omitted rather than fabricated.

Does the skill publish directly to a Slack canvas?

No. The skill outputs a Markdown file with image-marker placeholders only. Publishing to Slack (canvas API calls, image upload, and marker substitution with real Slack file IDs) is a separate step requiring human review before release.

What inputs are required to run the demo script generator?

Required inputs are the qb-scenario-reference.md, the target release's feature-index.md, the Help portal article corpus, and the cumulusci.yml project.custom feature flags. The prior-release canvas source and PMOS capability roadmap are optional.