How do I install the Github CI Watch skill?

Run npx skillmds@latest add jasoncarreira/github-ci-watch in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Github CI Watch safe to use?

SkillMD's automated safety review verdict for this skill is PASS. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: executes scripts, makes network calls, reads secrets. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Github CI Watch?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Github CI Watch free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Github CI Watch?

jasoncarreira (@jasoncarreira) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Github CI Watch by jasoncarreira — Agent Skill

Name: Github CI Watch
Rating: 4.2 (5 reviews)
Author: jasoncarreira

Github CI Watch

Watch the main branch of one or more GitHub repositories for new CI (GitHub Actions) workflow-run failures — emits a fresh turn the moment a build breaks and stays silent while CI is green. Use when mimir maintains repos whose CI it should react to (e.g. a failing build on main after a merge it landed). Seen-set deduped so each failed run is reported exactly once. Companion to the ``pollers`` framework skill (mechanics) and the ``world-scanning`` skill (catalog of what's worth polling). Opt-in: copy this directory into ``<home>/skills/github-ci-watch/`` then set the env vars below.

jasoncarreira Updated Aug 19, 2026 6 repo stars

File contents

github-ci-watch — react when CI breaks

An opt-in poller skill that ships with mimir under mimir/optional-skills/ but is NOT auto-installed — most installs don't watch a repo's CI, so the framework doesn't seed it by default.

It watches the main branch of each GITHUB_REPOS entry, inspects the last few GitHub Actions workflow runs, and emits one ci_failure event per newly-failed run (conclusion failure / timed_out / startup_failure). Green builds produce zero output — the "silence as filter" principle: this poller only speaks when CI breaks.

Installation

Copy the directory into your agent home:
```
cp -r mimir/optional-skills/github-ci-watch <home>/skills/
```
(Or run from inside the container against /workspace/mimir.)
Set the env vars — at minimum GITHUB_REPOS (plus GITHUB_TOKEN if gh auth isn't already configured in the environment).
The pollers framework discovers pollers.json and runs scripts/poller.py on its cron (default */15 * * * *).

State

Reported run IDs are tracked in seen_run_ids.json (trimmed to the last 200) so a given failure is reported exactly once. State lives in $STATE_DIR (resolved by the framework to a persistent per-poller location that survives container rebuilds).

Output

One JSONL event per new failure: {event_type: "ci_failure", repo, branch, workflow, conclusion, run_id, created_at, url, prompt} — the prompt is the turn the agent wakes on.

---name: github-ci-watchdescription: Watch the main branch of one or more GitHub repositories for new CI (GitHub Actions) workflow-run failures — emits a fresh turn the moment a build breaks and stays silent while CI is green. Use when mimir maintains repos whose CI it should react to (e.g. a failing build on main after a merge it landed). Seen-set deduped so each failed run is reported exactly once. Companion to the ``pollers`` framework skill (mechanics) and the ``world-scanning`` skill (catalog of what's worth polling). Opt-in: copy this directory into ``<home>/skills/github-ci-watch/`` then set the env vars below.---# github-ci-watch — react when CI breaksAn **opt-in poller skill** that ships with mimir under``mimir/optional-skills/`` but is NOT auto-installed — most installsdon't watch a repo's CI, so the framework doesn't seed it by default.It watches the ``main`` branch of each ``GITHUB_REPOS`` entry, inspectsthe last few GitHub Actions workflow runs, and emits one ``ci_failure``event per newly-failed run (conclusion ``failure`` / ``timed_out`` /``startup_failure``). Green builds produce **zero output** — the"silence as filter" principle: this poller only speaks when CI breaks.## Installation1. Copy the directory into your agent home: ``` cp -r mimir/optional-skills/github-ci-watch <home>/skills/ ``` (Or run from inside the container against ``/workspace/mimir``.)2. Set the env vars — at minimum ``GITHUB_REPOS`` (plus ``GITHUB_TOKEN`` if ``gh auth`` isn't already configured in the environment).3. The ``pollers`` framework discovers ``pollers.json`` and runs ``scripts/poller.py`` on its cron (default ``*/15 * * * *``).## StateReported run IDs are tracked in ``seen_run_ids.json`` (trimmed to thelast 200) so a given failure is reported exactly once. State lives in``$STATE_DIR`` (resolved by the framework to a persistent per-pollerlocation that survives container rebuilds).## OutputOne JSONL event per new failure:``{event_type: "ci_failure", repo, branch, workflow, conclusion,run_id, created_at, url, prompt}`` — the ``prompt`` is the turn theagent wakes on.

Frequently asked questions