Terminal
Terminal/Skill
Build MotherDuck analytics into customer-facing applications with tenant isolation, backend routing, and serving APIs.
By MotherDuck
Works with
npx skills add motherduckdb/agent-skills --skill motherduck-build-cfa-appUse an active remote MotherDuck MCP server or local MotherDuck server to inspect the in-scope database, schema, grain, keys, and relevant metrics. Reuse known context and narrow discovery to the requested work; do not scan the whole workspace by default. Let the actual data model shape the result.
Resolve the target from the request or active context. Ask only if ambiguity materially affects the result. Without a server, use supplied schema and explicit assumptions for planning; do not imply live validation.
postMessage origin/type/payload, use initial_state only for JSON-serializable UI state, and keep navigation, export, and persistence policy in the host application.Match execution to the request: answer, review, or planning work returns the requested architecture artifacts; build or change work creates the requested in-scope files or services and validates them. Ask before destructive actions, external writes not already requested, or a material expansion of scope.
When this skill produces a native DuckDB (md:) connection, watermark it with custom_user_agent=agent-skills/2.6.0(harness-<harness>;llm-<llm>). If metadata is missing, fall back to harness-unknown and llm-unknown.
For a full engagement, cover the following as relevant to the request:
For explicit structured JSON requests, read the output contract. Otherwise use the format that fits the requested deliverable.
Read only the sections relevant to the task; these are guidance, not a mandatory itinerary.
references/CFA_IMPLEMENTATION_GUIDE.md -- backend implementation, service accounts, routing, and read-scaling examplesreferences/CFA_ARCHITECTURE.md -- architecture comparison, isolation model, and connection-path detailRead the execution reference only to run the bundled examples or reproduce their validation.
Load related skills only for missing capabilities; reuse established context.
motherduck-connect -- choose the correct PG endpoint or native DuckDB pathmotherduck-explore -- inspect the live database and schema before choosing an architecturemotherduck-model-data -- design analytics-ready per-customer tablesmotherduck-query -- validate serving queries and latency-sensitive aggregationsmotherduck-load-data -- build ingestion paths for customer-facing data refresh