Install any skill in seconds. Free to start, no credit card required.
Get Started Free →julialang/ci-timing
Compare a Julia PR's Buildkite job durations against recent CI history (per-job mean/min/max over the last N days).
Passed 16 of 19 test cases with the skill, and 8 of 19 without it.
and 10 more in the full report
11 fixed10 passed either way3 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 8 test cases the skill fixed. Same model, same prompt, with and without the skill.
In what default order are CI jobs listed in the markdown table produced by contrib/ci-timing/ci_timing_compare.jl?
| Checked | Without skill | With skill |
|---|---|---|
| States that the table orders jobs starting with the slowest job first | Missed | Passed |
The instructions your model reads when the skill loads.
julia --startup-file=no --project=contrib/ci-timing contrib/ci-timing/ci_timing_compare.jl <PR-number>
Prints a markdown table, slowest job first, plus a TOTAL row: each job's duration
in the PR's julia-pr build vs. the mean/min/max of the same job name over the
last 7 days of julia-ci-timing
history. ⚠️ = above the weekly max, ✅ = below the weekly min. No Buildkite
token needed; gh is only needed to turn a PR number into a build.
Flags: --build julia-pr/853, --days N, --include-failed, --min-seconds N
(hides short jobs).
Caveats when reading it:
juliasyntax/Launch * jobs are seconds long, so their percentages are noise;
--min-seconds 120 drops them.For logs behind a slow or failed job, see the buildkite-logs skill.
test cases passed, vs 8 / 19 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.