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

save

Skill1 starsChanged 4 months agoMITView on GitHub

Save a Claude Code dynamic workflow run's script as a reusable slash-command workflow (the "s" action from the CLI /workflows panel). Use when the user wants to keep, save, or reuse a workflow run.

36 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use load, ingest and 8 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • TheLatentSpaceLabSkill

    load

    Load a document into memory for RAG

    Also in 4 projects that use this

  • JaimeGBASkill

    ingest

    Digest an external source (article, paper, transcript, URL, book chapter) and integrate its content into the knowledge base

    Also in 8 projects that use this

  • ArtemXTechSkill

    query

    Query data from this vault. USE WHEN user asks about projects, clients, tasks, daily notes. Use grep to extract frontmatter - do NOT read full files.

    Also in 4 projects that use this

  • szweibelSkill

    idea

    Generate a wide field of options when the user is brainstorming, exploring, expanding, or pressure-testing — not recommending or implementing

    Also in 3 projects that use this

  • Microsoft AzureSkill

    lint

    Run all linting and spell checking for TypeScript and Rust code. Run this before committing to catch style issues, clippy warnings, and misspellings.

    Also in 5 projects that use this

  • HK-hubSkill

    defuddle

    Extract clean markdown content from web pages using Defuddle CLI, removing clutter and navigation to save tokens. Use instead of WebFetch when the user provides a URL to read or analyze, for online documentation, articles, blog posts, or any standard web page.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 31 edited versions we read keep these.

  • 0

    Distinctive

    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 the user gave no runId, call the conductor list_runs tool first and ask which run to save (show compact rows only).

    line 13
  2. Very specific:

    Call the conductor save_workflow tool: {runId, name, scope: "project"|"user", cwd: <absolute project path>, force: <true only if --force>}.

    line 14
  3. Very specific:

    If the source run is older than ~25 days (expiresInDays ≤ 5 in list_runs), mention the save just rescued it from session cleanup.

    line 17

“Common” is measured: kept by at least 6 in 10 of the 31 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.

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

/conductor:save — save a run as a reusable workflow

Saves the run's script so it can be invoked as /<name> in later sessions. Project scope (default) writes to the nearest .claude/workflows/ (shared via git); --user writes to ~/.claude/workflows/ (personal).

Procedure

  1. If the user gave no runId, call the conductor list_runs tool first and ask which run to save (show compact rows only).
  2. Call the conductor save_workflow tool: {runId, name, scope: "project"|"user", cwd: <absolute project path>, force: <true only if --force>}.
  3. On saved: false with an "exists" reason: report the conflict and require an explicit --force from the user — never force on your own.
  4. On success, report the target path, the /​<name> invocation, and the note field if present (meta.name mismatch). Remind the user the command becomes available in new sessions.
  5. If the source run is older than ~25 days (expiresInDays ≤ 5 in list_runs), mention the save just rescued it from session cleanup.

Fallback if MCP tools are unavailable:

node "${CLAUDE_PLUGIN_ROOT}/server/cli.js" save <runId> <name> [--user] [--force] --cwd "$PWD"

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.

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free