monitor-ci SKILL.md skillA
monitor-ci from sergeyklay/.agents is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add sergeyklay/.agents/monitor-ci@v1.0Pins v1.0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- sergeyklay/.agents
- Path
.agents/skills/monitor-ci/SKILL.md- Versions recorded
- 1
- Latest version
- v1.0, committed Sep 3, 2026
- Size
- 7,533 bytes
- Repository stars
- 6
- License
- Apache-2.0
Drive a long-running GitHub Actions run to a trustworthy conclusion without burning the session on polling. Use when asked to wait for a pipeline, watch a build, babysit a release or deploy run, restart it if it fails, or report whether it went green. Also use when a run must finish before a follow-up step such as a push, a tag, or a dependent job in another repository. Covers confirming the run is the intended one, bounded waiting instead of open-ended blocking, reading the real per-job…
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
# Babysit a CI Run
Waiting on a pipeline looks like a one-line job and is not. Three things go wrong, and each one produces a confident but wrong report: the wrong run gets watched, the waiting strategy exhausts the session before the run finishes, or the run's outcome is read off a summary that hides a suppressed failure.
This skill is the mechanics of getting from "it is running" to "here is what actually happened". Whether the green that comes out is *evidence* is a separate question, and it belongs to `prove-checks`.
## Trigger
- A run must reach a conclusion before the next step can start.
- The task says wait for, watch, babysit, or monitor a build, release, deploy or pipeline.
- A failed run must be restarted, possibly more than once.
- Another party is blocked on the answer "did it go green?"
## Procedure
### 1. Confirm the run is the one you were asked about
A run URL or id identifies a run, not an intent. Before waiting on it, read back what it actually is and check it against the request:
```
gh api repos/<owner>/<repo>/actions/runs/<run-id> \
--jq '{name, event, status, conclusion, head_branch, head_sha, attempt: .run_attempt}'
```
…Read the whole file at its exact version.
How to install
mdr add sergeyklay/.agents/monitor-ci@sha256:b8ddbed8853c6720The line at the top of this page pins the label v1.0, 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_cykfcygfrpt4ym7o)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Sep 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 (7533 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
sergeyklay/.agents · 6 stars · license Apache-2.0 · pushed 2026-10-29 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_cykfcygfrpt4ym7o GET https://markdownregistry.com/api/v1/resolve?ref=sergeyklay/.agents/monitor-ci GET https://markdownregistry.com/api/v1/blob/b8ddbed8853c672053a1b7212046afd7b5ada5e0194a26ff5c0d3e1125e121f3
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.
More from sergeyklay/.agents
Every file in sergeyklay/.agents