PranavNagrecha/AwesomeSalesforceSkills / skills/admin/analytics-recipe-design
analytics-recipe-design
VerifiedUse this skill when designing or building CRM Analytics Data Prep recipes — including node selection, join patterns, bucket field configuration, formula expressions, and scheduling. Triggers: 'build a recipe', 'join datasets in analytics', 'bucket a measure field', 'schedule a recipe', 'data prep transformation'. NOT for dataflow JSON and its node types — use admin/analytics-dataflow-development. NOT for tuning a slow or oversized dataset — use data/analytics-dataset-optimization.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 17.5 KB |
| references/examples.md | markdown | 7.3 KB |
| references/gotchas.md | markdown | 10.5 KB |
| references/llm-anti-patterns.md | markdown | 7.5 KB |
| references/metadata-examples.md | markdown | 7.3 KB |
| references/well-architected.md | markdown | 7.7 KB |
| scripts/check_analytics_recipe_design.pyexecutable | script | 8.8 KB |
| templates/analytics-recipe-design-template.md | markdown | 4.3 KB |
templates/analytics-recipe-design-template.md
View on GitHub# Analytics Recipe Design — Work Template
Use this template when designing or building a CRM Analytics Data Prep recipe.
## Scope
**Skill:** `analytics-recipe-design`
**Request summary:** (fill in what the user asked for — e.g., "Build a recipe to enrich Opportunity data with Account segment information and schedule it nightly")
---
## Context Gathered
Record answers to the Before Starting questions from SKILL.md before touching the canvas.
| Question | Answer |
|---|---|
| CRM Analytics license confirmed? | [ ] Yes / [ ] No — permission set: |
| Source datasets (names + object origins) | |
| Output dataset name | |
| Join keys and cardinality | |
| Required output columns | |
| Aggregation logic needed? | [ ] Yes / [ ] No — describe: |
| Refresh schedule required? | [ ] Yes / [ ] No — cadence: |
| Input dataset row count estimate | |
| Row-level security predicate needed? | [ ] Yes / [ ] No — predicate field: |
---
## Node Graph Design
Document the intended node sequence before opening the recipe canvas.
| Step | Node Type | Configuration Summary | Join Type (if Join) |
|---|---|---|---|
| 1 | Load | Dataset: | n/a |
| 2 | Load | Dataset: | n/a |
| 3 | Filter | Condition: | n/a |
| 4 | Join | Keys: | (Inner / LeftOuter / RightOuter / Outer / Lookup / MultiValueLookup) |
| 5 | Bucket | Source field: / Output column: | n/a |
| 6 | Formula | Output column: / Expression: | n/a |
| 7 | Aggregate | Group by: / Aggregations: | n/a |
| 8 | Output | Dataset name: | n/a |
Add or remove rows as needed. Every Join node row must have an explicit join type — do not leave blank.
---
## Join Type Rationale
For each Join node, document why that join type was chosen:
| Join Node | Join Type | Rationale |
|---|---|---|
| (e.g., Join 1 — Opps + Accounts) | Lookup | Must preserve all Opportunity rows; Account details are additive |
| | | |
---
## Bucket Node Configuration
For each Bucket node:
| Bucket Node | Source Field | Field Kind | Output Column | Bucket Labels and Ranges |
|---|---|---|---|---|
| | | Measure / Dimension / Date | | |
---
## Formula Node Expressions
For each Formula node (use recipe expression language, not SAQL):
| Formula Node | Output Column | Output Type | Expression |
|---|---|---|---|
| | | Text / Number / Date | |
---
## Schedule Configuration
If a recurring schedule is needed, record the Schedule Resource API call details:
```
PUT /services/data/v67.0/wave/asset/{recipeId}/schedule
Content-Type: application/json
{
"frequency": "_______________",
"daysOfWeek": ["_______________"],
"time": { "hour": __, "minute": __, "timeZone": "_______________" }
}
```
`frequency` values: `hourly` (add `hourlyInterval` and `lastHour`), `weekly`, `monthly` (use `daysOfMonth`), `monthlyrelative` (use `weekInMonth` and `dayInWeek`), `eventdriven` (use `"triggerRule": "$ALL_SALESFORCE_OBJECTS"` instead of `time`). There is no cron expression. GET and DELETE use the same URL.
Note: The `recipeId` starts with `05v` and comes from `GET /wave/recipes`. To run the recipe now, POST `{"dataflowId": "<targetDataflowId>", "command": "start"}` to `/wave/dataflowjobs`, where `targetDataflowId` (starts with `02KB`) comes from `GET /wave/recipes/{recipeId}?format=R3`.
---
## Checklist
Work through this before marking the recipe complete:
- [ ] Every Join node has an explicitly chosen and documented join type
- [ ] All enrichment joins (add columns, preserve all rows) use Lookup or LeftOuter — not Inner
- [ ] Bucket node types match the source field kind (Measure / Dimension / Date)
- [ ] Formula node expressions use recipe expression language (not SAQL)
- [ ] Recipe has been run at least once successfully
- [ ] Output dataset row count verified against input row count — no unexplained shrinkage
- [ ] All output columns confirmed correct in dataset schema view
- [ ] Bucket labels verified on sample rows
- [ ] Schedule configured via Schedule Resource API or Analytics Studio scheduling panel (not in recipe body)
- [ ] Security predicate applied to output dataset (if required)
- [ ] Recipe node names are descriptive (not "Node 1", "Join 2")
---
## Notes
Record any deviations from the standard pattern and why:
(e.g., "Used Inner join on Step 4 because the requirement explicitly states: only show Opportunities with a matched Account — this is intentional filtering, not enrichment.")
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| deprecation-and-migrationaddyosmani/agent-skillsManages deprecation and migration. Use when removing old systems, APIs, or features. Use when migrating users from one implementation to another. Use when migrating a database schema in production, such as renaming or dropping a column without downtime (expand/contract). Use when deciding whether to maintain or sunset existing code. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| performance-optimizationaddyosmani/agent-skillsOptimizes application performance across frontend, backend, queries, and databases. Use when performance requirements exist, when you suspect performance regressions, when Core Web Vitals or load times need improvement, when N+1 query patterns need fixing, or when profiling reveals bottlenecks. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| agent-cost-reportthedotmack/claude-memBelievable agent cost report for any period, default the last 7 full days PT, not counting today. Measured tokens from Claude Code transcripts priced at OpenRouter list prices (ESTIMATED), measured provider spend when a sanctioned source exists, note-taker cost separate, Timing-style HTML/PDF plus report.json, line-items.csv, evidence.json. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |
| agent-cost-reportthedotmack/claude-memBelievable agent cost report for any period, default the last 7 full days PT, not counting today. Measured tokens from Claude Code transcripts priced at OpenRouter list prices (ESTIMATED), measured provider spend when a sanctioned source exists, note-taker cost separate, Timing-style HTML/PDF plus report.json, line-items.csv, evidence.json. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |