Consumer Goods Sync Management Configure
Use this skill to set up Salesforce Consumer Goods (CG) Cloud Mobile Sync end-to-end...
Install
npx skills add forcedotcom/sf-skills --skill consumer-goods-sync-management-configure -g -a claude-code -y- Repository
- forcedotcom/sf-skills1.1k
- Category
- Design
- Updated
- 5d ago
- License
- Apache-2.0
- Context cost
- Mediumabout 3,000 tokens
- Runs scripts
- No, instructions only
What it does
Use this skill to set up Salesforce Consumer Goods (CG) Cloud Mobile Sync end-to-end for the Sync Management App managed package, it runs all three acts in order (Act 1 Setup Sync, Act 2 Assign Users, Act 3 Plan & Verify), not just installing the baseline, so a sales rep can see the day's planned visits offline. Use it when asked to \"set up CG Cloud mobile sync\", \"configure Consumer Goods mobile sync\", \"set up sync for Retail Execution\", \"install the sync baseline\", \"assign a user to the sync configuration\", \"verify the sync setup\", or \"why can't my rep see their planned visits offline\" when sync setup or the baseline install is suspected. DO NOT TRIGGER for general CG Cloud mobile-app troubleshooting unrelated to sync setup, for authoring new or custom sync baselines (this installs only shipped baselines discovered at runtime), or for building or customizing the mobile app UI itself, those are out of scope.
Setting up CG Cloud Mobile Sync means running all three acts in order, Act 1 (Setup Sync), Act 2 (Assign Users), Act 3 (Plan & Verify), NOT just installing the sync artefacts. Installing the baseline is one step of Act 1; finishing it is not finishing the setup.
Guide an admin/implementer through setting up Consumer Goods (CG) Cloud Mobile Sync for a customer org so a sales rep can install the CG Cloud Mobile App and see the day's planned visits offline. The moving parts live in the managed package Sync Management App (its namespace is resolved at runtime, see ns_prefix in Session state) plus CG Cloud core / Retail Execution settings.
This skill automates as much as a real transport can trigger, a Headless-360 / generic-core call (SOQL, sObject REST, Connect, Tooling), an sf deploy, or a global @RestResource /v1/* endpoint in the package. A public package method is not enough: in a managed package public is namespace-private (unreachable from a subscriber org), so only global/webservice/@RestResource members are triggerable. Where neither a generic core capability nor an invokable package action can complete a step, the skill reports what's needed, and who provides it, and stops that step; it never fakes a capability.
Scope & definition of done, READ THIS FIRST
"Set up CG Cloud mobile sync" / "set up sync for Retail Execution" / "configure Consumer Goods mobile sync" with no narrowing qualifier means run ALL THREE ACTS, in order: Act 1 → Act 2 → Act 3. It does not mean "install the artefacts." If you are about to run only the install for an unqualified request, that is the bug this section prevents, start at Act 1, step 1 (readiness).
