Agent skill · posthog
depot-ci
Configures and manages Depot CI, a drop-in replacement for GitHub Actions that runs workflows entirely within Depot. Use when migrating GitHub Actions workflows to Depot CI, running `depot ci migrate`, managing Depot CI secrets and variables, running workflows with `depot ci run`, debugging Depot CI runs with `depot ci run list`, `depot ci status`, `depot ci logs`, `depot ci diagnose`, or `depot ci ssh`, inspecting test results with `depot tests` or run artifacts with `depot ci artifacts`, checking workflow compatibility, or understanding Depot CI capabilities. Also use when the user mentions .depot/ directory, depot ci commands, or asks about running GitHub Actions workflows on Depot's infrastructure without GitHub-hosted runners. Also use when comparing what Depot CI and GitHub Actions report for a skipped, empty-matrix or continue-on-error job, or when working out whether a check run satisfies a required status check or a merge queue.
What it needs
About 11k tokens when loaded.
What this skill does
Depot CI Depot CI is a programmable CI system for engineers and agents. Workflows in Depot CI run entirely on Depot compute with built-in job visibility, debuggability, and control. GitHub Actions is the first syntax Depot CI supports: migrate your existing GitHub Actions workflows, and get fast, reliable runs on optimized infrastructure. This SKILL.md covers the core workflow plus the most common commands. Detailed flag tables, JSON output shapes, and less-common commands live in three reference files under references/, pointed to from the relevant sections below. Load a reference file only when you need detail it points to. <!-- PostHog-local section. Keep it when resyncing from upstream; see UPSTREAM.md. --> PostHog addition: read references/posthog-check-run-semantics.md before you reason about what a Depot CI run reports to GitHub. It covers what Depot CI and GitHub Actions each post for a skipped, empty-matrix or continue-on-error job, how GitHub and the Trunk merge queue score those conclusions, and how the two engines differ on check naming and reruns. This repo runs Depot CI workflows out of .depot/workflows/ alongside GitHub Actions, so both engines report on the same commit. <!-- End PostHog-local section. --> Architecture Three subsystems: compute (provisions and executes work), orchestrator (schedules multi-step workflows, handles dependencies), GitHub Actions parser (translates Actions YAML into orchestrator workflows). The system is fully programmable. Common flags Nearly every depot ci command (and depot tests) accepts: --org <id>: organization ID, required when the user belongs to multiple organizations (see Org Context Check below). --token <token>: Depot API token. -o, --output json: machine-readable output, useful for agents and scripting. Most depot ci subcommands accept the -o shorthand, but depot tests, depot ci secrets, and depot ci vars accept only the long --output form. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills posthog/depot-ci