forcedotcom/sf-skills / skills/tableau-next-asset-create
tableau-next-asset-create
VerifiedBuild and edit Tableau Next semantic models (SDMs), vizzes, and dashboards via MCP. TRIGGER when: building a semantic model or dashboard from CSV/Excel files; ingesting a flat file/database into DLO/DMO; profiling a dataset (grain, measures, dimensions; large/wide files via `infer_object_schema`); adding a dimension, measure, AI-ready metric, join, or logical view; running a semantic query, interpreting a breakdown, analyzing account/customer engagement, or pulling counts/totals from existing Tableau Next data (even unnamed/read-only); creating/editing a viz (filter, forecast, sort, shelf, mark encoding, reference line), widget, or dashboard layout. Also: Data Cloud SQL transforms; show a dashboard; share/revoke access; reuse prod or promote Personal Org assets; provision users/licenses; data alerts ('alert me when'); list/classify verified questions or score agent SQL. DO NOT TRIGGER for: rewriting prose descriptions, layout-only dashboard review, debugging MCP, or writing app code.
references/tasks/create-data-transform.md
View on GitHub# Task: Create or update a Data Cloud SQL transform
Materialize a **derived** DLO/DMO from one or more source objects via a Data
Cloud SQL (DCSQL) transform. Use this when the user wants a new derived table
or to change how an existing transform-backed table is produced — not for
CSV ingest (`ingest-flat-file.md`) and not for semantic-model calculated
fields (`enrich-model.md`).
## Gates (assert before any tool call) → `../shared-gates.md`
Required: **G1** · Conditional: **G2** (◐, source object must exist)
- **G1** (router-asserted): a `mcp__tableau-next-*__` tool must be connected.
- **Tool names are written bare** — invoke each under your client's name for that `tableau-next-*` server tool (`shared-gates.md`).
- **Confirmation (this guide):** never call `create_data_transform`,
`update_data_transform`, or `run_data_transform` without an explicit "yes"
after showing SQL + preview. Run is a **separate** yes from create/update.
- **G2** (◐): the **source** relation must be a real `__dll` / `__dlm` from
`browse_data_assets`. Do not invent the apiName.
## Steps
Payloads, immutable-vs-editable fields, timeout recovery, SparkInternal
substitutions, and error strings are in
**`../data-transform-gotchas.md`**.
1. Disambiguate: **create** if the output object does not exist; **update**
if it is already transform-backed (never a second transform on that table).
2. Resolve the source `assetApiName` (with suffix). Multiple matches → STOP
and ask.
3. Generate DCSQL; validate (`validate_data_transform` and/or `run_query`
with `rowLimit: 10`). **Every output SELECT alias / `fields[].name` must
be `__c`-suffixed** — validate does not error on a bare alias, it
silently renames the derived field, and the mismatch only fails later
on `run_data_transform` (see the deep ref).
4. Confirm with the user (SQL + preview + output name).
5. Create (full nested `definitions`/`manifest`) or update (GET first; full
replace; copy 🔒 fields). Create, update, and validate send the **same
flat body** (`name` / `type` / `definitions` at the top level — no
`dataTransformObject` / `dataTransform` envelope). On update timeout, GET
and compare `compiled_code` — do not blindly retry.
6. Create-only: add the new output object to the workspace the user named
(else list and ask).
7. Confirm, then `run_data_transform` only after the transform is `ACTIVE`
(not `PROCESSING`). Runs may be sync or async; poll
`get_data_transform_run_history` until the run succeeds or fails
(typically 10–15 minutes). If status looks stuck, call
`refresh_data_transform_status` then poll history again. Do **not** treat
`get_data_transform` `ACTIVE` as “rows are ready.” BATCH definitions use
`DCSQL`; STREAMING uses `SQL`. DMO outputs need `KQ_<pk>` (see the deep
ref).
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 |