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

fleet-init

Skill2 starsChanged 44 days agoMITView on GitHub

Scan a repos directory and generate (or update) spring-fleet.config.json for the fleet.

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. Brandondaymdr/Claude-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 repository10 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, 1 is distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    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. Distinctive:

    Run the scanner to produce a draft:

    line 15
  2. Very specific:

    Write spring-fleet.config.json to the user's project root.

    line 32
  3. Very specific:

    If logs are console-only or scattered, suggest the spring-fleet-logging-setup skill so /debug has stable per-service logs.

    line 34

≈ “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

Initialize or refresh the fleet config.

Input: $ARGUMENTS: optional repos root path. If omitted, ask the user (or use an existing config's reposRoot).

Steps:

  1. Determine the repos root. Confirm it exists.
  2. Run the scanner to produce a draft:
    python "${CLAUDE_PLUGIN_ROOT}/scripts/scan_repos.py" --root <reposRoot>
    It detects build tool, services vs shared libs, ports, and context paths.
  3. The draft pre-fills traceKeys with the modern OTel-first default (trace_id, span_id, sessionId, requestId) and seeds topology from any Backstage catalog-info.yaml files it finds at repo roots (each dependsOn: component:* becomes a [from, to] edge; components with no inbound dependency become entries). Ask the user to confirm:
    • traceKeys: which MDC keys actually identify a request/session in their fleet (drop entries that are never emitted).
    • topology: confirm or amend the Backstage-derived entries and edges; for fleets without Backstage, fill these in manually. Pre-fill from any existing spring-fleet.config.json if present.
  4. Validate the result against ${CLAUDE_PLUGIN_ROOT}/spring-fleet.config.schema.json (required fields, types).
  5. Write spring-fleet.config.json to the user's project root. Remind them it is .gitignored and must never be committed.
  6. If logs are console-only or scattered, suggest the spring-fleet-logging-setup skill so /debug has stable per-service logs.

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.

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