Agent skill

CI Timing

by wado-lang in wado-lang/wado

Measure how long GitHub Actions jobs and steps took across past runs, and find the pull request that made CI slower.

MITAuto-check passedDevelopment

Install CI Timing

skills CLI
$ npx skills add wado-lang/wado --skill ci-timing -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install wado-lang/wado ci-timing --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/wado-lang/wado.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/ci-timing .claude/skills/ci-timing && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
ci-timing
GitHub stars
117
Token cost
~518 tokens
SKILL.md length
270 words
Files
2
Skills in repo
15
Repo updated
First seen
Licence
MIT

At a glance

Measure how long GitHub Actions jobs and steps took across past runs, and find the pull request that made CI slower.

  • Any question about CI duration
  • SKILL.md covers Find When a Job Got Slower, Find Which Step Grew and Read the Numbers
  • Runs JavaScript scripts from its folder; calls mise
  • Tasks that involve Pull requests

What it does

CI Timing is an agent skill from wado-lang/wado. Measure how long GitHub Actions jobs and steps took across past runs, and find the pull request that made CI slower. Use for any question about CI duration, a slow job, or when CI got slow.

Its SKILL.md is about 520 tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file.

It sits in Development, covering Pull requests and CI/CD. It works with GitHub Actions and WebAssembly. The repository describes itself as: The Wado Programming Language. The licence is MIT.

When your agent uses it

  • Any question about CI duration
  • Tasks that involve Pull requests
  • Tasks that involve CI/CD

Example prompts

  • “/ci-timing”

Requirements

  • Node.js

What it can do on your machine

Read from SKILL.md and the folder at commit 037dba4. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships script files (JavaScript), which the agent can run.

    Shell commands in SKILL.md call:

    • mise

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

CI Timing loads about 518 tokens when it runs. Until then it costs about 50 tokens; SKILL.md has 270 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~50
When it runs · the whole SKILL.md, loaded when a task matches
~518

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from wado-lang/wado at commit 037dba4, republished under its MIT licence (© wado-lang). 270 words, ~518 tokens.

Download SKILL.mdSave it as .claude/skills/ci-timing/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
ci-timing
description
Measure how long GitHub Actions jobs and steps took across past runs, and find the pull request that made CI slower. Use for any question about CI duration, a slow job, or when CI got slow.

CI Timing

ci-times.mjs reads run, job and step timings from the GitHub API with gh. Run it with mise's Node, and redirect its output to a file in scratchpad/: a sweep over a month makes hundreds of API calls.

Find When a Job Got Slower

Sweep the runs on main, one row per run, oldest first:

sh
mise exec -- node .claude/skills/ci-timing/ci-times.mjs \
  --since 2026-09-01 --job 'E2E\+stdlib' --step stdlib \
  > scratchpad/ci-times.tsv

Each matched job prints as name=STEP/JOB in seconds. - means the step did not run or there was no --step. The row ends with the run's title, which names the merged pull request. Look for the row where a job's total steps up and stays up.

Only runs on main from push events give a clean timeline: each one is a single merge. The defaults are --workflow ci.yml --branch main --event push.

Find Which Step Grew

The job total can grow while the step you guessed stays flat. A step that a pull request added is invisible to --step. Print every step of the runs on either side of the jump and compare them:

sh
mise exec -- node .claude/skills/ci-timing/ci-times.mjs --sha <before> --job 'stdlib O3'
mise exec -- node .claude/skills/ci-timing/ci-times.mjs --sha <after>  --job 'stdlib O3'

--run <run id> does the same for a run that is not on main, such as a pull request's run.

Read the Numbers

  • Hosted runners vary from run to run. Several runs on each side of a jump show a real change. A single run does not.
  • The slowest job sets how long CI takes. A step that grew in a job that finishes early does not slow CI down.
  • A test step grows as tests are added. Compare its growth with the growth in the count of what it runs (wado-compiler/tests/fixtures/*.wado, test blocks under wado-compiler/lib/) before calling it a regression.

© wado-lang, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file in .claude/skills/ci-timing of wado-lang/wado.

  • SKILL.md
  • ci-times.mjs

Open the folder on GitHubat commit 037dba4

Compare with similar skills

CI Timing next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

CI Timing compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
CI Timing this skillwado-lang/wado117—~518Automated safety check: PassMIT
Babysit PR To Pass CIsgl-project/sglang37k2 repos~3kAutomated safety check: PassApache-2.0
Ghbubbuild/bub1.7k—~798Automated safety check: PassApache-2.0
Renovate Actions PR Reviewbacknotprop/plannotator9.2k—~640Automated safety check: PassApache-2.0
Submit Aetherkiri Cross Repo PRsAetherKiri/Aether149—~1.9kAutomated safety check: PassGPL-3.0
GitHub PR Actions Fixopenteams-lab/openteams627—~878Automated safety check: PassApache-2.0

Similar skills

  • Babysit PR To Pass CI

    sgl-project/sglang

    Start and persistently pursue a goal to babysit an SGLang pull request until selected GitHub Actions workflows pass on the latest PR head.

    37k GitHub starsUsed in 2 repos~3k tokens
    DevelopmentAuto-check passed
  • Gh

    bubbuild/bub

    GitHub CLI skill for interacting with GitHub via the gh command line tool.

    1.7k GitHub stars~798 tokensUpdated yesterday
    DevelopmentAuto-check passed
  • Renovate Actions PR Review

    backnotprop/plannotator

    Reviews Renovate pull requests that bump GitHub Actions by checking pinned SHAs against upstream tags, scanning changelogs and confirming workflows stay compatible.

    9.2k GitHub stars~640 tokensUpdated today
    DevelopmentAuto-check passed
  • Prepare, validate, push, open, monitor, and merge paired pull requests across the public AetherKiri repository and private AetherInternal package without publishing private source or unrelated…

    149 GitHub stars~1.9k tokensUpdated today
    DevelopmentAuto-check passed
  • GitHub PR Actions Fix

    openteams-lab/openteams

    OpenTeams skill for watching GitHub Actions checks after a pull request is submitted or updated, inspecting failures, making the smallest safe code fix, validating locally, pushing to the PR branch…

    627 GitHub stars~878 tokensUpdated 4 days ago
    DevelopmentAuto-check passed
  • Fix CI

    ccusage/ccusage

    Diagnoses and fixes failing GitHub Actions checks with gh. An agent skill from ccusage/ccusage.

    19k GitHub stars~487 tokensUpdated today
    DevelopmentAuto-check passed

More from wado-lang/wado

All 15 skills in this repo
  • Profile the native Rust wado binary (compile/serve/run) for host-side bottlenecks — CPU with a sampling profiler, memory with the span trace's RSS and valgrind DHAT.

    117 GitHub stars~2.9k tokensUpdated today
    Auto-check: notes
  • Wado Performance

    wado-lang/wado

    Analyze and improve the runtime speed of a Wado program's compiled guest Wasm — profile hot functions, read the generated WIR for allocations and copies, reason about the WasmGC cost model, and…

    117 GitHub stars~7.5k tokensUpdated today
    Auto-check passed
  • Investigate and improve code coverage for the wado-compiler crate.

    117 GitHub stars~1.1k tokensUpdated today
    Auto-check passed
  • Git Upstream Sync

    wado-lang/wado

    The only way to merge origin/main into a branch, conflicts or not.

    117 GitHub stars~855 tokensUpdated today
    Auto-check passed
  • Jco

    wado-lang/wado

    Transpile Wado Wasm components to JS with jco, then run, debug, and benchmark them on Node.

    117 GitHub stars~2.7k tokensUpdated today
    Auto-check passed
  • On Task Done

    wado-lang/wado

    Task-completion flow: /cr (a /code-review answered with /code-review-response, which ends with /distill), update docs (spec/cheatsheet/compiler/optimizer), then run mise run on-task-done (build…

    117 GitHub stars~611 tokensUpdated today
    Auto-check passed

Questions about CI Timing

What does CI Timing do?

Measure how long GitHub Actions jobs and steps took across past runs, and find the pull request that made CI slower. CI Timing is an agent skill from wado-lang/wado. Measure how long GitHub Actions jobs and steps took across past runs, and find the pull request that made CI slower.

When should I use CI Timing?

CI Timing fits situations like: any question about CI duration; tasks that involve Pull requests; tasks that involve CI/CD.

How do I install CI Timing in Claude Code?

Run `npx skills add wado-lang/wado --skill ci-timing -a claude-code`. Or copy the skill folder (.claude/skills/ci-timing in wado-lang/wado) into .claude/skills/ci-timing in your project. Claude Code loads it when a task matches its description.

How do I install CI Timing in Codex?

Run `npx skills add wado-lang/wado --skill ci-timing -a codex`. Or copy the skill folder (.claude/skills/ci-timing in wado-lang/wado) into .agents/skills/ci-timing in your project. Codex loads it when a task matches its description.

Can I use CI Timing in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add wado-lang/wado --skill ci-timing -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/ci-timing, .gemini/skills/ci-timing, .github/skills/ci-timing and .opencode/skills/ci-timing in your project.

What does CI Timing need to run?

Going by SKILL.md and its folder, CI Timing needs JavaScript for the scripts in its folder and the command-line tools its instructions call (mise). Our summary lists: Node.js.

Does CI Timing access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is CI Timing safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does CI Timing use?

CI Timing is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does CI Timing use?

About 518 tokens (SKILL.md is roughly 2.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to CI Timing?

Skills that share tags, products or a category with CI Timing: Babysit PR To Pass CI (sgl-project/sglang, 37k stars), Gh (bubbuild/bub, 1.7k stars), Renovate Actions PR Review (backnotprop/plannotator, 9.2k stars) and Submit Aetherkiri Cross Repo PRs (AetherKiri/Aether, 149 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains CI Timing?

wado-lang (a GitHub organization) maintains it in wado-lang/wado, which has 117 GitHub stars. The repository holds 15 skills in this directory. The repository was last updated on October 8, 2026.

Source: wado-lang/wado on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.