preset-admin
Manage Preset teams, workspaces, memberships, invites, role identifiers, seat checks, and audit logs through direct Management…
@preset-ioInstall SkillDevelopment
Skill
/preset-mcp-visualization
Use Superset MCP tools for Explore links, chart configuration discovery, chart previews, saved charts, and chart updates. Use only for MCP tool workflows; do not use for direct API work.
Claude Code
$ npx -y skills add preset-io/agent-skills --skill preset-mcp-visualization --agent claude-code
Codex
$ npx skills add preset-io/agent-skills --skill preset-mcp-visualization -a codex -y
Cursor
$ npx skills add preset-io/agent-skills --skill preset-mcp-visualization -a cursor -y
Gemini CLI
$ npx skills add preset-io/agent-skills --skill preset-mcp-visualization -a gemini-cli -y
GitHub Copilot
$ npx skills add preset-io/agent-skills --skill preset-mcp-visualization -a github-copilot -y
OpenCode
$ npx skills add preset-io/agent-skills --skill preset-mcp-visualization -a opencode -y
Windsurf
$ npx skills add preset-io/agent-skills --skill preset-mcp-visualization -a windsurf -y
SKILL.md
preset-mcp-visualization.SKILL.mdname: preset-mcp-visualization
description: Use Superset MCP tools for Explore links, chart configuration discovery, chart previews, saved charts, and chart updates. Use only for MCP tool workflows; do not use for direct API work.
preset-mcp-visualization
Use for chart and Explore workflows through MCP.
Always
- Treat "create", "make", or "build" a chart as saved-chart intent: use `generate_chart` directly. Treat "add" as saved-chart intent only when no dashboard target is named; with a dashboard target, route to `preset-mcp-dashboard`.
- Use `generate_explore_link` for "show", "visualize", "explore", or "preview" requests with no save intent.
- Use `get_dataset_info` once to resolve exact column and metric names before building the config.
- Use `get_chart_type_schema` only for unfamiliar or complex chart types, or after a config validation error — not for simple bar, line, pie, table, or big-number charts.
- Use saved metrics as saved metrics; do not treat metric names as raw columns.
- `generate_chart` request shape: top-level `dataset_id` (not `datasource_id`), chart fields nested inside `config`, and `config.chart_type` uses the MCP taxonomy, currently common values such as `xy`, `table`, `pie`, `pivot_table`, `mixed_timeseries`, `handlebars`, and `big_number` — not a Superset `viz_type` string. If the needed type is not listed or validation fails, trust `get_chart_type_schema`.
- Never fabricate URLs. Use URLs returned by MCP tools.
Decision Rules
- Creation intent ("create/make/build a chart", or "add a chart" with no dashboard target): `generate_chart`. Do not substitute an unsaved Explore link.
- Preview intent ("show/visualize/explore/preview"): `generate_explore_link`.
- Use `update_chart` to change an existing saved chart.
- Use `update_chart_preview` only for cached preview form data.
- Route adding charts to dashboards to `preset-mcp-dashboard`.
Workflow Order
1. Resolve the dataset and its exact columns/metrics with one `get_dataset_info` call. 2. Build the config and call the tool matching the user's intent (create → `generate_chart`). 3. If the call returns a validation error, do not retry the same config blindly: fetch `get_chart_type_schema` once, fix the config against it, and retry once. 4. Report success based on the tool response, not assumption.
Retrieve
- Visualization workflow details: [references/visualization-workflows.md](references/visualization-workflows.md)
Read more
name: preset-mcp-visualization description: Use Superset MCP tools for Explore links, chart configuration discovery, chart previews, saved charts, and chart updates. Use only for MCP tool workflows; do not use for direct API work.
preset-mcp-visualization
Use for chart and Explore workflows through MCP.
Always
- Treat "create", "make", or "build" a chart as saved-chart intent: use `generate_chart` directly. Treat "add" as saved-chart intent only when no dashboard target is named; with a dashboard target, route to `preset-mcp-dashboard`.
- Use `generate_explore_link` for "show", "visualize", "explore", or "preview" requests with no save intent.
- Use `get_dataset_info` once to resolve exact column and metric names before building the config.
- Use `get_chart_type_schema` only for unfamiliar or complex chart types, or after a config validation error — not for simple bar, line, pie, table, or big-number charts.
- Use saved metrics as saved metrics; do not treat metric names as raw columns.
- `generate_chart` request shape: top-level `dataset_id` (not `datasource_id`), chart fields nested inside `config`, and `config.chart_type` uses the MCP taxonomy, currently common values such as `xy`, `table`, `pie`, `pivot_table`, `mixed_timeseries`, `handlebars`, and `big_number` — not a Superset `viz_type` string. If the needed type is not listed or validation fails, trust `get_chart_type_schema`.
- Never fabricate URLs. Use URLs returned by MCP tools.
Decision Rules
- Creation intent ("create/make/build a chart", or "add a chart" with no dashboard target): `generate_chart`. Do not substitute an unsaved Explore link.
- Preview intent ("show/visualize/explore/preview"): `generate_explore_link`.
- Use `update_chart` to change an existing saved chart.
- Use `update_chart_preview` only for cached preview form data.
- Route adding charts to dashboards to `preset-mcp-dashboard`.
Workflow Order
1. Resolve the dataset and its exact columns/metrics with one `get_dataset_info` call. 2. Build the config and call the tool matching the user's intent (create → `generate_chart`). 3. If the call returns a validation error, do not retry the same config blindly: fetch `get_chart_type_schema` once, fix the config against it, and retry once. 4. Report success based on the tool response, not assumption.
Retrieve
- Visualization workflow details: [references/visualization-workflows.md](references/visualization-workflows.md)
Ships withagent-skills
Agent guidance for working with Preset, Apache Superset, and Superset MCP tools. The skills are authored once and load across every supported agent client — see Supported clients.
1329 skills
Stars on GitHub
Momentum
- stars in total
- 13
Other skills on agent-skills.
@preset-ioInstall Skillpreset-api
Prepare direct Preset API access: auth, JWT exchange, base URLs, pagination, Rison parameters, response handling, and shared API…
@preset-ioInstall Skillpreset-dashboards
Inspect Preset workspace dashboards, charts, dashboard composition, screenshots, thumbnails, chart data, and chart/dashboard…
@preset-ioInstall Skillpreset-database-connec…
Inspect or route Preset database connection configuration, validation, OAuth, upload, create, update, and delete workflows…
@preset-ioInstall Skillpreset-datasets
Inspect Preset workspace datasets, database metadata, schemas, tables, columns, metrics, and dataset/database workflow routing…
@preset-ioInstall Skillpreset-destructive-imp…
Review destructive, overwrite-capable, sparse-update, all-assets restore, database import, and secret-bearing Preset import…
@preset-ioInstall SkillMore skills from other plugins.
Auto-invoked
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…
@obraInstall Skillask-matt
Ask which skill or flow fits your situation. A router over the skills in this repo.
@mattpocockInstall SkillAuto-invoked
Questions about preset-mcp-visualization.
- Which coding agents can use preset-mcp-visualization?
- preset-mcp-visualization installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.