convergence-loop SKILL.md skillA
convergence-loop from chrono-meta/forge-harness is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add chrono-meta/forge-harness/convergence-loop@git:20260811.eede7adPins git:20260811.eede7ad in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- chrono-meta/forge-harness
- Path
plugins/fh-commons/skills/convergence-loop/SKILL.md- Versions recorded
- 5
- Latest version
- git:20260811.eede7ad, committed Aug 11, 2026
- First version recorded
- Jun 3, 2026
- Size
- 9,200 bytes
- Repository stars
- 30
- License
- MIT
A universal gate-reinforcement meta-skill that replaces the "single-pass = done" pattern with a converging loop of up to N rounds. Can be applied to any gate, checkpoint, or verification step. Only declares "truly passed" after FAIL→FIX→re-verify repeats until convergence (all items pass). Escalates to structural redesign if not converged within N rounds. Triggers on: "convergence-loop", "how many rounds do we need", "suspicious of single-pass", "not sure if it really passed", or equivalent…
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
# convergence-loop — Universal Convergence Loop Gate Reinforcement > A single pass declaration is hard to trust. A fix exposes new FAILs, and round 2 catches what round 1 missed. convergence-loop assigns a "truly passed" criterion to any gate. ## Triggers - `/convergence-loop` - "convergence-loop", "how many rounds do we need", "not sure if it really passed" - "suspicious of single-pass", "run until it passes", "keep verifying until clean" - "single pass isn't enough", "need another round", "the fix might have introduced new issues" - Auto-proposed: when the same artifact receives a FAIL verdict 2+ times in the same session (observable: 2nd FAIL on identical scope) --- ## Origin Extracted from a recurring "single-pass gate is hard to trust" pattern observed across multiple hub workflows. The canonical reference is: - `harvest-loop` extract→attack→synthesize cycle: pattern extraction → attack → synthesis → the repeating structure must run until convergence When the same structure recurs across gates, it is a skill. ## Applicable Targets | Applicable Gate | Example | |---|---| | Skill diagnostic gate | harness-doctor + apex-review | …
Read the whole file at its exact version.
How to install
mdr add chrono-meta/forge-harness/convergence-loop@sha256:a388832ce8713998The line at the top of this page pins the label git:20260811.eede7ad, 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_quedzantlq7a2p5h)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Jun 3, 2026 and Aug 11, 2026, about one every 17 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260811.eede7ad latest | 2026-08-11 | eede7ad | 9,200 B | A | view · diff |
| git:20260802.44b349d | 2026-08-02 | 44b349d | 8,097 B | A | view · diff |
| git:20260627.a6d421d | 2026-06-27 | a6d421d | 6,647 B | A | view · diff |
| git:20260603.5a5a642 | 2026-06-03 | 5a5a642 | 5,793 B | A | view · diff |
| git:20260603.c071dbf | 2026-06-03 | c071dbf | 5,356 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 (9200 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
chrono-meta/forge-harness · 30 stars · license MIT · pushed 2026-10-31 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_quedzantlq7a2p5h GET https://markdownregistry.com/api/v1/resolve?ref=chrono-meta/forge-harness/convergence-loop GET https://markdownregistry.com/api/v1/blob/a388832ce87139980c0e1f095edc6bdf3220d7b97a2c51957c9c1e2e2a1c434d
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.