Claude Cursor GitHub Copilot 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.

LLM Mart · 0 points · 0 0 0

Virus-scanned Reviewed automatically before listing.

Full trust report

Download preset-io-agent-skills-plugins_preset-mcp-skills_skills_preset-mcp-visualization-73d2674.zip · 1 KB

preset-io/agent-skills 12 1 forks Apache-2.0 Updated 14d ago

Part of preset-io/agent-skills — 28 skills

Install

skills CLI

npx skills add https://github.com/preset-io/agent-skills/tree/master/plugins/preset-mcp-skills/skills/preset-mcp-visualization

Claude Code

claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install preset-io-agent-skills@llmmart

Git git clone https://github.com/preset-io/agent-skills.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole preset-io/agent-skills collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

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

Resolve the dataset and its exact columns/metrics with one get_dataset_info call.
Build the config and call the tool matching the user's intent (create → generate_chart).
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.
Report success based on the tool response, not assumption.

Retrieve

Visualization workflow details: references/visualization-workflows.md

Files (agent-skills)

references

visualization-workflows.md 859 B

# Visualization Workflows

## Create a Chart

For "create", "make", "build", or "add" a chart with no dashboard target:

1. `list_datasets` or `get_dataset_info` to resolve exact columns and metrics
2. `generate_chart`
3. On a validation error, `get_chart_type_schema` once, fix the config, retry once

Check the response for success or error before claiming the chart exists.

When a dashboard target is named, route to `preset-mcp-dashboard` instead.

## Preview Without Saving

For "show", "visualize", "explore", or "preview" requests with no save intent, use `generate_explore_link` instead of `generate_chart`. This creates a reviewable interactive URL without permanently saving a chart.

## Update Chart

Use `get_chart_info` before `update_chart` so the update is based on the current chart configuration. Do not use SQL execution to modify a chart.

SKILL.md 2.4 KB

---
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)