Agent skill · operations · steipete
openclaw-ci-limits
Manage OpenClaw GitHub Actions and Blacksmith CI capacity, runner-registration budgets, fanout caps, main-push single-flight, shard sizing, hosted-runner offload, queue health, and safe ramp-down/ramp-up changes. Use when tuning `.github/workflows/*`, `docs/ci.md`, CI runner labels, matrix `max-parallel`, ClawSweeper/Blacksmith burst protection, CodeQL runner placement, or investigating slow/queued OpenClaw CI.
Why this skill is useful
Provides specific commands and procedures for managing CI capacity and diagnosing bottlenecks that the AI wouldn't reliably generate on its own.
What it needs
Requires blacksmith, ghx, jq, node installed locally. About 10k tokens when loaded. Last updated 2026-08-07. 385,400 stars on the source repository.
What this skill does
OpenClaw CI Limits Use this skill for CI capacity changes, not ordinary test failure triage. The goal is to keep OpenClaw fast while distinguishing runner registration, runner availability, Blacksmith control-plane health, and downstream queue drains. Core Facts Full main-tier CI runs hourly; ordinary main pushes run security-fast. A green push is not evidence that the full suite passed. Ordinary PRs defer Windows, macOS Node/Swift, iOS build/simulator, real-Gateway UI, published-driver update, Knip, and most architecture proof. Import-cycle and Kysely guards remain blocking. Use docs/ci/scope-and-routing/selection.md and the current manifest for exact event, owner, and release-fallback selection; do not restore deferred lanes while tuning capacity. Android screenshots remain release-only. Do not assume the scarce resource. Prove whether pressure is runner registrations, eligible runner availability, Blacksmith capacity/control plane, workflow dependencies, test runtime, or a downstream queue writer. GitHub runner registrations for openclaw currently report a 10,000 per 5-minute bucket in actionsrunnerregistration. Verify the live bucket before each tuning pass because GitHub can change it. The openclaw organization shares one bucket. Core REST quota does not draw down this bucket. Check actionsrunnerregistration separately; core quota can be healthy while runner registration is throttled. Use about 60% of the live bucket as the operating target. With the current 10,000-registration bucket, keep planned Blacksmith burst load under 6,000 registrations per 5 minutes and leave the rest for other repos, retries, and burst overlap. Jobs that route, notify, summarize, choose shards, or run short CodeQL quality scans should stay on GitHub-hosted runners unless measured evidence says Blacksmith is required. Runner Cost Policy Use the smallest runner that completes the required workload reliably. Keep short control jobs hosted and ordinary trusted development proof local. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills steipete/openclaw-ci-limits