PranavNagrecha/AwesomeSalesforceSkills / skills/admin/data-storytelling-design
data-storytelling-design
VerifiedDesigning data stories and narrative-driven analytics in Salesforce: structuring CRM Analytics dashboards for executive communication, text widgets and conditional highlights for annotation, sequential narrative in Tableau Story sheets, and Einstein Discovery narrative REST endpoints. Trigger keywords: data storytelling dashboard, executive analytics narrative, CRM Analytics text widget annotation, Tableau story sheet, smart data discovery narrative API. NOT for building the Einstein Discovery story or prediction definition - use admin/einstein-discovery-setup. NOT for choosing between Reports, CRM Analytics and Tableau - use admin/einstein-analytics-basics.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 14.1 KB |
| references/examples.md | markdown | 7.5 KB |
| references/gotchas.md | markdown | 9.4 KB |
| references/llm-anti-patterns.md | markdown | 4.8 KB |
| references/well-architected.md | markdown | 3.4 KB |
| scripts/check_data_storytelling_design.pyexecutable | script | 2.2 KB |
| templates/data-storytelling-design-template.md | markdown | 1.4 KB |
references/llm-anti-patterns.md
View on GitHub# LLM Anti-Patterns — Data Storytelling Design
Common mistakes AI coding assistants make when generating or advising on data storytelling in Salesforce.
---
## Anti-Pattern 1: Designing Dashboards Without a Defined Call to Action
**What the LLM generates:** A dashboard design with multiple charts and no narrative text, organized by chart type rather than by the insight the audience needs.
**Why it happens:** LLMs default to "add relevant charts" without asking what decision the dashboard enables.
**The correct pattern:** Before placing any chart, define: "After viewing this, [audience] will [take this action]." The layout and text widgets must make this action obvious without requiring the viewer to synthesize across multiple charts.
**Detection hint:** If the proposed design has no text widget and no single primary message, the design is incomplete.
---
## Anti-Pattern 2: Recommending Smart Data Discovery Narrative as Auto-Embedded
**What the LLM generates:** "Enable Einstein Discovery and the narrative will appear in your CRM Analytics dashboard automatically."
**Why it happens:** LLMs conflate enabling Einstein Discovery stories with automatic narrative injection into dashboards.
**The correct pattern:** The Einstein Discovery narrative comes from `POST /services/data/vXX.X/smartdatadiscovery/narrative` (API 51.0+), which returns narrative data for a story. Custom code (LWC, Visualforce, an integration) must call it and render the result; nothing in the documentation places it in CRM Analytics dashboards automatically. Do not cite `/wave/smartdatadiscovery/narratives`; that path is not the documented resource.
**Detection hint:** Any claim that enabling Einstein Discovery automatically adds narrative to existing dashboards is incorrect.
---
## Anti-Pattern 3: Using Multiple Dashboard Tabs Instead of Tableau Story Sheets for Sequential Narrative
**What the LLM generates:** "Create separate dashboard tabs for each step of the story — Introduction, Analysis, Recommendation."
**Why it happens:** LLMs suggest the most familiar Tableau/Salesforce pattern (tabs) without knowing the Story sheet exists.
**The correct pattern:** For sequential narrative, use Tableau Story sheets. They enforce guided sequence, support captions per view, and are designed for presentation mode. Multiple tabs require viewers to discover the sequence themselves.
**Detection hint:** If sequential narrative is the goal and the response suggests multiple dashboard tabs, suggest evaluating Tableau Story sheets instead.
---
## Anti-Pattern 4: Omitting Text Widgets from CRM Analytics Executive Dashboards
**What the LLM generates:** A CRM Analytics dashboard design with only metric tiles and charts, no text widgets.
**Why it happens:** LLMs list visualization elements without considering the narrative context layer.
**The correct pattern:** CRM Analytics executive dashboards must include text widgets with the primary message framed as a statement. Charts provide supporting evidence; text widgets deliver the conclusion.
**Detection hint:** Any CRM Analytics executive dashboard design without text widgets is missing the narrative layer.
---
## Anti-Pattern 5: Applying the Same Layout Pattern Regardless of Audience Role
**What the LLM generates:** A single dashboard template applied identically to executives, managers, and frontline users.
**Why it happens:** LLMs use a single dashboard template without accounting for role-specific information needs.
**The correct pattern:** Executive dashboards prioritize headline metrics (Z-pattern, 30-second readability). Manager dashboards include comparison and drill-down. Frontline dashboards prioritize action triggers and compact metric tiles with filter controls. Each role's design follows the Efficiency principle differently.
**Detection hint:** If audience-specific design is not addressed in the storytelling recommendations, the design is likely optimized for one role but not others.
---
## Anti-Pattern 6: Designing One Desktop Layout And Assuming It Works On Phones
**What the LLM generates:** A 12-column Z-pattern layout with no mention of mobile, followed by "executives can open it on their phones."
**Why it happens:** The model treats the dashboard as one canvas, as in slide tools.
**The correct pattern:** A CRM Analytics dashboard holds one or more `gridLayouts`, and the platform picks one by its `selectors` (for example a Mobile layout with `"maxWidth(599)"`). Build a phone layout with its own order: headline text, then one or two numbers, then one chart. Embedded dashboards in mobile browsers are not supported; phones use the CRM Analytics mobile app or Lightning app pages in the Salesforce mobile app. Set `mobileDisabled` where a dashboard should not open on mobile.
**Detection hint:** A storytelling design with a single layout, no `selectors`, and a claim about mobile readability.
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 |