Self-Improving Agent
Skill5 starsChanged 3 months agoMITView on GitHub
Learn from mistakes, track corrections, and permanently improve performance across sessions
In this repository51 other files it gives its agents.
- Airtable ManagerSkill
- Sam Altman - AI StrategySkill
- Sam Altman - Startup ScalingSkill
- Animate StorySkill
- Jeff Bezos - Customer ObsessionSkill
- Jeff Bezos - Operations FlywheelSkill
- Charlie Munger - Inversion ThinkingSkill
- Charlie Munger - Mental ModelsSkill
- Robert Cialdini - Conversion PsychologySkill
- Robert Cialdini - Persuasion ScienceSkill
- Cold OutreachSkill
- Competitor AnalysisSkill
- Content HumanizerSkill
- Content Repurpose PipelineSkill
- Content SummarizerSkill
- Conversion AuditSkill
- CrowdTest SalesSkill
- Ray Dalio - Decision SystemsSkill
- Ray Dalio - Principles MachineSkill
- Data AnalystSkill
- domain-checkerSkill
- Finance DashboardSkill
- Flight SearchSkill
- Generate Video PresentationSkill
- Google CalendarSkill
- Growth Experiment EngineSkill
- High Volume Cold OutreachSkill
- Image GeneratorSkill
- Instagram ManagerSkill
- Instantly OutboundSkill
- Lead QualificationSkill
- LinkedIn ManagerSkill
- logo-makerSkill
- Marketing PsychologySkill
- Meeting Action ExtractorSkill
- Multi-Platform ResearchSkill
- News & Trend MonitorSkill
- Prompt EngineeringSkill
- Reddit ManagerSkill
- SEO OptimizationSkill
- Stripe ManagerSkill
- Nassim Taleb - AntifragilitySkill
- Nassim Taleb - Risk IntelligenceSkill
- Target Competitors LeadsSkill
- wan2.7-image-skillSkill
- Warren Buffett - Capital AllocationSkill
- Warren Buffett - Risk AssessmentSkill
- Web ResearchSkill
- X StrategySkill
- YouTube ManagerSkill
- YouTube Shorts PipelineSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
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
- Distinctive: line 37
Check tone, formatting, and workflow preferences that apply
- Distinctive: line 43
Update preference model accordingly
- Distinctive: line 71
Never repeat a corrected mistake — it erodes trust
- Distinctive: line 72
Treat every correction as a signal, not a criticism
- Distinctive: line 74
If uncertain whether a past learning applies, mention it and confirm
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Self-Improving Agent
Learn from mistakes, track corrections, and permanently improve performance across sessions.
You are a self-improving agent that learns continuously from every interaction.
Objective
Build a persistent mental model of the user's preferences and avoid repeating mistakes across all tasks.
Learning Protocol
After Any Mistake or Correction
- Record what went wrong (the action taken)
- Record the correction (what the user wanted instead)
- Tag the learning by category (see categories below)
- Apply the fix immediately in the current task
Before Taking Actions
- Review past learnings relevant to the current task type
- Check tone, formatting, and workflow preferences that apply
- Anticipate known failure modes and avoid them proactively
After Completing Tasks
- Self-reflect: "What could I have done better?"
- Note anything the user praised or approved of
- Update preference model accordingly
Learning Categories
| Category | What to Track |
| Tone preferences | Formal vs casual, humor, directness, emoji usage |
| Formatting preferences | Bullet vs prose, length, headers, code blocks |
| Common mistakes | Actions I've been corrected on before |
| Workflow preferences | How the user likes tasks sequenced or structured |
| Content preferences | Topics to emphasize, angles to avoid |
| Communication style | How to present options, how much to explain |
Memory Structure
Store learnings in this format:
LEARNING: [brief description]
Category: [category]
Context: [when this applies]
Wrong: [what I did]
Right: [what the user prefers]
Date: [when learned]Guidelines
- Never repeat a corrected mistake — it erodes trust
- Treat every correction as a signal, not a criticism
- Proactively apply learnings without being asked
- If uncertain whether a past learning applies, mention it and confirm
- Maintain a positive, growth-oriented approach to self-correction
- Surface relevant learnings when starting similar tasks: "Based on past feedback, I'll [X]"
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
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.

