AgentStack
SKILL verified MIT Self-run

Orchestra Dbt Slim Ci Setup

skill-orchestra-hq-orchestra-skills-orchestra-dbt-slim-ci-setup · by orchestra-hq

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.

No reviews yet
0 installs
16 views
0.0% view→install

Install

$ agentstack add skill-orchestra-hq-orchestra-skills-orchestra-dbt-slim-ci-setup

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

Are you the author of Orchestra Dbt Slim Ci Setup? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Orchestra dbt Slim CI setup

Retrofit Slim CI onto an existing production dbt Orchestra pipeline (one pipeline for prod and CI). Generate or patch repo artifacts, validate pipeline YAML, and leave a verification checklist. Do not assume warehouse or Git connections can be created via API.

When to use

  • User asks to set up Slim CI, dbt CI/CD in Orchestra, or run-pipeline for dbt PR checks.
  • Workspace is a dbt repo or user supplies dbt repo paths and pipeline YAML location.
  • Default scope: retrofit an existing production pipeline; do not create a separate CI-only pipeline unless the user opts out of shared latest_production.

Companion skill

After setup, failed PR checks: use pr-slim-ci-orchestra-debug (project or org copy). Do not merge debug steps into this skill.

Workflow

  1. Collect inputs — Follow [references/inputs-matrix.md](references/inputs-matrix.md). Ask for must-haves; discover from repo when in a dbt project.
  2. Detect context — In dbt repo: read dbt_project.yml, profiles.yml, orchestra/, .github/workflows/. Outside: require repo URL, pipeline YAML path, and where GHA lives. If already configured per Orchestra docs, report and run verification only.
  3. Load Orchestra docs — Follow [references/orchestra/mcp-playbook.md](../../references/orchestra/mcp-playbook.md) (Orchestra Documentation MCP, then Orchestra MCP).
  4. Inventory pipelinelist_pipelines; read YAML. Checklist: [references/retrofit-checklist.md](references/retrofit-checklist.md).
  5. Patch pipeline YAML — Minimal changes from [templates/pipeline-inputs-snippet.yml](templates/pipeline-inputs-snippet.yml). Git-backed: commit YAML; do not use update_pipeline. Orchestra-backed only: validate_pipeline then create_pipeline / update_pipeline.
  6. GitHub Actions — Add or patch workflow from [templates/github-dbt-slim-ci.yml](templates/github-dbt-slim-ci.yml). Separate pipeline repo: Action branch = pipeline YAML branch; dbt_branch only in run_inputs.
  7. dbt prerequisites — CI/prod targets in Orchestra connection profiles; excludes in Slim command; bootstrap latest_production (successful prod run on default branch).
  8. Secrets checklist — Document ORCHESTRA_API_KEY, optional pipeline/task id secrets, GHA environment → Orchestra environment mapping. Warehouse creds stay in Orchestra dbt connection.
  9. Validatevalidate_pipeline when definition available; dbt parse when possible. start_pipeline with Slim runInputs only with user approval.
  10. Report — Use [references/completion-report.md](references/completion-report.md).

Guardrails

  • One production pipeline for prod + Slim CI unless user wants isolated artifact history.
  • Do not implement manual S3 manifest export unless user rejects Orchestra latest_production.
  • Do not commit API keys or connection secrets.
  • Do not broaden scope to full pipeline authoring during retrofit.
  • Git-backed vs Orchestra-backed determines commits vs MCP create/update.
  • Cite Orchestra docs via MCP; treat any single repo as a pattern, not universal defaults.

Out of scope

Non-GitHub CI (document start_pipeline MCP tool / CLI as follow-up), new warehouse/Git OAuth setup, Lightdash preview CI, auto-fixing failing Slim CI runs.

Doc index

| Topic | URL | |-------|-----| | CI/CD for dbt Core | https://docs.getorchestra.io/docs/git-control-and-ci-cd/ci-cd/dbtcicd | | GitHub Actions CI/CD | https://docs.getorchestra.io/docs/git-control-and-ci-cd/ci-cd/githubactions | | dbt Core execute | https://docs.getorchestra.io/docs/integrations/dbtcore/dbtcoreexecute | | Pipeline inputs | https://docs.getorchestra.io/docs/core-concepts/variables/inputs | | dbt Core in Orchestra | https://docs.getorchestra.io/docs/guides/dbt-core/orchestra-setup |

Full input matrix and MCP steps: [references/orchestra-slim-ci.md](references/orchestra-slim-ci.md).

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Versions

  • v0.1.0 Imported from the upstream source.