Menu

Individual skill

consumer-goods-sync-management-configure

0upvotes

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.

skills/consumer-goods-sync-management-configure/SKILL.md

Read pinned source

Source commit a8a18ce1e4ba12e69b4073eab98ce31bfbd8271e

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 4, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,151
Repository last updated
Nov 6, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

**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).

**You are NOT done after installing artefacts.** Setup is complete only when **Act 3's end state** is reached (the activated config listed, verified across the four objects, and checked against the baseline files). A run that ends after the install is a *partial* run — say so plainly.

**Act 1 is not "install-only."** It has hard **readiness gates before** the install — the **namespace gate** (A1.1) and **Retail Execution enablement** (A1.2) — and a **verify after** it (A1.4). Installing the baseline into a non-RE-enabled org produces a config that can never sync, so readiness is checked first; a hard miss is **reported-and-stopped**, not written around. The baseline install *is* the sync configuration (the root `Sync_Config__c` and its values come from the baseline CSVs) — there is no separate "create config" step.