PranavNagrecha/AwesomeSalesforceSkills / skills/admin/analytics-data-manager
analytics-data-manager
VerifiedUse this skill when configuring Data Manager in CRM Analytics: enabling objects for sync, scheduling data sync runs, setting up remote connections to external databases, monitoring sync status and error logs, or troubleshooting connected object issues. Trigger keywords: data sync, connected objects, Data Manager, sync schedule, remote connection, Snowflake connector, sync error, incremental sync, CRM Analytics data pipeline. NOT for pushing external data in programmatically via the External Data API — use data/analytics-external-data. NOT for authoring dataflow nodes — use admin/analytics-dataflow-development.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 16.2 KB |
| references/examples.md | markdown | 6.7 KB |
| references/gotchas.md | markdown | 6.0 KB |
| references/llm-anti-patterns.md | markdown | 9.0 KB |
| references/well-architected.md | markdown | 5.4 KB |
| scripts/check_analytics_data_manager.pyexecutable | script | 11.8 KB |
| templates/analytics-data-manager-template.md | markdown | 4.1 KB |
templates/analytics-data-manager-template.md
View on GitHub# Analytics Data Manager — Work Template
Use this template when configuring, troubleshooting, or auditing the Data Manager layer of CRM Analytics.
---
## Scope
**Skill:** `analytics-data-manager`
**Request summary:** (describe what the user asked for — sync configuration, remote connection setup, error diagnosis, capacity audit, etc.)
**Layer confirmed:** [ ] Data Manager / sync layer [ ] Recipe/dataflow layer (route to `analytics-dataset-management`)
---
## Context Gathered
### Org and License
- CRM Analytics license type: _______________
- Org instance: _______________
- Admin performing configuration: _______________
### Current Sync State
- Total objects currently enabled for sync: ___ / 100 (hard limit)
- Number of concurrent syncs currently running or scheduled at the same time: ___ / 3 (hard limit)
- Connections present (list all): _______________
### Request Details
- Target objects or external tables to add/modify: _______________
- External database type (if applicable): [ ] Snowflake [ ] BigQuery [ ] Redshift [ ] S3 [ ] Other: ___
- Sync mode requested: [ ] Full [ ] Incremental [ ] Unsure (default to full for first sync)
- Downstream recipe/dataflow that will consume the connected object: _______________
---
## Pre-Configuration Checklist
- [ ] Total enabled objects < 100 (verified in Data Manager > Connect)
- [ ] No more than 3 syncs scheduled at the same time after this change
- [ ] For external databases: remote connection created and tested before enabling tables
- [ ] For external databases: Salesforce CRM Analytics IP egress ranges allowlisted in target database network policy
- [ ] For objects with cross-object formula fields: full sync scheduled periodically (not only incremental)
---
## Sync Configuration Plan
| Object / Table | Connection | Sync Mode | Schedule | Cross-Object Formulas? | Periodic Full Sync Needed? |
|---|---|---|---|---|---|
| | | Full / Incremental | | Yes / No | Yes / No |
| | | Full / Incremental | | Yes / No | Yes / No |
| | | Full / Incremental | | Yes / No | Yes / No |
---
## Remote Connection Details (if applicable)
| Field | Value |
|---|---|
| Connection name | |
| Connector type | Snowflake / BigQuery / Redshift / S3 / Other |
| Host / Account identifier | |
| Database | |
| Schema | |
| Authentication method | Password / Key Pair / OAuth |
| IP allowlist confirmed | Yes / No / N/A |
| Connection test result | Passed / Failed / Not yet run |
---
## Post-Sync Validation
After sync runs, verify each of the following:
- [ ] Monitor tab shows status = Completed (not Failed or Partial) for each object
- [ ] Row counts in Monitor tab match expected totals (cross-reference source object count)
- [ ] Critical fields are present in connected object schema (spot-check in Data Manager > Connect > [object] > Fields)
- [ ] No field-level errors in Monitor run log
---
## Downstream Materialization Confirmation
Connected objects are staging-layer replicas. A successful sync does NOT make data available in dashboards until a recipe or dataflow is run.
- [ ] Recipe / dataflow identified: _______________
- [ ] Recipe / dataflow re-run after sync completed
- [ ] Output dataset updated in Analytics Studio (verify Last Refreshed timestamp)
- [ ] Dashboard widget showing correct data after dataset refresh
---
## Monitoring and Alerting
- [ ] Data Manager monitoring notifications configured (Monitor > Notification Settings)
- [ ] Notification recipients: _______________
- [ ] Alert conditions: [ ] Sync Failure [ ] Partial Sync [ ] Other: ___
---
## Known Issues and Deviations
| Object | Issue | Mitigation |
|---|---|---|
| | Cross-object formula fields — incremental sync will miss related-object updates | Schedule periodic full sync |
| | | |
---
## Sync Runbook Summary
Document this for future admins:
- Total enabled objects: ___
- Objects using incremental-only sync: ___
- Objects requiring periodic full sync (cross-object formula dependency): ___
- Concurrent sync peak (max simultaneous runs): ___
- Remote connection credential expiry dates: ___
- Next capacity audit date: ___
---
## Notes
(Record any deviations from the standard pattern, escalated issues, or pending actions.)
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |