review-flows SKILL.md skillA
This file is byte-identical to the first copy the registry indexed. Same content hash, so the same checks give both the same grade.
review-flows from kurrent-io/kcap is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add kurrent-io/kcap/review-flows@git:20261029.ab14ff3Pins git:20261029.ab14ff3 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- kurrent-io/kcap
- Path
kcap/skills/review-flows/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261029.ab14ff3, committed Oct 29, 2026
- First version recorded
- Oct 19, 2026
- Size
- 22,121 bytes
- Repository stars
- 31
- License
- a license file GitHub does not identify
This skill should be used ONLY when the user explicitly asks to run a structured review *flow* — e.g. "start a review flow", "submit this for review", "re-review after I address findings", or wants an iterative review loop run by a separate reviewer that continues until sign-off. Do NOT use this skill (and do NOT call the flows MCP tools) for an ordinary review request such as "review my PR", "review this diff/spec/design", or "code review" where the user just wants you to review it yourself —…
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 Flows Use the `kcap mcp flows` MCP tools (`start_review_flow`, `submit_review_round`, …) to run a structured review **flow**: your work is submitted to a **separate, hosted reviewer** agent, which returns a result (`findings` with the findings text, or `clean`); you address findings and keep iterating until the reviewer returns `clean`. This is a deliberate, heavier workflow — use it only when the user explicitly opts into it. These four tools are aliases of the generic flow tools (`start_flow`, `send_to_participant`, `get_flow_status`, `close_flow`) — see the `agent-flows` skill for non-review flows. ## Long rounds are normal `round_timeout` is an **inactivity** bound, not a wall-clock cap: a round only fails for taking too long if the reviewer goes genuinely quiet for that whole stretch — an actively-working reviewer can legitimately run a round for a long time. If a status check (or a `submit_review_round`/`start_review_flow` call) returns the benign "Flow still running" text, that is an expected outcome on a long round, not a problem — re-enter the wait with `get_review_flow_status(flow_run_id, wait: true)`, which blocks (via bounded, internally-retried checks —… …
Read the whole file at its exact version.
How to install
mdr add kurrent-io/kcap/review-flows@sha256:8c11cc27e4ad2b32The line at the top of this page pins the label git:20261029.ab14ff3, 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_dlfjigkrrfpfsu4v)
0 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Oct 19, 2026 and Oct 29, 2026, about one every 2 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261029.ab14ff3 latest | 2026-10-29 | ab14ff3 | 22,121 B | A | view · diff |
| git:20261024.a1b2440 | 2026-10-24 | a1b2440 | 22,020 B | A | view · diff |
| git:20261020.bf6d98a | 2026-10-20 | bf6d98a | 22,005 B | A | view · diff |
| git:20261020.059935c | 2026-10-20 | 059935c | 21,772 B | A | view · diff |
| git:20261019.02040a9 | 2026-10-19 | 02040a9 | 21,255 B | A | view |
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 (22121 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
kurrent-io/kcap · 31 stars · license a license file GitHub does not identify · pushed 2026-11-04 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_dlfjigkrrfpfsu4v GET https://markdownregistry.com/api/v1/resolve?ref=kurrent-io/kcap/review-flows GET https://markdownregistry.com/api/v1/blob/8c11cc27e4ad2b32eaa7d5bb377a66574e9063cb3ca93a18d59df3c016c82074
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.