Claude Cursor GitHub Copilot Skill

preset-mcp-dashboard

Use Superset MCP tools for dashboard inspection, dashboard creation, and adding charts to dashboards. 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-dashboard-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-dashboard

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

Use for dashboard workflows through MCP.

Always

Use list_dashboards and get_dashboard_info for dashboard discovery.
Use add_chart_to_existing_dashboard when the user wants to add a chart to an existing dashboard.
Use generate_dashboard only for a brand-new dashboard.
Never create a new dashboard as a silent fallback after add-to-existing fails.
Report permission-denied results directly and ask before changing the plan.

Decision Rules

Existing dashboard target present: use add_chart_to_existing_dashboard.
New dashboard request: use generate_dashboard with known chart IDs.
Dashboard analysis without result rows: stay on metadata/detail tools.
Dashboard chart data: route to preset-mcp-data.
Chart creation before dashboard assembly: route to preset-mcp-visualization.

Workflow Order

Resolve dashboard and chart IDs.
Inspect existing dashboard details when modifying one.
Add to existing or create new according to user intent.
Use only URLs and status returned by MCP tools.

Retrieve

Dashboard workflows: references/dashboard-workflows.md

Files (agent-skills)

references

dashboard-workflows.md 1.4 KB

# Dashboard Workflows

| Goal | MCP Tool |
|---|---|
| Find dashboards | `list_dashboards` |
| Inspect dashboard metadata/layout/charts | `get_dashboard_info` |
| Create a new dashboard from chart IDs | `generate_dashboard` |
| Add a chart to an existing dashboard | `add_chart_to_existing_dashboard` |
| Remove a chart from a dashboard | `remove_chart_from_dashboard` |
| Inspect stored chart positions | `get_dashboard_layout` |
| Change layout, title, theme, CSS, or cross-filtering | `update_dashboard` |

If `add_chart_to_existing_dashboard` reports a permission problem, tell the user they lack edit rights and ask before creating a new dashboard. Do not silently pivot to `generate_dashboard`.

## Layout

Both `generate_dashboard` and `update_dashboard` accept `position_json`, Superset's layout tree — chart placement is not limited to the auto-arranged grid. The grid is 12 columns wide and row heights are in 8px units; set `width`/`height` under each `CHART-<id>` component's `meta`.

`position_json` fully replaces the existing layout, so author the whole tree in one call: every chart must be reachable from `ROOT_ID` and each component's `parents` must list its full ancestor chain. `get_dashboard_layout` reports the stored per-chart `width`/`height` but not the raw tree, so it verifies a write rather than enabling an incremental edit.

`generate_dashboard` is for new dashboards only. To re-lay-out an existing one, use `update_dashboard` — never re-create it.

SKILL.md 1.4 KB

---
name: preset-mcp-dashboard
description: Use Superset MCP tools for dashboard inspection, dashboard creation, and adding charts to dashboards. Use only for MCP tool workflows; do not use for direct API work.
---

# preset-mcp-dashboard

Use for dashboard workflows through MCP.

## Always

- Use `list_dashboards` and `get_dashboard_info` for dashboard discovery.
- Use `add_chart_to_existing_dashboard` when the user wants to add a chart to an existing dashboard.
- Use `generate_dashboard` only for a brand-new dashboard.
- Never create a new dashboard as a silent fallback after add-to-existing fails.
- Report permission-denied results directly and ask before changing the plan.

## Decision Rules

- Existing dashboard target present: use `add_chart_to_existing_dashboard`.
- New dashboard request: use `generate_dashboard` with known chart IDs.
- Dashboard analysis without result rows: stay on metadata/detail tools.
- Dashboard chart data: route to `preset-mcp-data`.
- Chart creation before dashboard assembly: route to `preset-mcp-visualization`.

## Workflow Order

1. Resolve dashboard and chart IDs.
2. Inspect existing dashboard details when modifying one.
3. Add to existing or create new according to user intent.
4. Use only URLs and status returned by MCP tools.

## Retrieve

- Dashboard workflows: [references/dashboard-workflows.md](references/dashboard-workflows.md)