Fetch CI build results and diagnose failures. Auto-detects provider from project files or URLs. Supports GitHub Actions, Buildkite, and CircleCI.
69
55%
Does it follow best practices?
Impact
92%
1.67xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./tests/ext_conformance/artifacts/agents-mikeastock/skills/fetch-ci-build/SKILL.mdCI provider auto-detection
GitHub detection method
100%
100%
Buildkite detection method
100%
100%
CircleCI detection method
100%
100%
GitHub output uses gh CLI
100%
100%
Buildkite output uses uv run script
0%
100%
CircleCI output uses uv run script
0%
100%
BUILDKITE_API_TOKEN documented
0%
100%
BUILDKITE_ORGANIZATION_SLUG documented
0%
100%
CIRCLECI_TOKEN documented
0%
100%
No circleci CLI for fetching
0%
100%
ci_detect.sh is executable bash
100%
100%
GitHub Actions failure diagnosis
Run ID extracted
100%
100%
Uses --log-failed flag
100%
100%
gh run view command present
100%
100%
Read source files step
40%
100%
Present failure details
100%
100%
Ask user how to proceed
0%
0%
systematic-debugging escalation
0%
0%
Test failure pattern
100%
100%
Lint/build failure pattern
100%
100%
Iterates over multiple failures
100%
50%
No browser-only approach
100%
100%
Buildkite and CircleCI diagnosis
Buildkite uses uv run script
0%
100%
CircleCI uses uv run script
0%
100%
No circleci CLI for fetching
100%
100%
BUILDKITE_API_TOKEN documented
100%
100%
BUILDKITE_ORGANIZATION_SLUG documented
0%
100%
CIRCLECI_TOKEN documented
0%
100%
Buildkite --build flag
100%
100%
Buildkite --branch flag
100%
100%
CircleCI auto-detects project slug
0%
100%
CircleCI --project override
0%
75%
CircleCI --branch flag
100%
100%
47823e3
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.