Menu
Use the bkci CLI to query Buildkite builds, logs, artifacts, and token scope status with LLM-friendly JSON output.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | buildkite-cli |
| description | Use the bkci CLI to query Buildkite builds, logs, artifacts, and token scope status with LLM-friendly JSON output. |
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.
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
Set one of these env vars before calling bkci:
BUILDKITE_TOKENBUILDKITE_API_TOKENBK_TOKENIf no env token is set, auth can be configured interactively:
bkci auth setup
This writes ~/.config/buildkite-cli/auth.json with strict permissions.
bkci auth setup automatically.bkci auth status reports missing token/auth, stop and ask the user to run auth setup manually.Required scopes:
read_buildsread_build_logsread_artifactsValidate token/scopes first:
bkci auth status
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
bkci always returns a stable top-level JSON envelope:
okapiVersioncommandrequestsummarypaginationdataerrorUse --raw to keep exact Buildkite payloads in data.
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 buildjobs log get for relevant job IDsartifacts list / artifacts downloadannotations listStructured workflow for investigating public software supply-chain attacks across local repositories, GitHub organizations, and CI/host fleets. Use when asked to assess exposure to compromised packages, malicious releases, package-manager attacks, GitHub Actions/OIDC abuse, or published IOC lists.
Multi-model code review. Runs code-review skill with 2 models in parallel, then synthesizes findings.
Multi-agent workflow (tracer/resolver/bypass) for secure code review, exploitability triage, and PoC validation in codebases. Use when conducting structured security research or penetration test analysis.
Send a desktop notification when pi finishes a task. Works on macOS, Windows, and Linux. On first use, interactively asks the user to choose a notification preference (always, ask every time, or never) via arrow-key selector. Use this skill at the end of every task completion — after committing, after finishing a code change, after answering a question, or any other unit of work.
Search a specific GitHub repository for code using gh search and fetch file contents via gh api without cloning. Use when given a repo URL and query to locate logic in remote repos.
Analyze Playwright test logs on Buildkite to extract failed-only tests across jobs.