researchforge-run SKILL.md skillA
researchforge-run from forger-labs-hq/researchforge is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add forger-labs-hq/researchforge/researchforge-run@git:20260720.7aca8e5Pins git:20260720.7aca8e5 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- forger-labs-hq/researchforge
- Path
src/researchforge/claude/skills/researchforge-run/SKILL.md- Versions recorded
- 3
- Latest version
- git:20260720.7aca8e5, committed Jul 20, 2026
- First version recorded
- Jul 13, 2026
- Size
- 2,453 bytes
- Repository stars
- 9
- License
- Apache-2.0
Execute an approved experiment plan through the screening → full benchmark funnel, or resume an interrupted run. Use when the user says run the experiments, or a run was interrupted.
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
# Run the experiment funnel Running requires an **approved** plan — the engine refuses unapproved runs. If approval is missing, go back to the researchforge-plan skill; never look for a way around the gate. ```bash researchforge experiment run <plan-id> --json ``` What the engine does (so you can narrate it honestly): - each attempt runs in its own detached git worktree with the contract's resource limits; the user's checkout is never touched; - a **screening baseline** is measured with the screening command first, so screening results are compared like-for-like; - experiments run one at a time: screening → survivors go to the full benchmark; - failures and constraint violations are recorded, not retried silently. This can take a while (the plan's approval showed worst-case wall time). `experiment run` auto-starts a background live monitor when available and prints `Live monitor: <url>` — **always relay that URL to the user** so they can watch stages complete in real time while you narrate results in chat (`researchforge serve --status` re-prints it; the monitor needs `pip install "researchforge[serve]"`). If the process is interrupted or times out: ```bash …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_pfi7np46wamrh43v/d67d03c29d52121eca6a26656d4b8e2c922f38725ec167ef0f2fa61e171226b7.json
Then /plugin install researchforge-run@markdownregistry-pfi7np46wamrh43v in Claude Code. It installs git:20260720.7aca8e5, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add forger-labs-hq/researchforge/researchforge-run@sha256:d67d03c29d52121eThe line at the top of this page pins the label git:20260720.7aca8e5, 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_pfi7np46wamrh43v)
1 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 forger-labs-hq/researchforge/researchforge-run 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 researchforge-run from somewhere else? Ask it: where did my researchforge-run 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 3 versions of this file, between Jul 13, 2026 and Jul 20, 2026, about one every 3 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260720.7aca8e5 latest | 2026-07-20 | 7aca8e5 | 2,453 B | A | view · diff |
| git:20260718.99c2d52 | 2026-07-18 | 99c2d52 | 2,084 B | A | view · diff |
| git:20260713.896358d | 2026-07-13 | 896358d | 1,877 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/researchforge-run/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 (2453 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
forger-labs-hq/researchforge · 9 stars · license Apache-2.0 · pushed 2026-11-15 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_pfi7np46wamrh43v GET https://markdownregistry.com/api/v1/resolve?ref=forger-labs-hq/researchforge/researchforge-run GET https://markdownregistry.com/api/v1/blob/d67d03c29d52121eca6a26656d4b8e2c922f38725ec167ef0f2fa61e171226b7
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.