step-analysis

Diagnose skipped or unexpected Buildkite pipeline steps using MCP tools.

Updated Jan 19, 2026
One-click install
npx skills add https://github.com/mcncl/skill-buildkite --skill step-analysis
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: step-analysis
Source: https://github.com/mcncl/skill-buildkite/tree/main/skills/step-analysis
Command: npx skills add https://github.com/mcncl/skill-buildkite --skill step-analysis

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Explains why Buildkite pipeline steps were skipped, didn't run, or behaved unexpectedly.

Core Features & Use Cases

  • Retrieve and inspect build and pipeline states to identify why a step did not run.
  • Correlate step outcomes with dependencies and conditions to explain failures.
  • Provide actionable guidance to resolve skipped or blocked steps in future runs.

Quick Start

Ask for an explanation of why a specific Buildkite step was skipped or did not run.

Frequently Asked Questions about step-analysis

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

FAQPage Schema
How do I analyze Buildkite pipeline logs to find out why a step was skipped?

To analyze Buildkite pipeline logs for skipped steps, retrieve and inspect build and pipeline states to identify why a step did not run. Correlating step outcomes with dependencies and conditions explains failures and identifies root causes.

Why does my Buildkite step not run when dependencies are met?

Your Buildkite step might not run due to unmet dependency rules or blocking conditions. Analyzing the pipeline configuration and correlating it with the specific build state determines why the step was skipped or did not execute.

What is the best way to debug an unexpectedly skipped Buildkite step?

The best way to debug a skipped Buildkite step is to fetch state data and read logs to determine root causes. Inspecting step dependencies and correlating outcomes with pipeline conditions provides actionable guidance.

Can I diagnose specific Buildkite builds to explain why steps behaved unexpectedly?

Yes, you can diagnose specific Buildkite builds to explain why steps behaved unexpectedly. The analysis applies to diagnosing specific builds, steps, and their dependencies across pipelines and projects to find root causes.

How do I get actionable guidance to resolve blocked Buildkite steps in future runs?

To get actionable guidance for resolving blocked Buildkite steps, analyze the pipeline state and step dependencies. This process identifies why steps did not run and provides specific recommendations to fix future pipeline executions.