agentleFS
Sign inStart free
michaelandrewgamblemichaelandrewgamble/workflows-conductor/skills/rerun/SKILL.md

rerun

Skill1 starsChanged 4 months agoMITView on GitHub

Re-run a Claude Code dynamic workflow from a past run's script — a fresh run, useful for killed/failed runs or repeating a job. Use when the user wants to rerun, relaunch, retry, or restart a workflow run.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. robium-ai/robium★ 93same 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 repository3 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 0 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    If no runId was given, call the conductor list_runs tool and ask which run to re-run (killed/failed runs are the usual candidates — show …

    line 9
  2. Very specific:

    Call the conductor export_script tool: {runId} → returns a scriptPath.

    line 10
  3. Very specific:

    If the Workflow tool is not available in this session, fall back to saving it as a named workflow instead: use /conductor:save <runId> …

    line 14

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

/conductor:rerun — relaunch a run's script as a fresh workflow

  1. If no runId was given, call the conductor list_runs tool and ask which run to re-run (killed/failed runs are the usual candidates — show compact rows).
  2. Call the conductor export_script tool: {runId} → returns a scriptPath. Do NOT fetch the script source into context.
  3. Invoke the Workflow tool with {scriptPath: <the returned path>}. This starts a fresh run — no cached agent results carry over, and it runs in this session.
  4. Report the new run ID from the Workflow result. Suggest /conductor:dashboard to watch it live, and /conductor:save <newRunId> <name> if the user wants to keep it as a named command.

If the Workflow tool is not available in this session, fall back to saving it as a named workflow instead: use /conductor:save <runId> <name> and tell the user to invoke /<name>.

Honest limitation: this is a re-run, not a resume — journal-cached results from the original run are not reused (true resume only works inside the session that owns the original run).

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

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.

Check your setup, free