motherduckdb/agent-skills / plugins/motherduck-skills-claude/skills/motherduck-security-governance
motherduck-security-governance
VerifiedAssess or configure MotherDuck access control, including roles (RBAC), share grants, table-, row-, and column-level security, masking, tenant isolation, residency, and Terraform governance.
Security and Governance
Source Of Truth
- Prefer current MotherDuck public trust, security, pricing, and product documentation.
- If the MotherDuck MCP
ask_docs_questionfeature is available, use it first. - Use current SSO and data-recovery docs when the requirement involves identity-provider login, restore windows, named snapshots, or
UNDROP DATABASE. - Verify claims against live public materials before making compliance or commercial assertions.
Default Posture
- Prefer service accounts for production systems, not personal tokens.
- Keep credentials in backend-controlled secrets, not browsers or hardcoded notebooks.
- Writes belong to the database owner; there is no write grant. Reads come from shares: restricted shares granted to roles,
INCLUDE_PATTERNfor which tables, secure views for which rows, columns, and values. Pick the archetype inreferences/ACCESS_CONTROL_SETUPS.mdbefore writing grants. - For answer or review requests, report the current and proposed access without changing it. For configure requests, apply the in-scope roles and grants, then verify them with
SHOWstatements and a real reader; ask before revoking access or widening an audience beyond the request. - Prefer structural isolation over query-time tenant filtering for serious B2B or CFA workloads.
- Treat region and residency as first-class architectural constraints that require current public confirmation.
- Be explicit about whether the boundary is a share, a Dive, a database, or a full application.
- Separate platform permissions (roles), data grants (who can attach a share), include patterns (which tables/views that share exposes), and secure views (which rows, columns, and values each consumer of that share sees).
- Secure views on shares provide row-level security, column-level security, and masking keyed on the consumer's identity or roles (plan-gated; verify current availability). For multi-tenant customer-facing products, structural isolation remains the stronger default; secure views fit internal audiences and partner or per-service-account shares.
- Flight
RUNgrants let others trigger a Flight that always executes with the owner's credentials. Review them like any privileged entry point: who holds the grant, which config the caller controls, and what the owner's token can write. - Map AI data flows explicitly:
prompt_jev()sends text and images to TypeSafe in the US from every region (off by default in EU regions);prompt()from Asia Pacific regions is served by a US endpoint; Agent Chat inference stays in the organization's geography. Admins control these on the AI Features settings page. - Flights can process PHI only under a signed HIPAA BAA; verify the current terms before relying on it.
- Separate documented product guarantees from architectural recommendations and assumptions in the final answer.
Workflow
- Identify where credentials live and who administers them.
- Define the actual isolation boundary: account, database, schema, share secure view, or query filter.
- Determine which preset/custom roles users hold, who can read, write, share, or administer the data, and which grants actually provide access.
- Check whether residency, compliance, or contractual guarantees are part of the requirement.
- Use only publicly documented security anchors unless the user has current commercial documentation in hand.
References
Read only the reference sections needed for the current task.
- Read
references/ACCESS_CONTROL_SETUPS.mdto design or review who can read and write what: the access model, a requirement-to-mechanism table, seven setup archetypes (simple warehouse, dev/prod, curated BI reader, team roles, row- and column-level access, customer-facing hypertenancy, partners), Terraform, and verification. - Read
references/SECURITY_GOVERNANCE_PLAYBOOK.mdfor public security anchors, service-account posture, residency and AI data flows, sharing boundaries, Flight run grants, governance as code, and what not to overstate
Related Skills
Load related skills only for missing capabilities; reuse established context.
motherduck-connectfor secure token handling and endpoint selectionmotherduck-explorewhen governance depends on what data is actually present and how it is partitionedmotherduck-share-datawhen the design includes governed data distribution
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |