Claude Cursor GitHub Copilot Skill

preset-database-connections

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.

LLM Mart · 0 points · 0 views 0 listing impressions 0 install-command copies
Virus-scanned Reviewed automatically before listing.

Full trust report

Download preset-io-agent-skills-plugins_preset-api-skills_skills_preset-database-connections-73d2674.zip · 2 KB
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-api-skills/skills/preset-database-connections
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-database-connections

Use for credential-bearing database connection reads and database connection changes.

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.
  • Prefer preset-datasets metadata before reading connection configuration.
  • Treat connection configuration as credential-bearing even on GET.
  • Get explicit confirmation before configuration reads, validation, OAuth, upload, create, update, or delete.
  • Redact SQLAlchemy URIs, passwords, private keys, SSH tunnel passwords, server certificates, access tokens, and engine extra secrets.

Decision Rules

  • Classify connection configuration as credential-bearing.
  • Permit metadata summary only unless the user approves a credential-bearing read.
  • Require approval before credential-bearing configuration reads, validation, OAuth, upload, create, update, sync permissions, or delete.
  • Forbid printing URI, password, private key, token, certificate, SSH password, or engine extras.

Workflow Order

  1. Resolve database connection metadata.
  2. Identify credential-bearing fields and endpoint risk.
  3. Prepare approval summary for configuration read, validation, OAuth, upload, create, update, or delete.
  4. Stop before credential-bearing configuration read, validation, OAuth, upload, create, update, or delete.

Retrieve

Files (agent-skills)
  • references
    • connection-configuration.md 1016 B
      # Connection Configuration
      
      Database connection configuration can expose credentials, network topology, server certificates, SSH tunnel settings, private keys, SQLAlchemy URIs, and engine-specific secrets.
      
      Use this file to route to the narrow connection reference:
      
      - Credential-bearing configuration reads and redaction: [connection-credential-reads.md](connection-credential-reads.md)
      - Validation, OAuth, upload, create/update/delete, and sync permissions: [connection-mutations-and-validation.md](connection-mutations-and-validation.md)
      - General sensitive-operation policy: load `preset-api` and then `references/safety-policy.md`.
      
      Route `GET /api/v1/database/{pk}/connection`, `POST /api/v1/database/test_connection/`, and `POST /api/v1/database/validate_parameters/` through this skill.
      
      Treat configuration reads as credential-bearing even when the HTTP method is `GET`. Redact SQLAlchemy URIs, passwords, private keys, SSH tunnel passwords, server certificates, access tokens, and engine `extra` secrets.
      
    • connection-credential-reads.md 944 B
      # Connection Credential Reads
      
      Use this reference before reading database connection configuration or responding to secret-disclosure requests.
      
      ## Credential-Bearing Read
      
      | Goal | Endpoint |
      |---|---|
      | Connection configuration | `GET /api/v1/database/{pk}/connection` |
      
      Before calling this endpoint, summarize:
      
      1. Workspace hostname.
      2. Database ID and database name.
      3. Why connection configuration is needed instead of metadata.
      4. Fields expected to be read.
      5. Redaction plan for any returned secrets.
      
      Wait for explicit confirmation before reading configuration.
      
      Do not paste raw responses into logs, Markdown, PR comments, or handoff notes. Never print SQLAlchemy URIs, passwords, private keys, SSH tunnel passwords, server certificates, access tokens, encrypted extra, or engine `extra` secrets.
      
      If the user asks to reveal credential values, decline the disclosure and offer a redacted metadata summary or a safe validation plan.
      
    • connection-mutations-and-validation.md 1.3 KB
      # Connection Mutations And Validation
      
      Use this reference before database create, update, delete, validation, OAuth, upload, sync permissions, or SQL validation workflows.
      
      Database mutations and validation can expose credentials or change live connection behavior. Use the workspace OpenAPI for the deployed version before relying on request fields.
      
      ## Endpoints
      
      | Goal | Endpoint |
      |---|---|
      | Create database connection | `POST /api/v1/database/` |
      | Update database connection | `PUT /api/v1/database/{pk}` |
      | Delete database connection | `DELETE /api/v1/database/{pk}` |
      | Sync database permissions | `POST /api/v1/database/{pk}/sync_permissions/` |
      | Test connection | `POST /api/v1/database/test_connection/` |
      | Validate connection parameters | `POST /api/v1/database/validate_parameters/` |
      | Validate SQL for a database | `POST /api/v1/database/{pk}/validate_sql/` |
      | OAuth callback/token storage | `GET /api/v1/database/oauth2/` |
      | Upload file metadata | `POST /api/v1/database/upload_metadata/` |
      | Upload file to database | `POST /api/v1/database/{pk}/upload/` |
      | Upload-capable schemas | `GET /api/v1/database/{pk}/schemas_access_for_file_upload/` |
      
      Before mutating or validating, summarize the target database, request body with secrets redacted, expected effect, rollback plan, and validation plan.
      
      Wait for explicit confirmation.
      
  • SKILL.md 2.2 KB
    ---
    name: preset-database-connections
    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.
    ---
    
    # preset-database-connections
    
    Use for credential-bearing database connection reads and database connection changes.
    
    ## 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.
    - Prefer `preset-datasets` metadata before reading connection configuration.
    - Treat connection configuration as credential-bearing even on `GET`.
    - Get explicit confirmation before configuration reads, validation, OAuth, upload, create, update, or delete.
    - Redact SQLAlchemy URIs, passwords, private keys, SSH tunnel passwords, server certificates, access tokens, and engine `extra` secrets.
    
    ## Decision Rules
    
    - Classify connection configuration as credential-bearing.
    - Permit metadata summary only unless the user approves a credential-bearing read.
    - Require approval before credential-bearing configuration reads, validation, OAuth, upload, create, update, sync permissions, or delete.
    - Forbid printing URI, password, private key, token, certificate, SSH password, or engine extras.
    
    ## Workflow Order
    
    1. Resolve database connection metadata.
    2. Identify credential-bearing fields and endpoint risk.
    3. Prepare approval summary for configuration read, validation, OAuth, upload, create, update, or delete.
    4. Stop before credential-bearing configuration read, validation, OAuth, upload, create, update, or delete.
    
    ## Retrieve
    
    - Connection configuration routing: [references/connection-configuration.md](references/connection-configuration.md)
    - Credential-bearing configuration reads and redaction: [references/connection-credential-reads.md](references/connection-credential-reads.md)
    - Validation, OAuth, upload, create/update/delete, sync permissions: [references/connection-mutations-and-validation.md](references/connection-mutations-and-validation.md)
    - Approval policy: load `preset-api` and then `references/safety-policy.md`.
    

Comments (0)

Sign in to join the conversation.

No comments yet.

Reviews (0)

No reviews yet.

Related