What problem does it solve? Teams need visibility into which databases an application connects to, what collections exist on each connection, and what fields and physical columns a collection has, without granting write access or exposing credentials. This Skill provides a read-only Database Explorer page and API for that inspection, with role-based access control. ## Core Features & Use Cases - Connection and Collection Browsing: List every configured database connection, page through collections per connection, and inspect a collection's resolved definition, fields, and physical columns, indexes, keys, and constraints. - Role-Based Access: Grant non-administrator roles access to the /settings/database-explorer page with a single permission grant that governs both the navigation entry and the API endpoints. - Credential Safety by Default: Connection responses use an allow-list that never exposes passwords, hosts, ports, socket paths, TLS material, or pool settings. - Use Case: A support engineer needs to verify which physical columns exist on a production collection without touching the schema. Grant their role the database-explorer page access, then open the settings page or call GET /api/database-explorer/connections/:connection/collections/:collection/physical. ## Quick Start Register the database explorer plugin on both the server and client composition roots, then ask the assistant to list the application's database connections and inspect a collection's fields.
