agentleFS
robonuggetsrobonuggets/calibrate/SKILL.md

calibrate

Skill18 starsChanged 7 months agoMITView on GitHub

In-session self-improvement. Reviews the current conversation for corrections, preferences, and patterns, then suggests specific skill/setup updates. Triggers on "calibrate", "what can you improve", "update your skills", "what did we learn", "tune up".

6 other projects use a version of this, 1 of them edited.

Adopted by

Most recently taken up by

  • Other versions6 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 1

    1. robonuggets/skills★ 3658% same

    Wrote their own version · 5

    1. grainulation/grainulator★ 86same name
    2. sparkline-ventures/product-eval★ 15same name
    3. ronniepinnell/casper★ 1same name
    4. mehboobali98/rmine-skills★ 0same name
    5. sethatwood/belay★ 0same 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

8 rules. 0 are common, 7 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 6 edited versions we read keep these.

  • 7

    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:

    After a task with multiple corrections

    line 17
  2. Very specific:

    When you say "calibrate", "what can you improve", "tune up", "update your skills"

    line 18
  3. Distinctive:

    Max 7 suggestions: If you find more, prioritize by impact (repeated corrections > one-offs).

    line 64
  4. Distinctive:

    Only suggest changes the data supports: Don't pad with generic improvements.

    line 66
  5. Distinctive:

    Wait for the user to respond with which numbers to apply (e.g.

    line 71
  6. Distinctive:

    If updating a skill, re-read it after editing to verify it's coherent

    line 76
  7. Distinctive:

    If updating memory, follow the memory system rules (write file + update MEMORY.md index)

    line 77
  8. Distinctive:

    No follow-up needed. Changes are live for the next time the skill/rule is invoked.

    line 81

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

Calibrate: In-Session Self-Improvement

What This Does

Reviews the current conversation and suggests specific updates to skills, CLAUDE.md rules, memory, or workflows based on what just happened. You pick which suggestions to apply.

When to Use

  • End of a work session
  • After a task with multiple corrections
  • When you say "calibrate", "what can you improve", "tune up", "update your skills"

Process

Step 1: Scan the Conversation

Review everything in the current session. Look for:

  • Corrections — where the user said "no", "wrong", "not that", "I meant X"
  • Preferences revealed — format choices, tone adjustments, workflow preferences
  • Process gaps — steps you missed that a skill should encode
  • Repeated patterns — same type of correction more than once = systemic issue
  • Things that worked — approaches the user confirmed or accepted without pushback

Step 2: Match to Updateable Targets

For each finding, identify WHERE the fix belongs:

  • Skill file — if the issue is about how a specific task is executed
  • CLAUDE.md — if the issue is about general agent behavior or rules
  • Memory — if it's a preference or context that should persist across sessions
  • Workflow/cron — if it's about when or how automated tasks run
  • SOUL.md / persona file — if it's about tone or writing style (rare, check with the user)

Step 3: Present Suggestions

Format as a numbered list. Each suggestion should be:

[number]. [TARGET: filename] — [what to change]
Brief why: [one sentence explaining the pattern that triggered this]

Example:

1. SKILL: thumbnail-skill — Add rule to always generate 3 thumbnail variations, not 1
Brief why: You asked for alternatives twice this session after I gave a single option.

2. CLAUDE.md — Add "never suggest routing to other agents" to red lines
Brief why: You corrected me when I suggested handing off to another agent.

3. MEMORY — Save preference: user prefers kebab-case for all file names
Brief why: You renamed two files I created in camelCase.

Rules for suggestions:

  • Max 7 suggestions. If you find more, prioritize by impact (repeated corrections > one-offs).
  • Be specific. Not "improve writing quality" but "add rule: no sentences over 20 words in community posts."
  • Only suggest changes the data supports. Don't pad with generic improvements.
  • If nothing meaningful to update, say so. "Clean session — nothing to calibrate" is a valid output.

Step 4: Apply

Wait for the user to respond with which numbers to apply (e.g. "do 1 and 3", "all", "skip 2").

Then:

  1. Make the changes to the target files
  2. Confirm each change with the file path and a one-line summary
  3. If updating a skill, re-read it after editing to verify it's coherent
  4. If updating memory, follow the memory system rules (write file + update MEMORY.md index)

Step 5: Done

No follow-up needed. Changes are live for the next time the skill/rule is invoked.

What NOT to Suggest

  • Changes that are already in the relevant skill or CLAUDE.md (check first)
  • Generic "best practices" not grounded in this session's data
  • Temporary fixes for one-off situations
  • Changes to other agents' files unless this agent has write access

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.