using-buildkite

Queries Buildkite Pipelines and Test Engine APIs for build statuses, failed jobs/job logs, and failed test executions/traces via bk CLI and BUILDKITE_API_TOKEN.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/blaknite/agent-skills --skill using-buildkite
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: using-buildkite
Source: https://github.com/blaknite/agent-skills/tree/main/using-buildkite
Command: npx skills add https://github.com/blaknite/agent-skills --skill using-buildkite

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you interact with Buildkite to check build statuses, debug failures by examining job logs, and analyze test results from the Test Engine API.

Core Features & Use Cases

  • Build Status: Quickly get the status of the latest or a specific build on a branch.
  • Job Analysis: List all jobs within a build, filter for failed or running jobs, and retrieve their logs.
  • Test Engine: Query the Test Engine API for failed test executions and traces.
  • Use Case: When a build fails, use this Skill to pinpoint the exact job that failed, view its logs, and identify the root cause of the failure.

Quick Start

Use the using-buildkite skill to get the status of the latest build on the 'main' branch for the 'my-org/my-pipeline' pipeline.

Frequently Asked Questions about using-buildkite

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check Buildkite build status for a specific branch?

To check Buildkite build status, you can query the Buildkite Pipelines API to retrieve the status of the latest or a specific build on a designated branch. This allows you to monitor CI/CD pipelines and verify build results directly.

How do I debug failed Buildkite jobs and retrieve their logs?

Debugging failed Buildkite jobs involves listing all jobs within a build, filtering for the failed ones, and retrieving their specific logs. This isolates the exact job that failed and exposes its logs to identify the root cause of the failure.

Can I analyze failed test executions and traces using the Buildkite Test Engine API?

Yes, you can analyze failed test executions and traces by querying the Buildkite Test Engine API. This requires a BUILDKITE_API_TOKEN environment variable to access the Test Engine and investigate test failures.

Do I need the bk CLI and an API token to query Buildkite test results?

Yes, accessing Buildkite test results requires the bk CLI installed and a BUILDKITE_API_TOKEN environment variable configured. These prerequisites authenticate your session and enable Test Engine API queries for failed test traces.

What is the best way to identify the root cause of a CI/CD build failure in Buildkite?

The best way to identify a CI/CD build failure root cause is to use Buildkite to pinpoint the exact failed job, view its logs, and analyze the Test Engine traces. This isolates the specific failure point and provides detailed execution data.