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

logs

Skill2 starsChanged 44 days agoMITView on GitHub

Tail or aggregate logs from the fleet's services: file-based when present, kubectl-based when the config has a k8s block (for mirrord / in-cluster runs).

6 other projects use a version of this.

Adopted by

Most recently taken up by

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 6 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:

    Run the aggregator, passing through the relevant flags:

    line 15
  2. Very specific:

    If a bare service name was given in $ARGUMENTS, pass it as --service.

    line 19

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

Show fleet logs.

Input: $ARGUMENTS: optional service name (default: all), plus optional --grep, --lines, --follow, --k8s.

Steps:

  1. Locate spring-fleet.config.json (cwd, else suggest /fleet-init).
  2. Run the aggregator, passing through the relevant flags:
    python "${CLAUDE_PLUGIN_ROOT}/scripts/tail_logs.py" --config ./spring-fleet.config.json [--service NAME] [--grep TEXT] [--lines N] [--follow] [--k8s]
    • If a bare service name was given in $ARGUMENTS, pass it as --service.
    • all or empty → all services.
    • --k8s falls back to kubectl logs -l <podSelectorTemplate> for any service whose file-based log is missing. Requires a k8s block in the config (namespace + optional context + podSelectorTemplate). mirrord users get this for free: the local service runs against the shared cluster, the other services log to stdout in-cluster, kubectl reads them.
  3. Present the tagged, aggregated output ([service/k8s] for kubectl-sourced lines). For --follow, stream until interrupted.

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