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/promote-or-reuse.md
View on GitHub# Task: Reuse a prod asset or promote a Personal Org asset
**Reuse** copies a production Dashboard, Visualization, DMO, SDM, or CIO
into a Personal Org workspace. **Promotion** packages a Personal Org asset
and, after the export is ready, lands datakits in a git repo via a reviewed
PR. Both use `create_reuse_promotion_request`; only Promotion then uses
`create_promotion_pull_request`.
Not a greenfield create (`build-end-to-end.md` / `create_semantic_model`) and
not sharing with a user (`share-asset.md`).
## Gates (assert before any tool call) → `../shared-gates.md`
Required: **G1**
- **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):** confirm `requestType` (Reuse vs Promotion),
`assetId`, workspace, label, and `requesterComment` before create. After a
Promotion export is `Ready`, **ask again** before
`create_promotion_pull_request`. Ask for the target directory and branch
name — do not invent them.
## Steps
Direction flip, poll fields (`status` vs `packageExportStatus`), list
filters, HTTP 400, and the client-side convert/`gh` procedure are in
**`../sharing-and-promotion.md`** (§Promote).
1. Confirm Personal Org context. Create is rejected outside it.
2. `create_reuse_promotion_request` with a non-empty `requesterComment`
(max 254 chars).
Reuse: prod `assetId` + Personal Org destination workspace. Promotion:
Personal Org `assetId` + the workspace that contains it.
3. Poll **`get_promotion_reuse_request`** with the returned id (not an
unfiltered list). Reuse: wait for the terminal `completed` (not
`migrationSucceeded`, a transient intermediate a late poll skips); **STOP**
on `failed` / `cancelled` / `rejected` (`rejectionComment` when rejected).
Promotion: poll `packageExportStatus` for lowercase `ready` (10s × 30s
window); `status` stays `requested` throughout.
4. Survey outstanding Reuse work with `list_promotion_reuse_requests` and
top-level `requestType=reuse` (not a `requestParams` wrapper). For one
known id, get-by-id.
5. Promotion only, after user confirm: `create_promotion_pull_request`, then
the download / `sf` convert / copy / `gh pr create` recovery path in the
deep ref. Stop if `sf` is missing.
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 |