orchestra-skills

Diagnose 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 "triage my pipeline", "show me what's broken", "investigate but don't fix yet", "prepare a fix for review", or when the user explicitly wants a review gate before applying changes. Also trigger when the user describes a symptom in a downstream system ("dashboard looks wrong", "chart is stale", "dbt model has bad data") even if no pipeline error exists — the skill will trace the symptom upstream.

Retrofits 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. Use when setting up Orchestra Slim CI, dbt CI/CD in Orchestra, run-pipeline for dbt, or latest_production defer state in a dbt repo or from outside it.

examine the data we have inside snowflake and based on this, build and deploy a testing pipeline and deploy it to orchestra

Create, validate, and remediate Orchestra pipeline YAML files. 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 dbt task", "write orchestra yaml", "fix validate errors", or when editing files under orchestra/ or similar pipeline directories.

Automatically diagnose and fix failed Orchestra data pipelines. Use this skill whenever a user mentions Orchestra pipeline failures, broken pipelines, pipeline errors, task failures, pipeline debugging, or wants to understand why an Orchestra pipeline run failed. Also trigger when the user says things like "fix my pipeline", "what's broken", "why did my pipeline fail", "debug this run", "retry my pipeline", or references Orchestra pipeline runs, task runs, or pipeline errors. This skill handles the full lifecycle: identify failures, fetch logs and artifacts, diagnose the root cause, apply fixes where possible, retry, and learn from past fixes. It supports all Orchestra integrations including dbt, Snowflake, Python, HTTP, Fivetran, Airbyte, and more. Trigger this skill even if the user just pastes an Orchestra error message, pipeline run URL, pipeline run link from the Orchestra UI, a UUID, a Slack alert, or a pipeline name/alias.