run-workflow
Skill94 starsChanged 33 days agoMITView on GitHub
Launches a saved multi-agent workflow by id on Claude Code or Codex. Use when the user asks to run a saved workflow or review loop.
6 other projects use a version of this.
Adopted by
Most recently taken up by
- khpeet/newrelic-skillstheir own version, first seen Nov 8, 2026
- norman-finance/norman-mcp-servertheir own version, first seen Nov 2, 2026
- HLIntel/thea-softwaretheir own version, first seen Nov 1, 2026
- HLIntel/Headrontheir own version, first seen Nov 1, 2026
- oocx/tfplan2mdtheir own version, first seen Oct 8, 2026
- simstudioai/skillstheir own version, first seen Sep 9, 2026
Other versions6 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 6
- oocx/tfplan2md★ 174same name
- norman-finance/norman-mcp-server★ 65same name
- HLIntel/Headron★ 3same name
- HLIntel/thea-software★ 3same name
- simstudioai/skills★ 2same name
- khpeet/newrelic-skills★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository146 other files it gives its agents.
- agents/AGENTS.mdAGENTS.md
- AGENTS.mdAGENTS.md
- hooks/AGENTS.mdAGENTS.md
- agents-hooksSkill
- agents-mcpSkill
- agents-memorySkill
- agents-skills-feedback-loopSkill
- agents-skillsSkill
- agents-subagentsSkill
- agents-swarm-orchestrationSkill
- ai-agentsSkill
- ai-architecture-advisorSkill
- ai-bot-builderSkill
- ai-coding-agents-observability-evalsSkill
- ai-coding-agents-pluginsSkill
- ai-coding-agents-provider-runtimeSkill
- ai-coding-agents-runtime-coreSkill
- ai-coding-agents-safety-envelopeSkill
- ai-coding-agents-settings-policySkill
- ai-coding-agentsSkill
- ai-coding-agents-stateSkill
- ai-coding-agents-surfacesSkill
- ai-context-layerSkill
- ai-data-curation-pretrainingSkill
- ai-deep-researchSkill
- ai-distributed-trainingSkill
- ai-evalsSkill
- ai-llm-inferenceSkill
- ai-llmSkill
- ai-local-model-opsSkill
- ai-ml-data-scienceSkill
- ai-mlopsSkill
- ai-ml-timeseriesSkill
- ai-post-trainingSkill
- ai-pretrainingSkill
- ai-product-operating-modelSkill
- ai-prompt-engineeringSkill
- ai-ragSkill
- ai-scaling-lawsSkill
- ai-vector-brainSkill
- ai-voice-botsSkill
- data-analytics-engineeringSkill
- data-lake-platformSkill
- data-metabaseSkill
- data-sql-optimizationSkill
- data-streamingSkill
- dev-ai-coding-metricsSkill
- dev-api-designSkill
- dev-context-code-graphSkill
- dev-context-engineeringSkill
- dev-context-multi-repoSkill
- dev-contribution-quality-analysisSkill
- dev-dependency-managementSkill
- dev-git-commit-messageSkill
- dev-git-workflowSkill
- dev-workflow-planningSkill
- docs-ai-prdSkill
- docs-codebaseSkill
- docs-notes-retrievalSkill
- document-docxSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
6 rules. 0 are common, 0 are distinctive, and 6 are very specific to this project.
0
Common
Most of the 6 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 40
If the plan has a context_budget block, follow its extract command instead of loading the whole file.
- Very specific: line 41
If the plan has a tree_snapshot, run its command once before the first worker, and apply its stop_rules after each read-only phase.
- Very specific: line 42
Run the execution_contract phases in order.
- Very specific: line 44
Keep to the plan's agent cap.
- Very specific: line 62
When prior decisions or pitfalls are relevant, consult learnings.consolidated.md if present.
- Very specific: line 64
After applying it, if you encountered a pattern worth remembering, a mistake worth preventing, or a domain fact that surprised you, append …
“Common” is measured: kept by at least 6 in 10 of the 6 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Run a Saved Workflow
A saved workflow keeps its guarantees in code or in a generated plan, not in a prompt: fresh agents each round, the refuter quorum, the frozen acceptance checks, the round cap. This skill finds the workflow and hands off to that code or plan. It never improvises a workflow of its own.
Quick Reference
| Situation | Action |
| Which workflows exist? | Read agents/workflows/*.manifest.json now. The id is the file name before .manifest.json. Never list from memory. |
| Claude Code | Give the user the exact /<id> command with its args. Do not run the steps yourself. |
Codex, <id>.codex-plan.json exists | Execute its execution_contract from this parent session with spawn_agent and wait_agent. |
Codex, manifest engine command | Run the manifest's command.run with the chosen options. No agents. |
| Codex, no plan and not a command | Stop. Say this workflow has no Codex plan yet. |
| A member failed or returned nothing usable | The verdict is INCOMPLETE, never a pass. |
| Commit, push, merge or open a PR | Never. Report the tree state and leave it to the user. |
Workflow
Find the library. Installs are symlinks, so resolve this skill's real path first.
agents/workflows/sits three levels above the real skill folder (skills/universal/run-workflow/):lib="$(cd "$(dirname "$(realpath "<this-skill-dir>/SKILL.md")")/../../.." && pwd)" ls "$lib"/agents/workflows/*.manifest.json- List and pick. For each manifest, show the id,
workflow.engineandworkflow.description. If the user named an id with no manifest, say so and list the ids that exist. Take the args fromworkflow.whenToUse. Ask for a missing required arg, such as the frozen spec and acceptance checks of a build loop, instead of inventing one. - Claude Code: hand off. Reply with the one command to type:
/<id>followed by the args objectwhenToUsedescribes. Do not re-implement the workflow inline, because an imitation drops the checks the script enforces in code. If/<id>is not found, the library sync has not linkedagents/workflows/<id>.jsinto the Claude workflows folder; say so and stop. - Codex: execute the plan from the parent session.
- If the plan has a
context_budgetblock, follow itsextractcommand instead of loading the whole file. - If the plan has a
tree_snapshot, run itscommandonce before the first worker, and apply itsstop_rulesafter each read-only phase. A rule that fires ends the run BLOCKED or INCOMPLETE with the rule's stop reason. - Run the
execution_contractphases in order. Each phase names its owner, its primitive (spawn_agent,wait_agent,send_input,close_agent, local reasoning or an immediate return) and its gate. This session does every dispatch, wait, merge and verdict; workers never spawn workers. - Brief each worker on its own: the plan's
task_nameandfork_turns, its rules, and the user's args. Keep toworkspace: one writer at a time. - Keep to the plan's agent cap. Spawn only the members, refuter
count,max_dynamic_membersand rounds (maxRounds, elsemax_rounds_default) it allows. Run no more at once than the session's thread limit, and queue the rest. - Apply
incomplete_rule: a failed, timed-out or malformed member makes the verdict INCOMPLETE. Name that member. Do not rerun it silently or do its part yourself. - Close every worker you spawned before you report.
- If the plan has a
- Report. Give the verdict, the stop reason, the open items or escalation, and any member that failed. When a fixer or builder ran, list its changes from
git status --shortand say that nothing was committed.
Gotchas
- A
.jsfile inagents/workflows/with no manifest still runs on Claude Code as/<id>, but it has no Codex plan. Do not offer it on Codex. - A plan's stop rule is part of the contract. Stopping early at a "good enough" round, or running past the cap, breaks the guarantee the user asked for.
Navigation
- agents-subagents - choose between a saved workflow, subagents and a team; Claude saved-workflow behaviour is in its workflow runtime reference.
- agents/workflows/ - the manifests, Claude scripts and generated Codex plans.
Learnings Loop
When prior decisions or pitfalls are relevant, consult learnings.consolidated.md if present; use learnings.md only for needed history or as the available fallback. Otherwise skip both.
After applying it, if you encountered a pattern worth remembering, a mistake worth preventing, or a domain fact that surprised you, append one dated bullet to learnings.md via agents-skills-feedback-loop/scripts/append_learning.py. Do not modify SKILL.md itself.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

