run-workflow SKILL.md skillA
run-workflow from hlintel/headron is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add hlintel/headron/run-workflow@git:20261104.5d19a74Pins git:20261104.5d19a74 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- hlintel/headron
- Path
skills/system/run-workflow/SKILL.md- Versions recorded
- 2
- Latest version
- git:20261104.5d19a74, committed Nov 4, 2026
- First version recorded
- Oct 27, 2026
- Size
- 10,333 bytes
- Repository stars
- 4
- License
- MIT
How to write and run a dynamic workflow script with the `run_workflow` tool: a Python script that orchestrates many agents with `agent`, `parallel`, `pipeline`, and `phase`. Use when a task splits into many independent or staged pieces of agent work (fan out over files, modules, bugs, or review angles, then aggregate), or when the user asks for a workflow. Don''t use for a single delegated task (use a subagent) or for legacy workflow files (see migrate-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
# Dynamic workflows with `run_workflow`
A workflow is a short Python script that the `run_workflow` tool executes. The
script decides which agents to start, in what order, and what to do with their
results. Use it instead of many manual subagent calls when the orchestration
itself is code: loops over a list, fan-out then aggregate, or staged pipelines.
## Steps
1. Pass the script inline as `Script`, or write it to a file (for example in
the conversation scratch directory) and pass its absolute path as
`ScriptPath`. Set exactly one of them; a file is easier to fix and rerun.
2. Call `run_workflow(Script="...", Description="...")` or
`run_workflow(ScriptPath="/abs/path/workflow.py", Description="...")`.
`Description` is a one-line goal shown in the UI.
The workflow runs in the background, and you are notified when it ends.
For a quick script, such as a `call_tool` fan-out, set
`WaitMsBeforeAsync` (up to 10000) to get the result in the same turn if it
finishes in time.
To pass inputs, set `Args` to a JSON object; the script reads it as the
`args` dict. When `ScriptPath` is a saved workflow's entry script, `Args`
…Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_zddnflxei223wpsz/7551606d8e93a135a8021af14af2b631a8b9d99f34049e8b9c666bbf0d5a4173.json
Then /plugin install run-workflow@markdownregistry-zddnflxei223wpsz in Claude Code. It installs git:20261104.5d19a74, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add hlintel/headron/run-workflow@sha256:7551606d8e93a135The line at the top of this page pins the label git:20261104.5d19a74, 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_zddnflxei223wpsz)
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 hlintel/headron/run-workflow 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 run-workflow from somewhere else? Ask it: where did my run-workflow 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 2 versions of this file, between Oct 27, 2026 and Nov 4, 2026, about one every 7 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261104.5d19a74 latest | 2026-11-04 | 5d19a74 | 10,333 B | A | view · diff |
| git:20261027.677d574 | 2026-10-27 | 677d574 | 10,332 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/run-workflow/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 (10333 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
hlintel/headron · 4 stars · license MIT · pushed 2026-11-18 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_zddnflxei223wpsz GET https://markdownregistry.com/api/v1/resolve?ref=hlintel/headron/run-workflow GET https://markdownregistry.com/api/v1/blob/7551606d8e93a135a8021af14af2b631a8b9d99f34049e8b9c666bbf0d5a4173
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.