Skip to content

forcedotcom/sf-skills / skills/tableau-next-asset-create

tableau-next-asset-create

Verified

Build 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.

FileKindSize
SKILL.mdskill md23.9 KB
references/admin-users.mdmarkdown5.9 KB
references/ai-readiness.mdmarkdown17.5 KB
references/alerts.mdmarkdown3.9 KB
references/build-workflow.mdmarkdown41.4 KB
references/dashboard-authoring.mdmarkdown15.5 KB
references/dashboard-design-principles.mdmarkdown18.6 KB
references/data-transform-gotchas.mdmarkdown9.5 KB
references/data-understanding.mdmarkdown26.8 KB
references/deep-reference-index.mdmarkdown4.8 KB
references/destructive-operations.mdmarkdown3.9 KB
references/edit-dashboard.mdmarkdown19.8 KB
references/edit-visualization.mdmarkdown41.5 KB
references/empty-source-handling.mdmarkdown4.9 KB
references/ingest-and-metric-gotchas.mdmarkdown35.4 KB
references/insight-bundle.mdmarkdown2.7 KB
references/large-flat-file-handling.mdmarkdown19.1 KB
references/schemas/edit-dashboard/_envelope.jsonconfig3.1 KB
references/schemas/edit-dashboard/_shared-widget-fields.jsonconfig7.0 KB
references/schemas/edit-dashboard/add_page.jsonconfig1.1 KB
references/schemas/edit-dashboard/delete_page.jsonconfig947 B
references/schemas/edit-dashboard/discard_dashboard.jsonconfig482 B
references/schemas/edit-dashboard/move_widget.jsonconfig1.4 KB
references/schemas/edit-dashboard/move_widget_to_page.jsonconfig1.4 KB
references/schemas/edit-dashboard/place_widget_on_page.jsonconfig1.4 KB
references/schemas/edit-dashboard/remove_widget_from_dashboard.jsonconfig864 B
references/schemas/edit-dashboard/remove_widget_from_page.jsonconfig1.1 KB
references/schemas/edit-dashboard/rename_page.jsonconfig1.0 KB
references/schemas/edit-dashboard/save_dashboard.jsonconfig775 B
references/schemas/edit-dashboard/undo.jsonconfig421 B
references/schemas/edit-dashboard/upsert_button_widget.jsonconfig3.3 KB
references/schemas/edit-dashboard/upsert_container_widget.jsonconfig4.2 KB
references/schemas/edit-dashboard/upsert_filter_widget.jsonconfig8.8 KB
references/schemas/edit-dashboard/upsert_metric_widget.jsonconfig3.8 KB
references/schemas/edit-dashboard/upsert_navigation_widget.jsonconfig4.4 KB
references/schemas/edit-dashboard/upsert_parameter_widget.jsonconfig9.9 KB
references/schemas/edit-dashboard/upsert_text_widget.jsonconfig5.5 KB
references/schemas/edit-dashboard/upsert_visualization_widget.jsonconfig3.4 KB
references/sdm-tool-reference.mdmarkdown33.1 KB
references/semantic-query-and-enrichment.mdmarkdown16.3 KB
references/shared-gates.mdmarkdown17.6 KB
references/sharing-and-promotion.mdmarkdown14.4 KB
references/tasks/ai-readiness-audit.mdmarkdown3.0 KB
references/tasks/analyze-data.mdmarkdown2.5 KB
references/tasks/build-dashboard.mdmarkdown3.7 KB
references/tasks/build-end-to-end.mdmarkdown4.4 KB
references/tasks/create-data-transform.mdmarkdown2.8 KB
references/tasks/create-viz.mdmarkdown3.6 KB
references/tasks/edit-dashboard.mdmarkdown5.0 KB
references/tasks/edit-sdm.mdmarkdown6.5 KB
references/tasks/edit-viz.mdmarkdown2.4 KB
references/tasks/enrich-model.mdmarkdown4.0 KB
references/tasks/ingest-flat-file.mdmarkdown3.9 KB
references/tasks/manage-alert.mdmarkdown1.6 KB
references/tasks/profile-dataset.mdmarkdown2.7 KB
references/tasks/promote-or-reuse.mdmarkdown2.3 KB
references/tasks/provision-user.mdmarkdown1.8 KB
references/tasks/query-model.mdmarkdown5.3 KB
references/tasks/review-verified-questions.mdmarkdown1.9 KB
references/tasks/share-asset.mdmarkdown1.8 KB
references/verified-questions.mdmarkdown4.6 KB
references/viz-authoring.mdmarkdown41.3 KB

references/tasks/edit-dashboard.md

View on GitHub
# Task: Edit an existing dashboard

Modify a dashboard that already exists — add/edit/move/remove a widget, or
add/rename/delete a page — via the atomic `edit_dashboard` batch tool, and only
persist the change on explicit request. For building a brand-new dashboard, use
`build-dashboard.md` instead. Entry point 20 ("add/edit a widget on an existing
dashboard" — see `build-dashboard.md`'s entry-point list).

## Gates (assert before any tool call) → `../shared-gates.md`

Required: **G1** · Conditional: **G3** (◐, only if placing a viz/metric widget
whose `id`/apiName you have not read back this session) · **G8** (◐, only if the
edit changes the narrative structure — e.g. adding a new KPI/chart — not a pure
reposition/rename)

- **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`).
- **No G2/G7 by default.** Repositioning, renaming, or removing an
  already-placed widget mutates layout, not data — the data-presence and
  query-returns-real-data gates don't re-apply. They DO apply transitively when
  the edit places a **new** viz/metric widget: that widget's underlying query
  must have returned real rows first (same rule as `build-dashboard.md`).
- **G8** (◐): reposition-only edits don't need a restated narrative; adding a
  widget that changes the story (a new KPI, a new breakdown) does — confirm it
  still fits the KPIs → trends → breakdowns → correlations order.

## Steps

The operation-type table, every `upsert_*_widget` shape, the widget-identity
rule, grid conventions, and draft-vs-persist mechanics are in
**`../edit-dashboard.md`**.

- **Before building a payload, Read the operation's schema file.**
  `../edit-dashboard.md` §2's table names the exact
  `../schemas/edit-dashboard/<operation>.json` for whichever operation(s) you're
  about to send (e.g. `upsert_metric_widget.json`, `move_widget.json`) — it has
  the authoritative required/optional fields, enums, and a worked example. Read
  only the file(s) for this batch, not the whole directory.
- **Always pass `minorVersion: -1` explicitly** on every `edit_dashboard` call —
  the schema shows it as a default, but it is not auto-applied; omitting it can
  surface `ILLEGAL_QUERY_PARAMETER_VALUE: Illegal value for query parameter
  'minorVersion': ''`.
- **Upsert → place, same discipline as viz creation.** An `upsert_*_widget`
  operation only *defines* a widget (create or full replace) — it renders
  nowhere until paired with `place_widget_on_page` (same batch, or a later one
  before you save) unless it's replacing an already-placed widget. Never
  define a new widget without also placing it.
- **Widget identity.** `widget.name` always identifies the widget inside an
  `upsert_*_widget` call; add `widget.id` only to fully replace an already
  *persisted* widget (never invent this value — read it back first, e.g. via
  `render_dashboard`/`get_dashboard`), and omit it to create a new widget. An
  unsaved draft widget has no `id` — replace it by `widget.name` alone. Page
  ops (`place_widget_on_page`/`remove_widget_from_page`/`move_widget`/
  `move_widget_to_page`) use a third, separate field: `placement.name`. Full
  detail: `../edit-dashboard.md` §3.
- **`autosave` is now top-level and batch-wide** (a sibling of `operations`,
  not a per-operation field). Leave it unset (default `false`) to stage a
  draft. The batch response IS the preview — show it, then ask before
  persisting. Drafts **accumulate** across successive `edit_dashboard` calls on
  the same dashboard until saved/discarded; the dashboard read tool will NOT
  show a staged draft.
- **Persist only on explicit confirmation.** `save_dashboard` may now appear
  standalone (commits whatever draft is already staged) or after other
  mutations in the same batch (persists once they succeed) — it's no longer
  required to be the batch's sole operation. Regardless of batch shape, only
  send it after the user confirms **having seen** the draft — even if the
  original request already said "save it" in the same message as the edit.
- **To revert an unsaved draft:** `undo` (standalone: reverts the last staged
  change; in a mixed batch: cancels every operation in that batch) or
  `discard_dashboard` (standalone: drops the whole staged draft; in a mixed
  batch: ignores every other operation in that batch). `undo` only works while
  a draft is staged — after a save there's nothing to undo (`RESOURCE_NOT_FOUND:
  "No staged draft to undo for dashboard <name>"`).
- **To fully delete a widget (not just unplace it):** use
  `remove_widget_from_dashboard` — a bare `widgetName`, deletes the definition
  and every placement across every page in one operation, in the same batch as
  any other `edit_dashboard` operations. `remove_widget_from_page` alone only
  removes the page placement, leaving an orphaned widget definition in the
  dashboard's `widgets` map — see `edit-dashboard.md` §6.
- No existing dashboard to edit? Route to **`build-dashboard.md`** instead.
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: 119kUpdated Claude CodeCodexVerifiedInstall
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: 119kUpdated Claude CodeCodexVerifiedInstall
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: 118kUpdated Claude CodeCodexVerifiedInstall
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: 118kUpdated Claude CodeCodexVerifiedInstall