agentleFS
ArcticFox2029ArcticFox2029/chamnan/skills/promote/SKILL.md

promote

Skill10 starsChanged 8 days agoMITView on GitHub

Turn a scratch script into a permanent tool this repo keeps. Use when a check, report, or analysis has proved worth running more than once.

17 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use research.

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.
  • NVIDIASkill

    research

    Before designing a feature, research how comparable libraries solve the problem, check best practices, known pitfalls, and upstream changes. Use when starting a new feature, investigating an unfamiliar area, or the user asks to research something.

    Also in 3 projects that use this

The file

Files
SKILL.md

Keep a script instead of rewriting it

chamnan-promote <file> <name> --desc "what it checks"
chamnan-promote --list

When

The plugin will tell you when the same scratch script has been written a third time. Act on that rather than filing it away — the file is still on disk at that moment, and next session it will not be.

Also promote without being told when a script is something the repo will want to re-run: a regression check, a report the user asks for regularly, a migration that will be repeated per environment.

Write the description

--desc is what a future session sees when deciding whether to use the tool instead of writing a new script. --desc "checks the save file" will not do that. --desc "verifies every profile in game/saves/ still migrates cleanly to the current GAME_VERSION" will.

Before promoting

Make it runnable from the repo root with no arguments, or with arguments it explains when given none. A tool that only works from the directory it was written in gets rewritten next time anyway.

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.