agentleFS
Sign inStart free
GabrielKqwGabrielKqw/weave-agent-workflow/skills/weave-gain/SKILL.md

weave-gain

Skill5 starsChanged 2 months agoMITView on GitHub

Show the measured terminal-output reduction for this project from local Weave run history: bytes received versus presented, percentage saved, and approximate tokens. Use when the user says "weave gain", "/weave-gain", "token savings", "output savings", or "Weave scoreboard". One-shot display, changes nothing.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 1 is distinctive, and 1 is 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.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Run from the project root:

    line 13
  2. Very specific:

    Only numbers the command printed.

    line 41

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

Weave Gain

Run from the project root:

weave gain

(node "<plugin-root>/cli/weave.js" gain when weave is not on the PATH, or the MCP gain tool.) For savings Weave could have had in past sessions, run weave discover.

Scoreboard

Render the real numbers as plain ASCII bars; the label carries the exact figure:

  weave gain                          <N> recorded commands

  Output   received   ████████████████████  <raw bytes>
           presented  ██████··············  <report bytes>   ▼ <percent>%
  Tokens   saved      ~<tokens>  (≈4 bytes/token)

  Next:  /weave-debt   (deferred shortcuts)
         /weave-audit  (what is still cuttable)

Honesty boundary

Only numbers the command printed. No history means No recorded runs yet., not an estimate. Token counts are approximate and labeled as such.

Boundaries

One-shot display. Edits nothing, changes no mode.

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