agentleFS
Sign inStart free
talayashtalayash/spring-fleet/skills/run/SKILL.md

run

Skill2 starsChanged 44 days agoMITView on GitHub

Plan or launch the fleet locally: compose-first per service, with stdout tee'd to logDir so /debug can read it later.

45 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use init, report and 5 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.
  • MicrosoftSkill

    init

    Also in 4 projects that use this

  • MicrosoftSkill

    report

    Turn an exploration (threads, findings, charts) into a single Markdown report — note, blog post, executive summary, KPI dashboard, slide brief, or multi-section analytical report, with embedded charts.

    Also in 3 projects that use this

  • BlockSkill

    plan

    Draft a TDD, PRD, or lightweight plan in the conversation without committing it.

    Also in 4 projects that use this

  • VercelSkill

    setup

    Set up Vercel CLI and project configuration. Use when the user says "set up Vercel", "configure Vercel", "link to Vercel", or "vercel init".

    Also in 5 projects that use this

  • AnthropicSkill

    status

    Case status summary by audience — client-facing (plain language), internal (for the professor), or court-ready (formal caption format per local rules). Same facts, different framing and depth. Use when a student needs to update the client, brief the professor, or prepare a court status report.

    Also in 3 projects that use this

  • Hugging FaceSkill

    implement

    Make tests pass. Invoke after /write-tests produces failing tests.

    Also in 4 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 41 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Confirm with the user: before executing; launching processes is not reversible and may bind to fleet ports already in use.

    line 30
  2. Very specific:

    After launch, suggest /logs --follow (or tail_service_log MCP tool) to confirm services are healthy.

    line 38

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

Plan or launch the Spring Boot fleet locally.

Input: $ARGUMENTS: optional bare service name (default: all), plus optional --execute to actually start the processes (default: print the plan only).

Per-service resolution (from services[].stack produced by /fleet-init):

  • dockerCompose=true → docker compose up -d in the repo (Spring Boot Docker Compose support discovers compose.yaml and wires @ServiceConnection beans automatically, the modern local-dev default).
  • otherwise → gradle bootRun or mvn spring-boot:run, with stdout/stderr tee'd to <logDir>/<service>.log so /debug and /logs work without any logback changes.

Steps:

  1. Locate spring-fleet.config.json (cwd, else suggest /fleet-init).
  2. Plan first (no --execute):
    python "${CLAUDE_PLUGIN_ROOT}/scripts/run_fleet.py" --config ./spring-fleet.config.json [--service NAME]
    Show the JSON plan. Each entry has: service, cwd, mode (compose / gradle / maven), command, logPath, and tee (whether stdout will be redirected).
  3. Confirm with the user before executing; launching processes is not reversible and may bind to fleet ports already in use.
  4. Execute with --execute when the user approves:
    python "${CLAUDE_PLUGIN_ROOT}/scripts/run_fleet.py" --config ./spring-fleet.config.json --execute [--service NAME]
    Each spawned process is detached. Stop them with the usual OS tools (or docker compose down for compose-managed services).
  5. After launch, suggest /logs --follow (or tail_service_log MCP tool) to confirm services are healthy.

Outside Claude Code

  • ${CLAUDE_PLUGIN_ROOT} is the spring-fleet plugin root. Claude Code fills it in; in Codex it is the folder two directories above this SKILL.md.
  • $ARGUMENTS is the text the user supplied with the request.
  • spring-fleet MCP tools: pass config_path (absolute path of the project's spring-fleet.config.json). Codex starts the server outside the project, so it cannot find the config on its own.

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