agentleFS
RoyoTechRoyoTech/royo-learn/skills/capture-learning/SKILL.md

capture-learning

Skill7 starsChanged 4 months agoMITView on GitHub

Capture a reusable lesson after a verified bug fix, user correction, non-obvious discovery, recurring failure, or successful procedure. Search first, then call royo-learn. Capturing never publishes or changes agent behavior.

14 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

6 rules. 0 are common, 4 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 14 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Do not use for routine progress or a session dump.

    line 23
  2. Very specific:

    Search learning_search using the central terms.

    line 27
  3. Distinctive:

    Search Engram through the same tool when useful.

    line 28
  4. Distinctive:

    Do not curate or publish in the same step unless the user explicitly requests the full cycle and evidence is sufficient.

    line 33
  5. Distinctive:

    Never include private chain-of-thought, secrets, credentials, personal data, or raw conversation history.

    line 49
  6. Very specific:

    If no lesson qualifies, state NO_REUSABLE_LEARNING and do not call capture.

    line 53

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

Capture Learning

Use when

  • the user corrects the agent;
  • a non-obvious bug is fixed;
  • a failed approach reveals a prevention rule;
  • a procedure succeeds repeatedly;
  • a tool limitation is discovered;
  • the same explanation is being repeated;
  • a significant task ends with a reusable lesson.

Do not use for routine progress or a session dump.

Workflow

  1. Search learning_search using the central terms.
  2. Search Engram through the same tool when useful.
  3. Decide whether there is an atomic, reusable lesson.
  4. Separate direct observation from interpretation.
  5. Gather only necessary evidence.
  6. Call learning_capture.
  7. Do not curate or publish in the same step unless the user explicitly requests the full cycle and evidence is sufficient.

Required quality

The candidate must contain:

  • minimal context;
  • direct observation;
  • reusable lesson;
  • procedure;
  • limits;
  • confidence;
  • evidence level;
  • retrieval terms;
  • source actor/session.

Never include private chain-of-thought, secrets, credentials, personal data, or raw conversation history.

Outcome

If no lesson qualifies, state NO_REUSABLE_LEARNING and do not call capture.

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.