agentleFS
unisoneunisone/claude-learner/skills/learning/SKILL.md

learning

Skill1 starsChanged 10 months agoMITView on GitHub

Self-improving agent patterns. Use when detecting corrections, proposing rules, or managing learned behaviors.

8 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions8 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 8

    1. alxyrgin/secondbrain_ai★ 17same name
    2. HsuanYuLee/polaris★ 5same name
    3. marco-souza/skills★ 3same name
    4. amoraleda/skills★ 2same name
    5. DaraBoth/skilljmskill★ 2same name
    6. akumidv/ai_akmon★ 1same name
    7. qkitzero/kage-bunshin★ 1same name
    8. zinan92/skills-repo★ 1same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

The file

We split this skill into the rules it gives an agent

5 rules. 0 are common, 4 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 5 edited versions we read keep these.

  • 4

    Distinctive

    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:

    If MCP is connected, you have these tools:

    line 33
  2. Distinctive:

    Detect corrections automatically: - When user says "actually...", "no, use...", "don't do X", log it

    line 45
  3. Distinctive:

    Propose rules for patterns: - If you see repeated corrections, propose a rule

    line 46
  4. Very specific:

    Check rules periodically: - Use get_rules to remind yourself of learned behaviors

    line 47
  5. Distinctive:

    Don't over-rule: - Not every correction needs a permanent rule

    line 48

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

Claude Learner - Self-Improvement Skill

You have access to claude-learner, a system that turns corrections into permanent rules.

When to Use

  • User corrects you ("No, don't do X, do Y instead")
  • You make a repeated mistake
  • User expresses a preference
  • A better pattern is discovered

Available Commands

CommandWhat It Does
/learner:statusCheck daemon and rules status
/learner:rulesList all rules
/learner:approve <id>Approve a pending rule
/learner:reject <id>Reject a pending rule
/learner:startStart the learning daemon
/learner:stopStop the learning daemon

MCP Tools

If MCP is connected, you have these tools:

  • log_correction - Log a correction event
  • propose_rule - Propose a new rule
  • get_rules - Get active rules
  • get_pending_rules - Get rules awaiting approval
  • approve_rule - Approve a rule
  • reject_rule - Reject a rule
  • get_stats - Get learning statistics

Best Practices

  1. Detect corrections automatically - When user says "actually...", "no, use...", "don't do X", log it
  2. Propose rules for patterns - If you see repeated corrections, propose a rule
  3. Check rules periodically - Use get_rules to remind yourself of learned behaviors
  4. Don't over-rule - Not every correction needs a permanent rule

Example Flow

User: "Don't use rm, use trash instead"

1. Log correction: log_correction({ 
     pattern: "using rm command",
     correction: "use trash instead of rm",
     context: "file deletion"
   })

2. If pattern repeats, propose rule: propose_rule({
     content: "Always use `trash` instead of `rm` for file deletion",
     trigger: "rm command usage"
   })

3. Rule goes to pending → user approves → permanently active

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.