ci-maintenance SKILL.md skillA
ci-maintenance from bolens/agent-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add bolens/agent-skills/ci-maintenance@git:20260909.82ed8e3Pins git:20260909.82ed8e3 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- bolens/agent-skills
- Path
skills/ci-maintenance/SKILL.md- Versions recorded
- 5
- Latest version
- git:20260909.82ed8e3, committed Sep 9, 2026
- First version recorded
- Sep 6, 2026
- Size
- 11,584 bytes
- Repository stars
- 3
- License
- MIT
Design, implement, and audit repository CI pipelines and reusable workflow contracts against applicable fleet standards. Use for CI setup, workflow hardening, required-check coverage, or shared pipeline changes. Keep hook-only setup, isolated test diagnosis, and PR monitoring in their existing workflows.
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
# CI maintenance Build CI around the repository's actual validation and delivery contract. Use its existing platform and tools. GitHub Actions guidance is available below, but a different provider is not a reason to migrate the repository. For toolchain setup or local/CI drift, use [portable development environments](references/development-environments.md). Prefer mise for pinned tools, devenv or devcontainers for portable setup, and NixOS development VMs or system tests when OS behavior matters and the setup improves reproducibility or onboarding. Share repository commands and version ownership across environments; preserve working alternatives and verify the actual setup path selected by CI. When changing environment examples, prefer `.env.spec` with explicit consumer/validator support and native schema-backed fixtures as described in that reference. Read [setup and runtime contracts](references/setup-contracts.md) when changing precedence, bootstrap diagnostics, concurrent services, generated examples, or secret-provider integration. ## Establish the applicable baseline …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_6s6bks2o6uldpp7q/1838d0319470b087f2cac9a52f083c6a488863b52a457615ec7a75f1f81f03c3.json
Then /plugin install ci-maintenance@markdownregistry-6s6bks2o6uldpp7q in Claude Code. It installs git:20260909.82ed8e3, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add bolens/agent-skills/ci-maintenance@sha256:1838d0319470b087The line at the top of this page pins the label git:20260909.82ed8e3, 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_6s6bks2o6uldpp7q)
2 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: what changed in bolens/agent-skills/ci-maintenance since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.
Got a copy of ci-maintenance from somewhere else? Ask it: where did my ci-maintenance come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.
Versions
The registry has recorded 5 versions of this file, between Sep 6, 2026 and Sep 9, 2026, more than one a day.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260909.82ed8e3 latest | 2026-09-09 | 82ed8e3 | 11,584 B | A | view · diff |
| git:20260908.dc3bb11 | 2026-09-08 | dc3bb11 | 11,307 B | A | view · diff |
| git:20260908.72ec452 | 2026-09-08 | 72ec452 | 10,779 B | A | view · diff |
| git:20260906.c0bfd04 | 2026-09-06 | c0bfd04 | 9,965 B | A | view · diff |
| git:20260906.4daf129 | 2026-09-06 | 4daf129 | 9,429 B | A | view |
Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.
Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml
It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.
Installed this file, say at .claude/skills/ci-maintenance/SKILL.md? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies
In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies
No sha256sum on your machine? shasum -a 256 prints the same lines.
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 (11584 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
bolens/agent-skills · 3 stars · license MIT · pushed 2026-11-17 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_6s6bks2o6uldpp7q GET https://markdownregistry.com/api/v1/resolve?ref=bolens/agent-skills/ci-maintenance GET https://markdownregistry.com/api/v1/blob/1838d0319470b087f2cac9a52f083c6a488863b52a457615ec7a75f1f81f03c3
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 bolens/agent-skills
Every file in bolens/agent-skills