preset-mcp

Étoiles11

Forks2

Mis à jour11 juin 2026 à 09:36

Route Superset MCP tool workflows, source-of-truth checks, and surface-boundary decisions. Use only for MCP tool workflows; do not use for direct API work.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Source

preset-io

preset-io/agent-skills

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Métiers associésSOC

Basé sur la classification professionnelle SOC

Développeurs de logicielsProfessions informatiques et mathématiques·SOC 15-1252

Explorateur de fichiers

3 fichiers

SKILL.md

readonly

name	preset-mcp
description	Route Superset MCP tool workflows, source-of-truth checks, and surface-boundary decisions. Use only for MCP tool workflows; do not use for direct API work.

preset-mcp

Use for Superset MCP intent, MCP tool routing, and MCP/API surface-boundary decisions.

Always

Stay on MCP tools for MCP intent.
Treat superset/superset/mcp_service as the only source of truth for MCP tool names, schemas, tags, annotations, prompts, resources, and RBAC metadata.
Call tools directly with the obvious parameters; fetch a tool's schema only after a validation error. These skills are workflow guidance, not schema definitions.
Do not use direct Preset Management API, Superset REST API, Snowflake Cortex API, curl, Python requests, exports, or database calls from this package.
If MCP cannot satisfy the request, stop and explain the missing MCP capability. Do not switch surfaces.

Decision Rules

MCP intent includes MCP tools, MCP clients, Superset MCP, Preset MCP, MCP resources, MCP prompts, tool discovery, and MCP tool errors.
Direct API intent includes API credentials, REST endpoints, OpenAPI, curl/Python requests, Management API, workspace API, and Snowflake Cortex APIs.
If the user starts with MCP intent and mentions direct API only as a fallback, keep MCP intent. Say: "No API fallback. Direct API is a different surface and requires separate explicit approval. Stop before API calls."
When the session is connected through MCP tools and the user has not named a surface, default to MCP and proceed; ask only when the user explicitly mixes both surfaces in one request.
Use a domain skill after routing: discovery, data, visualization, dashboard, sqllab, datasets, or troubleshooting.

Workflow Order

Identify whether the user requested MCP or direct API.
For MCP, choose the narrowest MCP domain skill.
Call the tool with the obvious parameters; consult its schema only after a validation error.
If MCP lacks a requested capability, explain the missing MCP capability.
Ask before changing surfaces and stop before API calls.

Retrieve

Tool categories and loading strategy: references/tool-categories.md
Surface boundary examples: references/surface-boundary.md

Plus depuis ce dépôt

même dépôt

preset-api

preset-io/agent-skills

Prepare direct Preset API access: auth, JWT exchange, base URLs, pagination, Rison parameters, response handling, and shared API setup. Use only for direct API workflows; Do not use for MCP-only work.

2026-06-2211

preset-dashboards

preset-io/agent-skills

Inspect Preset workspace dashboards, charts, dashboard composition, screenshots, thumbnails, chart data, and chart/dashboard operation routing through direct Superset API calls. Use only for direct API workflows; Do not use for MCP-only work.

2026-06-1211

preset-sql-execution

preset-io/agent-skills

Run or route SQL Lab execution, result retrieval, exports, query stop, saved-query mutation, and permalink workflows through direct Superset API calls. Use only for direct API workflows; Do not use for MCP-only work.

2026-06-1211

preset-cli

preset-io/agent-skills

Drive Preset's `sup` CLI (PyPI package `superset-sup`) for shell, scripting, CI/CD, and agent-driven Preset workflows. Use only for CLI workflows; Do not use for MCP-only work or for direct HTTP/SDK code paths.

2026-06-1211

preset-import-export

preset-io/agent-skills

Inspect and route direct Superset import/export workflows for dashboards, charts, datasets, databases, saved queries, themes, and asset bundles. Use only for direct API workflows; Do not use for MCP-only work.

2026-06-1111

preset-sqllab

preset-io/agent-skills

Inspect Preset SQL Lab bootstrap, query history, saved queries, result/export routing, query control, and SQL execution routing through direct Superset API calls. Use only for direct API workflows; Do not use for MCP-only work.

2026-06-1111

preset-mcp

Use for Superset MCP intent, MCP tool routing, and MCP/API surface-boundary decisions.

Always

Stay on MCP tools for MCP intent.

Treat superset/superset/mcp_service as the only source of truth for MCP tool names, schemas, tags, annotations, prompts, resources, and RBAC metadata.

Call tools directly with the obvious parameters; fetch a tool's schema only after a validation error. These skills are workflow guidance, not schema definitions.

Do not use direct Preset Management API, Superset REST API, Snowflake Cortex API, curl, Python requests, exports, or database calls from this package.

If MCP cannot satisfy the request, stop and explain the missing MCP capability. Do not switch surfaces.

Decision Rules

MCP intent includes MCP tools, MCP clients, Superset MCP, Preset MCP, MCP resources, MCP prompts, tool discovery, and MCP tool errors.

Direct API intent includes API credentials, REST endpoints, OpenAPI, curl/Python requests, Management API, workspace API, and Snowflake Cortex APIs.

If the user starts with MCP intent and mentions direct API only as a fallback, keep MCP intent. Say: "No API fallback. Direct API is a different surface and requires separate explicit approval. Stop before API calls."

When the session is connected through MCP tools and the user has not named a surface, default to MCP and proceed; ask only when the user explicitly mixes both surfaces in one request.

Use a domain skill after routing: discovery, data, visualization, dashboard, sqllab, datasets, or troubleshooting.

Workflow Order

Identify whether the user requested MCP or direct API.

For MCP, choose the narrowest MCP domain skill.

Call the tool with the obvious parameters; consult its schema only after a validation error.

If MCP lacks a requested capability, explain the missing MCP capability.

Ask before changing surfaces and stop before API calls.

Retrieve