Update to Preset API Skills

{
  "description": "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.",
  "included_files": [
    {
      "relative_path": "references/query-control.md",
      "size_in_bytes": 562
    },
    {
      "relative_path": "references/query-history.md",
      "size_in_bytes": 1114
    },
    {
      "relative_path": "references/query-results-and-exports.md",
      "size_in_bytes": 978
    },
    {
      "relative_path": "references/routing-essentials.md",
      "size_in_bytes": 1269
    },
    {
      "relative_path": "references/saved-queries.md",
      "size_in_bytes": 2040
    },
    {
      "relative_path": "references/sql-execution.md",
      "size_in_bytes": 1803
    },
    {
      "relative_path": "references/sqllab-bootstrap.md",
      "size_in_bytes": 599
    }
  ],
  "name": "preset-sqllab",
  "skill_md_contents": "---\nname: preset-sqllab\ndescription: 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.\n---\n\n# preset-sqllab\n\nUse for SQL Lab capability and query metadata workflows in a resolved Preset workspace.\n\n## Always\n\n- 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.\n- Run SQL Lab bootstrap/capability metadata reads directly.\n- 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.\n- Route execution, result retrieval/export, query stop, saved-query mutation, and permalinks to `preset-sql-execution`.\n\n## Decision Rules\n\n- Distinguish query history metadata from SQL text, result retrieval, and execution to pick the right endpoint and filters.\n- Other users' history or SQL text, and any history read where owner filtering cannot be applied first, require confirmation.\n- Route saved query, history, result, stop, permalink, and execution requests separately.\n- Avoid SQL execution from this skill.\n\n## Workflow Order\n\n1. Inspect SQL Lab bootstrap state.\n2. Route history, saved query, result, stop, permalink, and execution request.\n3. Fetch owner-filtered history or saved queries the user asked for with parameterized page limits.\n4. Confirm before unowned SQL-text reads; route execution-family operations to `preset-sql-execution`.\n\n## Retrieve\n\n- Combined SQL Lab routing and approval essentials: [references/routing-essentials.md](references/routing-essentials.md)\n- SQL Lab availability, database options, UI defaults: [references/sqllab-bootstrap.md](references/sqllab-bootstrap.md)\n- Query history reads and SQL text exposure: [references/query-history.md](references/query-history.md)\n- Saved query reads, mutations, permalinks: [references/saved-queries.md](references/saved-queries.md)\n- SQL execution routing: [references/sql-execution.md](references/sql-execution.md)\n- Result retrieval and exports: [references/query-results-and-exports.md](references/query-results-and-exports.md)\n- Query stop/cancel: [references/query-control.md](references/query-control.md)\n"
}