account-health-checkAudit an Orchestra workspace/account against Orchestra's best practices and produce a read-only health report — findings grouped by area, each tagged with severity, evidence, and a fix recommendation, written to a markdown file plus a chat summary. Use whenever the user wants an "account review", "w
build-data-reconciliation-pipelineBuilds Orchestra pipeline YAML using the native Data Reconciliation tasks (DATA_RECONCILIATION_MANUAL_QUERY, DATA_RECONCILIATION_CURSOR_FIELD) to prove two data stores match — the "did the migration land correctly" check between a source and destination integration (SNOWFLAKE, SQL_SERVER, DATABRICKS
configure-dbt-build-afterConfigure dbt model build_after for Orchestra state-aware orchestration — author the config.freshness.build_after block (count, period, updates_on) on dbt models so Orchestra rebuilds a model only after a minimum SLA window AND when its upstream data is fresh, then ensure use_state_orchestration is
configure-dbt-source-freshnessConfigure dbt source freshness for Orchestra state-aware orchestration — author warn_after/error_after thresholds and loaded_at_field/loaded_at_query in a dbt project's sources YAML, getting the warehouse details right for Snowflake, BigQuery, Databricks, or MotherDuck/DuckDB, then enable use_state_
create-orchestra-pipelineCreate, validate, and remediate Orchestra pipeline definitions, as YAML or OML. Use when asked to build a new pipeline, add tasks to an existing pipeline, fix pipeline validation errors, or author Orchestra workflow definitions from a description. Trigger on phrases like "create a pipeline", "add a
databricks-cost-auditRuns a daily, one-off Databricks cost-optimisation audit. Executes 10 checks against Databricks system tables (billing, compute, query history, lakeflow), writes ranked findings with estimated $ savings to a Delta table, and returns a summary highlighting what's new today vs. still-open. Use when th
databricks-cost-driversRank Databricks jobs and pipelines by cost/runtime and surface the biggest cost drivers, with trend direction. Use when the user asks what's costing the most in Databricks, which jobs got more expensive, or wants a weekly/ monthly cost review.
fix-orchestra-pipelineFix a failed Orchestra pipeline once the failure has been identified as an Orchestra-platform / configuration issue — pipeline YAML misconfiguration, wrong or missing task inputs, task ordering, env/connection wiring, a transient Orchestra-side blip needing a plain retry, or an Orchestra-backed pipe
fix-pipeline-dbt-taskFix a dbt Core task in an Orchestra Pipeline once the failure has been identified as a dbt code/config issue. Normally invoked by identify-pipeline-error after it classifies the cause; it can also run standalone if the user points directly at a broken dbt task. Succinct, API-first workflow refined f
fix-pipeline-python-taskFix a Python task in an Orchestra Pipeline once the failure has been identified as a Python code / dependency / destination-schema issue. Normally invoked by identify-pipeline-error after it classifies the cause; it can also run standalone if the user points directly at a broken Python task. Succinc
identify-pipeline-errorThe entry point for fixing anything in an Orchestra pipeline. Use this skill FIRST whenever a user wants to fix, debug, retry, or understand a failed Orchestra pipeline — e.g. "fix my pipeline", "what's broken", "why did my pipeline fail", "debug this run", "retry it" — or pastes an Orchestra run UR
merge-duplicate-pipelinesFinds Orchestra pipelines that are really the same process duplicated — across environments (`_prod`/`_staging`/`_dev`/`-uat` naming, or Orchestra's native Environments) or conceptually (same task graph copy-pasted per customer/region/business-unit under unrelated names) — then drafts one consolidat
orchestra-dbt-slim-ci-setupRetrofits dbt Slim CI onto an existing Orchestra production dbt pipeline using latest_production, state:modified+, and --defer, with GitHub Actions run-pipeline as the primary CI trigger. Audits the account for earlier or partial attempts first and proposes consolidation. Use when setting up Orchest
setup-incident-slack-summarySet up a scheduled Orchestra pipeline that has an agent summarise the workspace's incidents (filtered by status, severity, name and a lookback window) and post them to a Slack channel as a formatted table. Use whenever someone asks to "Setup Scheduled Incident Slack Summary Pipeline", wants a weekly
triage-orchestra-pipelineDiagnose a failed Orchestra pipeline, open a fix PR, validate it on a branch run, then present a human-readable triage summary and STOP for user approval before merging. Use this when the user wants to review the fix before it goes to main — not for fully automated fixes. Trigger on phrases like "tr
write-bigquery-dq-testsProfile BigQuery data, design data-quality tests appropriate to what each column actually is, then build and deploy a BigQuery DQ testing pipeline to Orchestra.
write-clickhouse-dq-testsProfile ClickHouse data, design data-quality tests appropriate to what each column actually is, then build and deploy a ClickHouse DQ testing pipeline to Orchestra.
write-databricks-dq-testsProfile Databricks data, design data-quality tests appropriate to what each column actually is, then build and deploy a Databricks DQ testing pipeline to Orchestra.
write-snowflake-dq-testsProfile Snowflake data, design data-quality tests appropriate to what each column actually is, then build and deploy a Snowflake DQ testing pipeline to Orchestra.