How do I install the Preset Sqllab skill?

Run npx skillmds@latest add preset-io/preset-sqllab in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Preset Sqllab safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Preset Sqllab?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Preset Sqllab free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Preset Sqllab?

preset-io (@preset-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Preset Sqllab by preset-io — Agent Skill

Name: Preset Sqllab
Author: preset-io

Preset Sqllab

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.

preset-io Updated Sep 17, 2026

File contents

preset-sqllab

Use for SQL Lab capability and query metadata workflows in a resolved Preset workspace.

Always

Auth and conventions come from preset-api (JWT exchange, base URLs, Rison); resolve the workspace hostname through the Management API when it is not already known. Consult preset-superset only when permissions drift matters.
Run SQL Lab bootstrap/capability metadata reads directly.
Run the user's own query history and saved-query reads directly when they asked in their own message AND current-user/owner filtering is applied before SQL-bearing fields are fetched (default page 25 records, hard cap 100 without explicit confirmation). If an endpoint returns SQL text before ownership is proven, keep the read confirmation-gated as SQL-text disclosure.
Route execution, result retrieval/export, query stop, saved-query mutation, and permalinks to preset-sql-execution.

Decision Rules

Distinguish query history metadata from SQL text, result retrieval, and execution to pick the right endpoint and filters.
Other users' history or SQL text, and any history read where owner filtering cannot be applied first, require confirmation.
Route saved query, history, result, stop, permalink, and execution requests separately.
Avoid SQL execution from this skill.

Workflow Order

Inspect SQL Lab bootstrap state.
Route history, saved query, result, stop, permalink, and execution request.
Fetch owner-filtered history or saved queries the user asked for with parameterized page limits.
Confirm before unowned SQL-text reads; route execution-family operations to preset-sql-execution.

Retrieve

Combined SQL Lab routing and approval essentials: references/routing-essentials.md
SQL Lab availability, database options, UI defaults: references/sqllab-bootstrap.md
Query history reads and SQL text exposure: references/query-history.md
Saved query reads, mutations, permalinks: references/saved-queries.md
SQL execution routing: references/sql-execution.md
Result retrieval and exports: references/query-results-and-exports.md
Query stop/cancel: references/query-control.md

---name: preset-sqllabdescription: 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.---# preset-sqllabUse for SQL Lab capability and query metadata workflows in a resolved Preset workspace.## Always- Auth and conventions come from `preset-api` (JWT exchange, base URLs, Rison); resolve the workspace hostname through the Management API when it is not already known. Consult `preset-superset` only when permissions drift matters.- Run SQL Lab bootstrap/capability metadata reads directly.- Run the user's own query history and saved-query reads directly when they asked in their own message AND current-user/owner filtering is applied before SQL-bearing fields are fetched (default page 25 records, hard cap 100 without explicit confirmation). If an endpoint returns SQL text before ownership is proven, keep the read confirmation-gated as SQL-text disclosure.- Route execution, result retrieval/export, query stop, saved-query mutation, and permalinks to `preset-sql-execution`.## Decision Rules- Distinguish query history metadata from SQL text, result retrieval, and execution to pick the right endpoint and filters.- Other users' history or SQL text, and any history read where owner filtering cannot be applied first, require confirmation.- Route saved query, history, result, stop, permalink, and execution requests separately.- Avoid SQL execution from this skill.## Workflow Order1. Inspect SQL Lab bootstrap state.2. Route history, saved query, result, stop, permalink, and execution request.3. Fetch owner-filtered history or saved queries the user asked for with parameterized page limits.4. Confirm before unowned SQL-text reads; route execution-family operations to `preset-sql-execution`.## Retrieve- Combined SQL Lab routing and approval essentials: [references/routing-essentials.md](references/routing-essentials.md)- SQL Lab availability, database options, UI defaults: [references/sqllab-bootstrap.md](references/sqllab-bootstrap.md)- Query history reads and SQL text exposure: [references/query-history.md](references/query-history.md)- Saved query reads, mutations, permalinks: [references/saved-queries.md](references/saved-queries.md)- SQL execution routing: [references/sql-execution.md](references/sql-execution.md)- Result retrieval and exports: [references/query-results-and-exports.md](references/query-results-and-exports.md)- Query stop/cancel: [references/query-control.md](references/query-control.md)

Frequently asked questions