build-speed SKILL.md skillA
build-speed from avelikiy/great_cto is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add avelikiy/great_cto/build-speed@git:20261103.73aca06Pins git:20261103.73aca06 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- avelikiy/great_cto
- Path
skills/build-speed/SKILL.md- Versions recorded
- 1
- Latest version
- git:20261103.73aca06, committed Nov 3, 2026
- Size
- 3,954 bytes
- Repository stars
- 112
- License
- MIT
Make a slow CI pipeline or build faster by measuring it first — per-step durations, the slowest step, a target — then one change at a time, re-measured the same way. Speed never comes from removing, skipping or weakening a check. Use when a build or CI is slow ("CI долго", "ускорь сборку", "гейт идёт 40 минут", "build takes forever"). Loaded by devops, ci-resolver.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# build-speed — measure, then change one thing, then measure the same way A build is made faster by finding where the minutes go. Guessing goes to the step that looks heavy; measuring goes to the step that is. On this repository's own gate one step, `lib tests` run in a single worker, was 21–30 of 28–38 measured minutes: 75–80% of the gate. Eight workers took that step to 5 minutes; no cache would have. ## 1. Measure before anything changes - **Per step, not in total.** The duration of each step from the CI log or the runner's API (`gh run view --json jobs`, the TAP `duration_ms`, timestamps around each step). A total says the build is slow; steps say where. - **At least three runs** of unchanged code. Write down the range, not one number: a shared runner and a busy laptop both vary by a third. - **Note the conditions.** Runner type, cores, cache state (cold or warm), concurrency flags. A measurement without its conditions cannot be repeated. ## 2. Pick one step and a target The slowest step, unless a faster one runs on every commit and the slow one does not. Write the target before the change: "`lib tests` from 21–30 min to under 10 …
Read the whole file at its exact version.
How to install
mdr add avelikiy/great_cto/build-speed@sha256:50264b2977eeeb3fThe line at the top of this page pins the label git:20261103.73aca06, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_62uhbs6r5mparafr)
6 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Nov 3, 2026.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (3954 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
avelikiy/great_cto · 112 stars · license MIT · pushed 2026-11-06 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_62uhbs6r5mparafr GET https://markdownregistry.com/api/v1/resolve?ref=avelikiy/great_cto/build-speed GET https://markdownregistry.com/api/v1/blob/50264b2977eeeb3f95c5456dbf3d1b2518fe059044fcf690a9c15697487ed66d
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.