self-improvement
Skill3 starsChanged 3 months agoMITView on GitHub
Read recommendations from lessons learned documents and incrementally improve skills, commands, and agents. Use when user asks to improve skills from lessons, apply recommendations, or requests "/claude-skills:self-improvement".
33 other projects use a version of this.
Adopted by
Most recently taken up by
- TrueImmortal82/open-code-skillstheir own version, first seen Nov 8, 2026
- wagmarsouza/trace-lessontheir own version, first seen Nov 8, 2026
- mahsumaktas/agent-evolution-kittheir own version, first seen Nov 8, 2026
- Elong-svg/business-plan-factorytheir own version, first seen Nov 8, 2026
- cjh-solver/MathModeling-Skills-Arsenaltheir own version, first seen Nov 8, 2026
- cormacc/dotagentstheir own version, first seen Nov 4, 2026
Used with
Projects with it also use skill-vetter, browser-use and 6 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
LaoK2017Skillskill-vetter
Security review and audit tool for AI agent skills. Use when asked to "vet a skill", "check skill security", "audit a skill", or when reviewing skills before installation to detect malicious code, unauthorized access, and suspicious patterns.
Also in 3 projects that use this
Saik0sSkillbrowser-use
AI-driven browser automation via Model Context Protocol
Also in 3 projects that use this
VercelSkillagent-browser
Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.
Also in 6 projects that use this
VercelSkillfind-skills
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
Also in 6 projects that use this
NVIDIASkilldeep-research
Queue deep, multi-step research and analysis tasks to the DeepAgents worker. Supports execution depth presets, request-specific rubrics, SubAgent delegation, and RubricMiddleware cross-validation.
Also in 3 projects that use this
Microsoft AzureSkillhumanizer
Tone enforcement patterns for external-facing community responses
Also in 3 projects that use this
Other versions33 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 33
- wanikua/boluobobo-ai-court-tutorial★ 2.7ksame name
- InternLM/WildClawBench★ 534same name
- pskoett/pskoett-ai-skills★ 327same name
- kunwl123456/zeroclaw-skills-collection★ 27same name
- OpenBMB/EC2-Bench★ 19same name
- eraycc/Openclaw-Skills★ 16same name
- cjh-solver/MathModeling-Skills-Arsenal★ 14same name
- bokan/claude-skill-self-improvement★ 12same name
- hua695/MathModeling-Skills-Arsenal★ 12same name
- lanyasheng/self-improving-agent★ 8same name
23 more not listed
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.
In this repository41 other files it gives its agents.
- cadence-goalsSkill
- ci-feedback-loopSkill
- compoundSkill
- decision-rights-doctrineSkill
- diataxisSkill
- dispatch-gateSkill
- drift-checkSkill
- family-checkSkill
- fix-then-re-review-ladderSkill
- github-projectsSkill
- gitSkill
- goal-treeSkill
- handoffSkill
- improvement-loopSkill
- kb-captureSkill
- kb-compileSkill
- kb-coreSkill
- kb-lessons-bridgeSkill
- kb-lintSkill
- l1-supervisorSkill
- l2-supervisorSkill
- lessons-learnedSkill
- lN-lifecycle-doctrineSkill
- lN-review-doctrineSkill
- medical-recordsSkill
- operator-interview-doctrineSkill
- operator-interviewSkill
- operator-reviewSkill
- planning-workflowSkill
- pr-review-fanoutSkill
- pull-taskSkill
- ralph-wiggumSkill
- reviewSkill
- root-cause-depthSkill
- scan-documentSkill
- self-verifySkill
- skillifySkill
- task-workflowSkill
- testing-without-mocksSkill
- vault-cloudSkill
- verify-inherited-premiseSkill
The file
We split this skill into the rules it gives an agent
8 rules. 0 are common, 5 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 32 edited versions we read keep these.
5
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 31
Safety Model: All changes require explicit user confirmation before application.
- Distinctive: line 52
If the task is repeatable and well-defined → create a script
- Distinctive: line 53
If the task requires judgment or varies by context → document guidance for Claude
- Distinctive: line 54
If both → script handles mechanics, Claude handles decisions
- Distinctive: line 98
When this skill is invoked:
- Very specific: line 135
When --batch is used, each recommendation analysis is dispatched to a subagent via the dispatch-task operation:
- Very specific: line 144
Scan: Run operations/scan-recommendations.md to find pending recommendations (inline — needs file system access)
- Very specific: line 156
If a dispatch returns status: fallback, skip that recommendation and report it as "analysis failed — manual review needed."
“Common” is measured: kept by at least 6 in 10 of the 32 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.
Files
Self-Improvement Skill
Closes the feedback loop between /claude-skills:lessons-learned analysis and system enhancement. Reads recommendations from lessons learned documents and incrementally implements improvements to skills, commands, and agents.
Core Concepts
Improvement Cycle:
- Scan - Find pending recommendations from lessons learned files
- Analyze - Assess feasibility and identify target files
- Propose - Generate specific changes for review
- Apply - Implement with user confirmation and traceability
Safety Model: All changes require explicit user confirmation before application.
Traceability: Each improvement links back to its source REC-ID.
Design Principles
Scripts vs Generative Tasks
Prefer deterministic scripts for repeatable, precision-critical operations:
| Use Scripts For | Use Claude For |
| File parsing and validation | Analyzing patterns and context |
| Structured data extraction | Generating documentation |
| Session/environment setup | Design decisions and tradeoffs |
| Status checks and reporting | Synthesizing recommendations |
| Template expansion | Adapting to novel situations |
Why: Scripts provide consistency, testability, and predictable behavior. Claude excels at judgment, synthesis, and handling variability.
When implementing improvements:
- If the task is repeatable and well-defined → create a script
- If the task requires judgment or varies by context → document guidance for Claude
- If both → script handles mechanics, Claude handles decisions
Examples:
validate-tmux-session.sh- Script checks window names (deterministic)create-tmuxp-session.sh- Script creates standard layout (repeatable)- Analyzing lesson patterns - Claude synthesizes (variable, requires judgment)
- Proposing code changes - Claude generates (context-dependent)
Operations
1. List Recommendations (Default)
When: User requests /claude-skills:self-improvement without arguments
Implementation: Load operations/scan-recommendations.md
Quick summary: Find and display pending skill/command recommendations ranked by priority
2. Analyze Recommendation
When: User selects a specific REC-ID to investigate
Implementation: Load operations/analyze-improvement.md
Quick summary: Deep analysis of recommendation feasibility, target files, and dependencies
3. Propose Changes
When: User wants to see proposed edits before applying
Implementation: Load operations/propose-changes.md
Quick summary: Generate diff-style preview of changes with rationale
4. Apply Improvement
When: User approves proposed changes
Implementation: Load operations/apply-improvement.md
Quick summary: Apply edits with confirmation, bump skill version and update CHANGELOG.md, update source file to mark REC as implemented
Execution
When this skill is invoked:
Step 1: Determine operation based on arguments
| Arguments | Operation |
| (none) | List pending recommendations |
REC-XXX | Analyze specific recommendation |
REC-XXX --propose | Generate proposed changes |
REC-XXX --apply | Apply with confirmation |
--batch | Process multiple recommendations |
Step 2: Load appropriate operation file
Read(file_path: "${CLAUDE_PLUGIN_ROOT}/skills/self-improvement/operations/{operation}.md")Step 3: Execute operation steps
Step 4: Report results and next actions
Options
| Option | Type | Default | Description |
REC-XXX | string | none | Target specific recommendation by ID |
--propose | boolean | false | Show proposed changes without applying |
--apply | boolean | false | Apply changes (requires confirmation) |
--batch | boolean | false | Process multiple recommendations |
--category | string | all | Filter by category (Workflow/Commands/Utilities/Skills) |
--priority | string | all | Filter by priority (HIGH/MEDIUM/LOW) |
--limit | int | 10 | Max recommendations to display |
--dry-run | boolean | false | Simulate apply without writing files |
Batch Mode with Subagent Dispatch
When --batch is used, each recommendation analysis is dispatched to a subagent via the dispatch-task operation:
Read: skills/task-workflow/operations/dispatch-task.md
Read: skills/task-workflow/references/subagent-dispatch.mdBatch Flow
- Scan: Run
operations/scan-recommendations.mdto find pending recommendations (inline — needs file system access) - Dispatch each: For each recommendation (up to
--limit), dispatch a subagent with:prompt: The recommendation's source text, target file paths, andoperations/analyze-improvement.md+operations/propose-changes.mdinstructionstask_subject: "Analyze: REC-XXX"max_retries: 1
- Review: Parent receives each
dispatch_resultand presents the proposal to the user - Apply: On user confirmation, apply changes inline via
operations/apply-improvement.md
Dispatching analysis to subagents reduces context window consumption — each subagent reads source files and generates proposals independently. The parent only sees the summarized proposal, not all the intermediate file reads.
Fallback
If a dispatch returns status: fallback, skip that recommendation and report it as "analysis failed — manual review needed."
Example Usage
# List pending recommendations
/claude-skills:self-improvement
# Analyze specific recommendation
/claude-skills:self-improvement REC-001
# See proposed changes
/claude-skills:self-improvement REC-001 --propose
# Apply with confirmation
/claude-skills:self-improvement REC-001 --apply
# Filter by category
/claude-skills:self-improvement --category Workflow --priority HIGH
# Batch mode (with confirmation per item)
/claude-skills:self-improvement --batch --limit 5Output Format
List Mode:
## Pending Recommendations
| Priority | REC-ID | Category | Title | Source |
|----------|--------|----------|-------|--------|
| HIGH | REC-001 | Workflow | Add parallel file reading | 20260115-Lessons.md |
| MEDIUM | REC-003 | Commands | Cache git status results | 20260114-Lessons.md |
Found 5 actionable recommendations. Use `/self-improvement REC-XXX` to analyze.Analyze Mode:
## REC-001: Add parallel file reading
**Source**: 20260115-Lessons Learned - Task Workflow.md
**Category**: Workflow | **Priority**: HIGH | **Effort**: Medium
### Context
[Original recommendation text]
### Target Files
- `skills/task-workflow/operations/workspace-setup.md` (line 45-60)
### Feasibility
- Complexity: Low
- Dependencies: None
- Conflicts: None detected
### Next Steps
Use `--propose` to see specific changes or `--apply` to implement.Progressive Disclosure
Load operation details on-demand:
Operations:
operations/scan-recommendations.md- Find and parse recommendationsoperations/analyze-improvement.md- Feasibility analysisoperations/propose-changes.md- Generate specific editsoperations/apply-improvement.md- Apply with confirmation
References:
references/recommendation-categories.md- Category to target mappingreferences/improvement-workflow.md- Full cycle workflow guidance
Error Handling
No recommendations found: Display "No pending recommendations found. Run /claude-skills:lessons-learned to generate."
Invalid REC-ID: Display "REC-ID not found. Use /claude-skills:self-improvement to list available."
Target file not found: Display warning, suggest manual review
Apply fails: Rollback changes, display error, preserve original state
Integration Points
- lessons-learned skill: Source of recommendations
- obsidian-notes skill: Note creation and updates
- git skill: Optional commit after apply
- Native Task Tools: Auto-complete tasks containing REC-ID, store source file in task metadata
See Also
/claude-skills:lessons-learned- Generate recommendations/lessons-learned --aggregate- Aggregate patterns across sessionsreferences/improvement-workflow.md- Review cadence and decision criteriaimprovement-loop- Invokes this skill's apply machinery from the meta pane; drafts each improvement as a PR-gated change against the target surface's repo (seeimprovement-loop/references/surface-repo-map.md)
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
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.

