Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →julialang/buildkite-logs
Fetch and inspect Julia Buildkite CI logs without web sign-in.
Passed 16 of 19 test cases with the skill, and 7 of 19 without it.
and 13 more in the full report
10 fixed8 passed either way4 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 10 test cases the skill fixed. Same model, same prompt, with and without the skill.
A commit was recently merged into Julia's master branch, and I want to check its build using Buildkite frontend JSON endpoints. Which pipeline slug corresponds to post-merge master builds in the julialang organization?
| Checked | Without skill | With skill |
|---|---|---|
| Identifies julialang/julia-ci as the pipeline slug for post-merge master builds. | Missed | Passed |
The instructions your model reads when the skill loads.
Use this when investigating Julia Buildkite CI failures, especially if the
Buildkite MCP is unavailable. The recipe requires gh, curl, python3, and
network access to GitHub and Buildkite.
Julia's CI runs on Buildkite. PR builds run in the julialang/julia-pr
pipeline, post-merge master builds in julialang/julia-ci, and scheduled runs
in julialang/julia-master-scheduled (the old julia-master pipeline no
longer exists). The public web UI requires sign-in to download raw_log, but
two frontend JSON endpoints are anonymously accessible for public pipelines.
Recipe:
Find the build number. gh pr checks <PR-number> gives launcher-job URLs
like https://buildkite.com/julialang/julia-pr/builds/<BUILD>#<uuid>; for a
master commit, use the commit statuses
(gh api repos/JuliaLang/julia/commits/<sha>/status). The #<uuid>
fragments there are only the top-level launcher jobs (Build/Check/Test/…),
not the per-platform jobs.
List all jobs in the build, with names, states, exit statuses, and UUIDs:
curl -sS -H "Accept: application/json" \
"https://buildkite.com/julialang/<PIPELINE>/builds/<BUILD>/data/jobs" \
-o /tmp/bkjobs.json
python3 -c "import json; [print(j['state'],'|',j.get('exit_status'),'|',j['name'],'|',j['id']) \
for j in json.load(open('/tmp/bkjobs.json'))['records']]"
This /data/jobs endpoint is what the build page's frontend uses; it
returns every job in one page (records, plus has_next_page). Do NOT use
builds/<BUILD>.json for job discovery — anonymously it returns build
metadata with an empty jobs array (the statistics field still shows
the true job count).
Fetch a job's log JSON (replace <PIPELINE>, <BUILD>, <JOB-UUID>):
curl -sS -H "Accept: application/json" \
test cases passed, vs 7 / 19 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.