motherduckdb/agent-skills / plugins/motherduck-skills-claude/skills/motherduck-build-data-pipeline
motherduck-build-data-pipeline
UnverifiedBuild ingestion-to-serving pipelines on MotherDuck, including stage boundaries, transformations, and publication. Use for any recurring ingestion from an API, SaaS app, or database into MotherDuck.
references/dlt-dbt-motherduck-project/pipeline/validate.py
View on GitHubfrom __future__ import annotations
from datetime import date
from decimal import Decimal
import duckdb
if __package__ in (None, ""):
import sys
from pathlib import Path
sys.path.append(str(Path(__file__).resolve().parents[1]))
from pipeline.settings import USER_AGENT, load_settings
EXPECTED_SUMMARY = [
("c1", "Acme Rockets", "enterprise", "north_america", 2, Decimal("155.00"), date(2026, 1, 12)),
("c2", "Birch Analytics", "mid_market", "emea", 1, Decimal("75.00"), date(2026, 1, 14)),
("c3", "Cedar Logistics", "enterprise", "apac", 1, Decimal("200.00"), date(2026, 1, 20)),
]
def validate_pipeline() -> None:
settings = load_settings()
database = f'"{settings.database}"'
conn = duckdb.connect(
f"md:{settings.database}",
config={
"motherduck_token": settings.token,
"custom_user_agent": USER_AGENT,
},
)
try:
counts = conn.sql(
f"""
SELECT
(SELECT count(*) FROM {database}."raw"."customers_raw") AS raw_customers,
(SELECT count(*) FROM {database}."raw"."orders_raw") AS raw_orders,
(SELECT count(*) FROM {database}."staging"."stg_orders") AS staged_orders,
(SELECT count(*) FROM {database}."analytics"."fct_customer_revenue") AS mart_rows
"""
).fetchone()
assert counts == (3, 6, 4, 3), counts
summary = conn.sql(
f"""
SELECT
customer_id,
customer_name,
segment,
region,
order_count,
total_amount,
last_order_date
FROM {database}."analytics"."fct_customer_revenue"
ORDER BY customer_id
"""
).fetchall()
assert summary == EXPECTED_SUMMARY, summary
finally:
conn.close()
print("Validation passed.")
for row in EXPECTED_SUMMARY:
print(row)
if __name__ == "__main__":
validate_pipeline()
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |