agentleFS
GrinvGrinv/mal-mcp/.agents/skills/self-learning/SKILL.md

self-learning

Skill2 starsChanged 2 months agoMITView on GitHub

After an audit/check finds a bug its own checklist should have caught, close that gap in the skill itself — not just fix the code. Run right after reporting/fixing any audit finding.

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If an existing bullet already covers this general class of check, sharpen/specialize it with the missed detail — don't add a new bullet …

    line 12
  2. Distinctive:

    Only add a brand-new bullet if nothing existing is even adjacent.

    line 15
  3. Distinctive:

    Keep additions to 1-2 lines.

    line 16
  4. Distinctive:

    If a skill file is drifting toward bloat (bullets turning into short essays), that's a signal to prune/merge, not to keep appending — …

    line 19

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

Self-learning — close the gap in the skill that missed it

For each confirmed finding from an audit/check pass:

  1. Identify which skill's checklist should have caught this — don't stop at fixing the code.
  2. If an existing bullet already covers this general class of check, sharpen/specialize it with the missed detail — don't add a new bullet next to it.
  3. Only add a brand-new bullet if nothing existing is even adjacent.
  4. Keep additions to 1-2 lines. No walkthroughs, no multi-sentence examples — these files compound over many passes; a short parenthetical example is fine, a paragraph is not.
  5. If a skill file is drifting toward bloat (bullets turning into short essays), that's a signal to prune/merge, not to keep appending — periodically re-read the whole file and tighten instead of only adding.

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.