agentleFS
TheAstroByteTheAstroByte/astrobyte-agent-skills/skills/continual-improvement-check/SKILL.md

continual-improvement-check

Skill1 starsChanged 14 days agoMITView on GitHub

Use when planning or developing an AI or agent workflow that will handle repeated real tasks. Ask whether its outcomes could improve later versions.

The file

Files
SKILL.md

Continual improvement check

For an AI or agent workflow that will handle repeated real tasks, ask:

Could representative real outcomes from this system become evaluated improvements to later versions?

Record a one-sentence answer in the plan. If yes, name one outcome signal worth keeping and one quality check that could judge it. Stop there unless the user asks to design the improvement loop.

Done when the plan contains a direct answer.

Inspired by Shopify Engineering's Sidekick continual-learning loop: https://shopify.engineering/sidekicks-continual-learning-loop

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.