By buildkite
Manage Buildkite CI/CD pipelines end-to-end: create, debug, and convert pipeline configurations; run builds locally; orchestrate job steps with agent commands; and automate via API and CLI.
Runs Buildkite CI builds against changes in the local working tree. Use when asked to run preflight or run CI.
This skill should be used when the user asks to "add an annotation", "upload artifacts from a step", "share data between steps", "upload pipeline dynamically", "request an OIDC token inside a step", "acquire a distributed lock", "get or update a step attribute", "redact a secret from logs", "retrieve a cluster secret at runtime", or "debug environment variables in hooks". Also use when the user mentions buildkite-agent annotate, buildkite-agent artifact upload/download, buildkite-agent meta-data set/get, buildkite-agent pipeline upload, buildkite-agent oidc request-token, buildkite-agent step, buildkite-agent lock, buildkite-agent env, buildkite-agent secret get, buildkite-agent redactor add, buildkite-agent tool sign/keygen, or any buildkite-agent subcommand used inside a running job step.
This skill should be used when the user asks to "call the Buildkite API", "use the REST API", "write a GraphQL query", "set up webhooks", "automate Buildkite", "integrate with Buildkite programmatically", "write a script that calls Buildkite", "handle webhook events", "paginate API results", or "authenticate with the Buildkite API". Also use when the user mentions api.buildkite.com, graphql.buildkite.com, Buildkite REST endpoints, GraphQL mutations, webhook payloads, API tokens, or asks about programmatic access to Buildkite data.
This skill should be used when the user asks to "trigger a build", "check build status", "watch a build", "view build logs", "rebuild a build", "cancel a build", "list builds", "download artifacts", "manage secrets", "create a pipeline", "list pipelines", or "interact with Buildkite from the command line". Also use when the user mentions bk commands, bk build, bk job, bk pipeline, bk secret, bk artifact, bk cluster, bk package, bk auth, bk configure, bk use, bk init, bk api, or asks about Buildkite CLI installation, terminal-based Buildkite workflows, or command-line CI/CD operations.
This skill should be used when the user asks to "migrate to Buildkite", "convert pipelines from Jenkins", "convert GitHub Actions workflows", "convert CircleCI config", "convert Bitbucket Pipelines", "convert GitLab CI", "migrate CI/CD to Buildkite", "switch from Jenkins to Buildkite", "move from GitHub Actions", "plan a CI migration", "convert my CI config", "bk pipeline convert", or "what's the Buildkite equivalent of". Also use when the user mentions migration planning, CI conversion, pipeline conversion, converting workflows, or asks about translating CI/CD configuration from another provider to Buildkite.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
The official Buildkite skills for Claude Code, Cursor, and other AI coding
agents. Install them into your agent of choice so it can generate correct
pipeline YAML, run bk and buildkite-agent CLI commands, call the API,
configure agents, and run preflight builds.
npx skills add buildkite/skills
See skills.sh for supported agents and options.
Search for Buildkite Skills in the Cursor Marketplace, or run /add-plugin and search for "Buildkite".
Recommended (one install): add the Buildkite power in the Powers panel, pointing at
github.com/buildkite/skills. The root POWER.md, mcp.json, and steering/
together give Kiro the Buildkite MCP server plus all six workflows (pipelines,
migration, preflight, agent-runtime, CLI, API), loaded automatically when relevant.
Alternatively, install individual workflows as Kiro skills via the Skills panel —
each skills/buildkite-*/ directory already conforms to the open Agent Skills standard.
Copy skill directories into your agent's skills folder:
# Claude Code
mkdir -p .claude/skills
cp -r skills/buildkite-pipelines .claude/skills/
cp -r skills/buildkite-preflight .claude/skills/
cp -r skills/buildkite-agent-runtime .claude/skills/
cp -r skills/buildkite-cli .claude/skills/
cp -r skills/buildkite-api .claude/skills/
cp -r skills/buildkite-migration .claude/skills/
# Cursor
mkdir -p .cursor/skills
cp -r skills/buildkite-pipelines .cursor/skills/
cp -r skills/buildkite-preflight .cursor/skills/
cp -r skills/buildkite-agent-runtime .cursor/skills/
cp -r skills/buildkite-cli .cursor/skills/
cp -r skills/buildkite-api .cursor/skills/
cp -r skills/buildkite-migration .cursor/skills/
Skills organized by what you are trying to accomplish.
| Skill | Directory | Description |
|---|---|---|
| Pipelines | skills/buildkite-pipelines/ | Pipeline YAML, step types, plugins, caching, parallelism, dynamic pipelines, matrix builds, artifacts, hooks |
| Migration | skills/buildkite-migration/ | CI migration planning, converting from GitHub Actions, Jenkins, CircleCI, Bitbucket Pipelines, GitLab CI using bk pipeline convert |
Skills needed across all journeys.
| Skill | Directory | Description |
|---|---|---|
| Preflight | skills/buildkite-preflight/ | bk preflight runs a CI build against local uncommitted changes |
| Agent Runtime | skills/buildkite-agent-runtime/ | buildkite-agent subcommands inside running job steps — annotate, artifact, meta-data, pipeline upload, OIDC, locks |
| CLI | skills/buildkite-cli/ | bk commands for builds, jobs, pipelines, secrets, artifacts, and auth |
| API | skills/buildkite-api/ | REST API, GraphQL API, webhooks, authentication, pagination |
Buildkite docs at buildkite.com/docs are the canonical reference for what Buildkite features exist and how they work.
Skills serve a different purpose: they encode expertise. Where docs explain every option, skills teach agents the right defaults, common patterns, and mistakes to avoid. A skill captures the judgment an experienced Buildkite user applies — which step type to reach for, how to structure a dynamic pipeline, when to use OIDC instead of static tokens.
In practice this means:
references/ subdirectories, loaded only when neededFor more on content strategy, see CONVENTIONS.md.
skills/buildkite-pipelines/SKILL.md)Full Buildkite docs at buildkite.com/docs.
npx claudepluginhub buildkite/skills --plugin buildkiteBuild CI/CD pipelines for GitHub Actions, GitLab CI, Jenkins, and more
DevOps and deployment automation - CI/CD pipelines, zero-downtime deployments - 1 skill, 2 commands, 2 agents
Debug CI/CD pipeline failures and fix configurations
Commands for CI/CD setup, containerization, and deployment automation
Harness CD integration pipeline with state-machine workflow orchestration
Use this agent when setting up CI/CD pipelines, configuring cloud infrastructure, implementing monitoring systems, or automating deployment processes. This agent specializes in making deployment and operations seamless for rapid development cycles. Examples:\n\n<example>\nContext: Setting up automated deployments\nuser: "We need automatic deployments when we push to main"\nassistant: "I'll set up a complete CI/CD pipeline. Let me use the devops-automator agent to configure automated testing, building, and deployment."\n<commentary>\nAutomated deployments require careful pipeline configuration and proper testing stages.\n</commentary>\n</example>\n\n<example>\nContext: Infrastructure scaling issues\nuser: "Our app crashes when we get traffic spikes"\nassistant: "I'll implement auto-scaling and load balancing. Let me use the devops-automator agent to ensure your infrastructure handles traffic gracefully."\n<commentary>\nScaling requires proper infrastructure setup with monitoring and automatic responses.\n</commentary>\n</example>\n\n<example>\nContext: Monitoring and alerting setup\nuser: "We have no idea when things break in production"\nassistant: "Observability is crucial for rapid iteration. I'll use the devops-automator agent to set up comprehensive monitoring and alerting."\n<commentary>\nProper monitoring enables fast issue detection and resolution in production.\n</commentary>\n</example>