salesforce-cpq
Use for Salesforce CPQ work — products, price rules, product rules, quote templates, advanced approvals, contracts/amendments/renewals. Migrating to Revenue Cloud — flag if relevant.
What this skill does
# salesforce-cpq Salesforce CPQ (formerly Steelbrick). Configure-Price-Quote. > **Migration note.** CPQ is being subsumed by **Revenue Cloud**. New builds should evaluate Revenue Cloud first. Existing CPQ orgs continue to work; this skill covers both. ## Surfaces - **Products** — standalone, options, bundles - **Product features / options** — bundle structure - **Price rules** — adjust prices based on conditions - **Product rules** — validation, alert, selection, filter - **Quote templates** — output document - **Advanced approvals** — multi-step approval flows - **Contracts / Amendments / Renewals** — order lifecycle - **Subscription pricing** — recurring, ramp, evergreen ## Method (typical workflows) ### Add product to bundle 1. Set parent product as bundle (Configurable, Allow Quantity, Pricing Method). 2. Create Product Option records linking child products. 3. Set Min/Max quantity + Required flag. 4. Configure Pricing Method (List vs Block vs Custom Logic). 5. Test in Quote Line Editor. ### Price rule 1. Identify the trigger — field change on Quote Line. 2. Define conditions — when does the rule fire? 3. Define actions — set field values, formulas, summary aggregates. 4. Set evaluation order — Calculator/Configurator/On Save. 5. Test against bundle + standalone scenarios. ### Quote template 1. Sections: Header, Line Items (grouped/ungrouped), Totals, Footer. 2. Templates per region/audience. 3. Template content fields (rich text, merge fields). 4. Conditional sections. 5. Test PDF generation; check pagination. ## Output shape ``` Workflow: <Bundle | Price Rule | Quote Template | Approval | Amendment> Configuration: Records: <count + names of metadata records> Files: <metadata XML paths> Test scenarios: - <scenario>: <expected outcome> - ... CPQ-specific limits: Lines per quote: <typical | hard cap> Calculation slots: <impact> Calculator job: <if async — note> Migration to Revenue Cloud: Equivalent surface: <if applicable> Effort: <low | med | high — based on customisation depth> ``` ## Rules - **Calculator order matters.** Price rules have explicit evaluation order — wrong order = wrong totals. - **Twin Fields** copy values between Quote Line and Product. Use them; don't reinvent via Apex. - **Product Options use lookups, not master-detail** — sharing is non-trivial. - **Subscriptions and one-time mix** — verify Subscription Pricing fields on every product. - **Quote Template is metadata.** Source-control it; don't edit only in Setup. ## Anti-patterns - Apex triggers on `SBQQ__QuoteLine__c` for things Price Rules can do (CPQ calculator vs trigger order conflicts) - Hardcoded discount percentages in formulas (use Discount Schedules) - Quote Templates with all logic in formulas (move to Quote Term records) - Bundles with > 50 options (perf cliff) ## When NOT to use - Org doesn't have CPQ licence - Greenfield revenue work — evaluate Revenue Cloud first - Simple price book — standard Salesforce Pricebook2 may be enough ## Subagent dispatch - `salesforce-architect` for capacity + perf review on large quotes - `apex-bulkifier` for any custom Apex on quote lines - `Plan` for migration to Revenue Cloud ## Key references - CPQ Implementation Guide: help.salesforce.com → Salesforce CPQ - Calculator order: docs detail Configurator → Pre-Calc → Calc → Post-Calc → On Save - Revenue Cloud migration: help.salesforce.com → Revenue Cloud ## Value over native CC CC won't naturally know CPQ's calculator pipeline, Twin Field semantics, Discount Schedule patterns, or Bundle Option lookup quirks. Platform-specific knowledge IS the value.
Related in Cloud & DevOps
appbuilder-action-scaffolder
IncludedCreate, implement, deploy, and debug Adobe Runtime actions with consistent layout, validation, and error handling. Use this skill whenever the user needs to add actions to an App Builder project, understand action structure (params, response format, web/raw actions), configure actions in the manifest, use App Builder SDKs (State, Files, Events, database), deploy and invoke actions via CLI, debug action issues, or implement patterns such as webhook receivers, custom event providers, journaling consumers, large payload redirects, action sequence pipelines, and Asset Compute workers. Also trigger when users mention serverless functions in Adobe context, action logging, IMS authentication for actions, or cron-style scheduled actions.
orchestrating-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. Use this skill when the user needs a multi-step Data Cloud pipeline, cross-phase troubleshooting, or data space and data kit management. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase sf data360 workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching phase-specific skill), the task is STDM/session tracing/parquet telemetry (use observing-agentforce), standard CRM SOQL (use querying-soql), or Apex implementation (use generating-apex).
github-project-automation
IncludedAutomate GitHub repository setup with CI/CD workflows, issue templates, Dependabot, and CodeQL security scanning. Includes 12 production-tested workflows and prevents 18 errors: YAML syntax, action pinning, and configuration. Use when: setting up GitHub Actions CI/CD, creating issue/PR templates, enabling Dependabot or CodeQL scanning, deploying to Cloudflare Workers, implementing matrix testing, or troubleshooting YAML indentation, action version pinning, secrets syntax, runner versions, or CodeQL configuration. Keywords: github actions, github workflow, ci/cd, issue templates, pull request templates, dependabot, codeql, security scanning, yaml syntax, github automation, repository setup, workflow templates, github actions matrix, secrets management, branch protection, codeowners, github projects, continuous integration, continuous deployment, workflow syntax error, action version pinning, runner version, github context, yaml indentation error
sf-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase `sf data360` workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching sf-datacloud-* skill), the task is STDM/session tracing/parquet telemetry (use sf-ai-agentforce-observability), standard CRM SOQL (use sf-soql), or Apex implementation (use sf-apex).
fabric-cli
IncludedUse this skill for Fabric.so CLI workflows with the `fabric` terminal command: diagnose/install/login, search or browse a Fabric library, save notes/links/files, create folders, ask the Fabric AI assistant, manage tasks/workspaces, generate shell completion, check subscription usage, produce JSON output, and use Fabric as persistent agent memory. Do not use for Microsoft Fabric/Azure/Power BI `fab`, Daniel Miessler's Fabric framework, Python Fabric SSH, Fabric.js, or textile/fashion fabric.
lark
IncludedLark/Feishu CLI skills: lark-cli operations for docs, markdown, sheets, base, calendar, im, mail, task, okr, drive, wiki, slides, whiteboard, apps, approval, attendance, contact, vc, minutes, event. Use when the user needs to operate Lark/Feishu resources via lark-cli, send messages, manage documents, spreadsheets, calendars, tasks, OKRs, deploy web pages, or any Feishu/Lark workspace operations.