review-cycles SKILL.md skillA
review-cycles from skillberry-ai/cap-evolve is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add skillberry-ai/cap-evolve/review-cycles@git:20261108.4e93f41Pins git:20261108.4e93f41 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- skillberry-ai/cap-evolve
- Path
.claude/skills/review-cycles/SKILL.md- Versions recorded
- 1
- Latest version
- git:20261108.4e93f41, committed Nov 8, 2026
- Size
- 10,756 bytes
- Repository stars
- 70
- License
- Apache-2.0
Run 3 independent review rounds on a cap-evolve PR, using agent-tool reviewers on this machine (GLM via Claude Code, IBM Bob Shell, or the user's own Claude Code as fallback), fix the findings between rounds, and report both verdicts. Use for every PR review in this repo opened via the open-pr skill, and whenever asked to review a cap-evolve PR (yours or someone else's). Use instead of the generic code-review skill, which makes one review and doesn't know this repo's rules.
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
# Review cycles Two reviewers review the PR in parallel, on this machine, with the user's own login to the reviewer tool. Each posts its review on the PR. You fix the findings, push, and run this skill again for the next round — **3 rounds total by default**. Reviewer N in round 2+ resumes its own earlier-round session. The reviewer tool is a backend in `scripts/offload-review/backends/<name>.sh`: - `glm` (the default): GLM through Claude Code, pointed at an internal gateway. - `bob`: IBM Bob Shell. - `claude`: the user's own Claude Code, with its own login and model. Use `--backend <name>` or `OFFLOAD_BACKEND` to pick the first one. **Fallback.** When a reviewer's backend is not set up, or it fails before that reviewer posts, the next backend in `OFFLOAD_FALLBACK` (default `bob claude`) runs that reviewer. So the default order is glm, then bob, then claude. - Each reviewer falls back on its own. One reviewer can post with glm and the other with bob. - A reviewer never posts twice. The next backend runs only while no review of that reviewer, round and head is on the PR. - The marker of each review names the backend that wrote it. The script's last line …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_lcu5ie3c5lexsv3g/c725170524f67c8b041fd8a700e0c72f089deeb7b84f24a06ce3b38a397183d7.json
Then /plugin install review-cycles@markdownregistry-lcu5ie3c5lexsv3g in Claude Code. It installs git:20261108.4e93f41, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add skillberry-ai/cap-evolve/review-cycles@sha256:c725170524f67c8bThe line at the top of this page pins the label git:20261108.4e93f41, 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_lcu5ie3c5lexsv3g)
5 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 skillberry-ai/cap-evolve/review-cycles 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 review-cycles from somewhere else? Ask it: where did my review-cycles 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 1 version of this file, committed on Nov 8, 2026.
Watch this file (sign in, one email per new version)
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/review-cycles/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 (10756 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
skillberry-ai/cap-evolve · 70 stars · license Apache-2.0 · pushed 2026-11-13 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_lcu5ie3c5lexsv3g GET https://markdownregistry.com/api/v1/resolve?ref=skillberry-ai/cap-evolve/review-cycles GET https://markdownregistry.com/api/v1/blob/c725170524f67c8b041fd8a700e0c72f089deeb7b84f24a06ce3b38a397183d7
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.