Update to Preset API Skills

{
  "description": "Inspect or route Preset database connection configuration, validation, OAuth, upload, create, update, and delete workflows through direct Superset API calls. Use only for direct API workflows; Do not use for MCP-only work.",
  "included_files": [
    {
      "relative_path": "references/connection-configuration.md",
      "size_in_bytes": 1016
    },
    {
      "relative_path": "references/connection-credential-reads.md",
      "size_in_bytes": 944
    },
    {
      "relative_path": "references/connection-mutations-and-validation.md",
      "size_in_bytes": 1355
    }
  ],
  "name": "preset-database-connections",
  "skill_md_contents": "---\nname: preset-database-connections\ndescription: Inspect or route Preset database connection configuration, validation, OAuth, upload, create, update, and delete workflows through direct Superset API calls. Use only for direct API workflows; Do not use for MCP-only work.\n---\n\n# preset-database-connections\n\nUse for credential-bearing database connection reads and database connection changes.\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.\n- Prefer `preset-datasets` metadata before reading connection configuration.\n- Treat connection configuration as credential-bearing even on `GET`.\n- Get explicit confirmation before configuration reads, validation, OAuth, upload, create, update, or delete.\n- Redact SQLAlchemy URIs, passwords, private keys, SSH tunnel passwords, server certificates, access tokens, and engine `extra` secrets.\n\n## Decision Rules\n\n- Classify connection configuration as credential-bearing.\n- Permit metadata summary only unless the user approves a credential-bearing read.\n- Require approval before credential-bearing configuration reads, validation, OAuth, upload, create, update, sync permissions, or delete.\n- Forbid printing URI, password, private key, token, certificate, SSH password, or engine extras.\n\n## Workflow Order\n\n1. Resolve database connection metadata.\n2. Identify credential-bearing fields and endpoint risk.\n3. Prepare approval summary for configuration read, validation, OAuth, upload, create, update, or delete.\n4. Stop before credential-bearing configuration read, validation, OAuth, upload, create, update, or delete.\n\n## Retrieve\n\n- Connection configuration routing: [references/connection-configuration.md](references/connection-configuration.md)\n- Credential-bearing configuration reads and redaction: [references/connection-credential-reads.md](references/connection-credential-reads.md)\n- Validation, OAuth, upload, create/update/delete, sync permissions: [references/connection-mutations-and-validation.md](references/connection-mutations-and-validation.md)\n- Approval policy: load `preset-api` and then `references/safety-policy.md`.\n"
}