agentleFS
Sign inStart free
zedarvateszedarvates/frugal-skills/skills/fleet/SKILL.md

fleet

Skill1 starsChanged 31 days agoMITView on GitHub

Instructions for the upstream workflow: Aggregate status across the fleet, sortable by project tokens saved, lines of code or number of fixes — a read-only view over the canonical fleet registry that the dashboard writes. Use when you need a portfolio-level roll-up across projects. This module deliberately reads the dashboard registry instead of keeping its own, so the two can no longer diverge. Not for editing the registry — use dashboard (fleet add); not for measuring one project's context cost — use context-profiler.

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

Create a free account to mount
Files
SKILL.md

fleet — portfolio roll-up, read-only

Package scope and prerequisites

This catalog ships instructions, not the executable runtime. Python modules, scripts, local services and optional tools named below must be installed separately from the upstream project. Check their availability before running commands; if they are missing, explain the prerequisite instead of claiming execution or results. The host agent may use model tokens while following these instructions.

Purpose

A single view over the fleet registry, sorted on demand. It used to keep its own registry under ~/.botte/fleet, which silently diverged from the one dashboard wrote; it now reads the canonical source.

python -m skills.fleet.status --sort project_tokens_saved
python -m skills.fleet.status --sort loc
python -m skills.fleet.status --sort fixes

When NOT to use

  • You need to add or change a fleet entry — use dashboard.
  • You need one project's prefix cost — use context_profiler.

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