How do I install the Buildkite CLI skill?

Run npx skillmds@latest add pspdfkit-labs/buildkite-cli in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Buildkite CLI safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Buildkite CLI?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Buildkite CLI free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Buildkite CLI?

pspdfkit-labs (@pspdfkit-labs) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Buildkite CLI by pspdfkit-labs — Agent Skill

Name: Buildkite CLI
Author: pspdfkit-labs

File contents

Buildkite CLI (`bkci`)

Use this skill when you want CI data from Buildkite through the bkci utility.

This is a good default when you need structured JSON output that is easy for agents to parse.

Install from local checkout

For now, install from a local clone and link it:

git clone https://github.com/PSPDFKit-labs/buildkite-cli <buildkite-cli-dir>
cd <buildkite-cli-dir>
pnpm install
pnpm run build
npm link

Verify:

bkci --help

After pulling updates, rebuild:

pnpm run build

Authentication

Set one of these env vars before calling bkci:

BUILDKITE_TOKEN
BUILDKITE_API_TOKEN
BK_TOKEN

If no env token is set, auth can be configured interactively:

bkci auth setup

This writes ~/.config/buildkite-cli/auth.json with strict permissions.

Agent safety rule

Do not run bkci auth setup automatically.
If bkci auth status reports missing token/auth, stop and ask the user to run auth setup manually.
Do not pass token values in command arguments unless the user explicitly requests it.

Required scopes:

read_builds
read_build_logs
read_artifacts

Validate token/scopes first:

bkci auth status

Common commands

List builds:

bkci builds list --org ORG --pipeline PIPELINE --per-page 10

Get one build with jobs:

bkci builds get --org ORG --pipeline PIPELINE --build BUILD_NUMBER

Fetch one job log (cleaned output):

bkci jobs log get --org ORG --pipeline PIPELINE --build BUILD_NUMBER --job JOB_ID --tail-lines 400 --max-bytes 250000

List artifacts:

bkci artifacts list --org ORG --pipeline PIPELINE --build BUILD_NUMBER

Download artifact(s):

bkci artifacts download --org ORG --pipeline PIPELINE --build BUILD_NUMBER --artifact-id ARTIFACT_ID --out /tmp/bk-artifacts

List annotations:

bkci annotations list --org ORG --pipeline PIPELINE --build BUILD_NUMBER

Output contract

bkci always returns a stable top-level JSON envelope:

ok
apiVersion
command
request
summary
pagination
data
error

Use --raw to keep exact Buildkite payloads in data.

Recommended usage pattern

auth status (if this fails due to missing token/scopes, ask user to fix auth before continuing)
builds list (optionally filtered by --pipeline, --branch, --state)
builds get for the selected build
jobs log get for relevant job IDs
artifacts list / artifacts download
annotations list

---name: buildkite-clidescription: Use the bkci CLI to query Buildkite builds, logs, artifacts, and token scope status with LLM-friendly JSON output.---# Buildkite CLI (`bkci`)Use this skill when you want CI data from Buildkite through the `bkci` utility.This is a good default when you need structured JSON output that is easy for agents to parse.## Install from local checkoutFor now, install from a local clone and link it:```bashgit clone https://github.com/PSPDFKit-labs/buildkite-cli <buildkite-cli-dir>cd <buildkite-cli-dir>pnpm installpnpm run buildnpm link```Verify:```bashbkci --help```After pulling updates, rebuild:```bashpnpm run build```## AuthenticationSet one of these env vars before calling `bkci`:- `BUILDKITE_TOKEN`- `BUILDKITE_API_TOKEN`- `BK_TOKEN`If no env token is set, auth can be configured interactively:```bashbkci auth setup```This writes `~/.config/buildkite-cli/auth.json` with strict permissions.### Agent safety rule- Do **not** run `bkci auth setup` automatically.- If `bkci auth status` reports missing token/auth, stop and ask the user to run auth setup manually.- Do **not** pass token values in command arguments unless the user explicitly requests it.Required scopes:- `read_builds`- `read_build_logs`- `read_artifacts`Validate token/scopes first:```bashbkci auth status```## Common commandsList builds:```bashbkci builds list --org ORG --pipeline PIPELINE --per-page 10```Get one build with jobs:```bashbkci builds get --org ORG --pipeline PIPELINE --build BUILD_NUMBER```Fetch one job log (cleaned output):```bashbkci jobs log get --org ORG --pipeline PIPELINE --build BUILD_NUMBER --job JOB_ID --tail-lines 400 --max-bytes 250000```List artifacts:```bashbkci artifacts list --org ORG --pipeline PIPELINE --build BUILD_NUMBER```Download artifact(s):```bashbkci artifacts download --org ORG --pipeline PIPELINE --build BUILD_NUMBER --artifact-id ARTIFACT_ID --out /tmp/bk-artifacts```List annotations:```bashbkci annotations list --org ORG --pipeline PIPELINE --build BUILD_NUMBER```## Output contract`bkci` always returns a stable top-level JSON envelope:- `ok`- `apiVersion`- `command`- `request`- `summary`- `pagination`- `data`- `error`Use `--raw` to keep exact Buildkite payloads in `data`.## Recommended usage pattern1. `auth status` (if this fails due to missing token/scopes, ask user to fix auth before continuing)2. `builds list` (optionally filtered by `--pipeline`, `--branch`, `--state`)3. `builds get` for the selected build4. `jobs log get` for relevant job IDs5. `artifacts list` / `artifacts download`6. `annotations list`

Frequently asked questions

Buildkite CLI