agentleFS
Sign inStart free
lukasrepubliclukasrepublic/agentic-foundry/skills/fleet/SKILL.md

fleet

Skill1 starsChanged 3 months agoMITView on GitHub

The session roster (/foundry:fleet) — native `/list-agents` annotated with each row's foundry programme, over the NATIVE session/container list. Read-only/advisory. Trigger to see all your parallel sessions and containers at a glance with their foundry context, or when supervising many sessions and asking "what is each one doing".

18 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use loop, learn and 1 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.
  • HeshamFSSkill

    loop

    Run a command or check on a recurring interval

    Also in 4 projects that use this

  • genomewalkerSkill

    learn

    Learn from web sources, generate SKILL.md, and store key patterns in soul memory. Trigger keywords: learn, skill-gen, web-learn, documentation, tutorial.

    Also in 3 projects that use this

  • Google CloudSkill

    triage

    Gather context on a change or bug and plan the implementation.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 15 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

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

    Run /list-agents — the native enumerator (this machine's sessions, plus container sessions while both sides are on Remote Control).

    line 8
  2. Very specific:

    Read-only, never acts. For the cross-session message-kind convention (FINDING / NEEDS-INTERFACE / CHALLENGE / HANDOFF), see …

    line 14

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

/foundry:fleet

Run /list-agents — the native enumerator (this machine's sessions, plus container sessions while both sides are on Remote Control). Foundry adds ONE overlay: for a row whose name matches a known container/session name, annotate it with that workspace's programme — next_action read from .foundry/releases/<programme>/state.yaml. Nothing else; the prior registry-based roster scripts were retired in R4 (v1.15.0) — this skill is the only surface left.

Read-only, never acts. For the cross-session message-kind convention (FINDING / NEEDS-INTERFACE / CHALLENGE / HANDOFF), see docs/how-to/deck-and-containers.md and scripts/foundry_message_kind.py.

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