motherduckdb/motherduck-partner-delivery
plugins/motherduck-skills-claude/skills/motherduck-partner-delivery/SKILL.md
Deliver repeatable MotherDuck architectures across multiple clients. Use when a consultancy, agency, or multi-client product team needs to standardize isolation, provisioning, regional deployment, sharing boundaries, and client-specific exceptions across client engagements.
$ install --global
skillsauthnpx skillsauth add motherduckdb/agent-skills motherduck-partner-deliveryInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Jun 11, 2026, 3:04 AM134.7s1 file scanned
SKILL.md
- name:
- motherduck-partner-delivery
- description:
- Deliver repeatable MotherDuck architectures across multiple clients. Use when a consultancy, agency, or multi-client product team needs to standardize isolation, provisioning, regional deployment, sharing boundaries, and client-specific exceptions across client engagements.
- argument-hint:
- [client-delivery-scenario]
- license:
- MIT
Partner Delivery
Use this skill when a consultancy, implementation partner, or multi-client product team needs a repeatable MotherDuck delivery pattern across several clients.
This is a use-case skill. It orchestrates motherduck-connect, motherduck-explore, motherduck-model-data, motherduck-query, motherduck-share-data, and motherduck-create-dive.
Start Here: Is a MotherDuck Server Active?
Always determine this first.
- If a remote MotherDuck MCP server or local MotherDuck server is active, use it.
- If the delivery will run against an existing workspace, ask which client databases or workspaces are already in scope.
- Explore the live setup when available:
- current client database boundaries
- regional layout
- existing service-account or share boundaries
- reusable schemas vs client-specific schemas
Use that discovery to decide what can be standardized and what must stay client-specific.
If no server is active, ask for representative client patterns and regions before proposing the standard delivery model.
Use This Skill When
- The user is delivering MotherDuck solutions across multiple clients.
- The user needs region-aware, repeatable architecture.
- The user needs standard provisioning with explicit client exceptions.
- The goal is a reusable delivery pattern, not a one-off single-client implementation.
Delivery Defaults
- structural isolation over query-time tenant filtering
- one client database or stronger boundary per client
- shared architecture, client-specific schema
- explicit sharing and revocation per client
- versioned templates for provisioning, validation, handoff, and exception tracking
Workflow
- Confirm whether live MotherDuck discovery is available.
- Classify the client patterns.
- Inspect the existing regional and database layout if available.
- Standardize the architecture and provisioning path.
- Define the repeatable validation pack for every client environment.
- Document client-specific exceptions.
- Produce the handoff assets and validation checks.
When this skill produces a native DuckDB (md:) connection, watermark it with custom_user_agent=agent-skills/2.2.2(harness-<harness>;llm-<llm>). If metadata is missing, fall back to harness-unknown and llm-unknown.
Output
The output of this skill should be:
- the default multi-client pattern
- the standard provisioning checklist
- the region and isolation posture
- the client-specific exceptions
If the caller explicitly asks for structured JSON, return raw JSON only with no Markdown fences or prose before/after it. This is mainly for automated tests, regression checks, or downstream tooling that needs a stable machine-readable shape. Normal human-facing use of the skill can stay in prose unless JSON is explicitly requested.
Use this exact top-level shape when JSON is requested:
{
"summary": {},
"assumptions": [],
"implementation_plan": [],
"validation_plan": [],
"risks": []
}
References
Read this as reference, not as a script to execute:
references/PARTNER_DELIVERY_GUIDE.md-- default multi-client pattern, standardize-versus-client-specific split, shares-versus-Dives-versus-apps choice, region/compliance handling, and provisioning starters
Runnable Artifact
artifacts/client_delivery_example.py-- MotherDuck-backed Python example showing one database namespace per client and a simple validation pass across client environmentsartifacts/client_delivery_example.ts-- TypeScript companion artifact with the same delivery output contract
Run it with:
uv run --with duckdb python skills/motherduck-partner-delivery/artifacts/client_delivery_example.py
Run the same artifact against temporary MotherDuck databases:
MOTHERDUCK_ARTIFACT_USE_MOTHERDUCK=1 \
uv run --with duckdb python skills/motherduck-partner-delivery/artifacts/client_delivery_example.py
Validate the TypeScript companion artifact:
uv run scripts/test_typescript_artifacts.py
Related Skills
motherduck-connect-- standardize the connection pathmotherduck-explore-- inspect existing client workspaces and boundariesmotherduck-model-data-- design client-specific schemasmotherduck-query-- validate core metrics and data contractsmotherduck-share-data-- publish governed share boundariesmotherduck-create-dive-- create repeatable client-facing answer surfaces when needed
Related Skills
motherduckdb/motherduck-create-flight
development
VerifiedTrustedCommunity
Create, schedule, run, and debug MotherDuck Flights — Python jobs that run on MotherDuck compute. Use whenever someone wants to create a flight, schedule a Python script or recurring job on MotherDuck, set up scheduled ingestion from Postgres, dlt sources, S3, BigQuery, Snowflake, or APIs, refresh aggregates or transformations on a cron, or operate flights with get_flight_guide, create_flight, run_flight, flight logs, secrets, schedules, and versions.
30SKILL.mdUpdated Jun 11, 2026
motherduckdb/motherduck-create-flight
development
VerifiedTrustedCommunity
Create, schedule, run, and debug MotherDuck Flights — Python jobs that run on MotherDuck compute. Use whenever someone wants to create a flight, schedule a Python script or recurring job on MotherDuck, set up scheduled ingestion from Postgres, dlt sources, S3, BigQuery, Snowflake, or APIs, refresh aggregates or transformations on a cron, or operate flights with get_flight_guide, create_flight, run_flight, flight logs, secrets, schedules, and versions.
30SKILL.mdUpdated Jun 11, 2026
motherduckdb/motherduck-share-data
data-ai
VerifiedTrustedCommunity
Create and manage MotherDuck data shares for zero-copy, read-only data distribution. Use whenever someone wants to share a database with team members, another organization, or the public — covers CREATE SHARE, access/visibility/update modes, GRANT READ ON SHARE, attaching share URLs, UPDATE SHARE, and REFRESH DATABASE.
30SKILL.mdUpdated May 7, 2026
motherduckdb/motherduck-security-governance
development
VerifiedTrustedCommunity
Explain MotherDuck security, governance, and access-control patterns. Use for any question about SOC 2, GDPR, compliance, data residency, regions, SSO, service accounts, token handling, tenant isolation, sharing boundaries, snapshots and recovery, or governance posture — including when a security_compliance_owner, technical_owner, or application_builder is evaluating MotherDuck.
30SKILL.mdUpdated May 7, 2026