motherduck-security-governance

What problem does it solve?

This skill helps clarify and design secure governance and access-control patterns in MotherDuck by aligning the requested security posture with the actual isolation and sharing boundaries that exist in the workspace.

Core Features & Use Cases

• Security and governance guidance: Produces safe defaults for credentials, isolation boundaries, and administrative vs consumer responsibilities.
• Boundary-first architecture framing: Distinguishes account, database, schema, Dive, share, and query-filter approaches so claims match the real control boundary.
• Governance-safe verification: Recommends checking live metadata (owned/shared databases and shares) and aligning answers with publicly documented security anchors.
• SSO, residency, and recovery considerations: Helps structure questions around SSO organization controls, region/residency constraints, and recovery/retention guidance without overstating guarantees.

Quick Start

Ask for a governance-safe recommendation by providing your intended isolation boundary (share vs Dive vs database vs query filter), credential approach (service accounts vs tokens), and residency/compliance needs, and then request a checklist-style response tailored to your architecture.