agentleFS
pfeffpfeff/claude-skills/skills/self-improvement/SKILL.md

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

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.
  • LaoK2017Skill

    skill-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

  • Saik0sSkill

    browser-use

    AI-driven browser automation via Model Context Protocol

    Also in 3 projects that use this

  • VercelSkill

    agent-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

  • VercelSkill

    find-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

  • NVIDIASkill

    deep-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 AzureSkill

    humanizer

    Tone enforcement patterns for external-facing community responses

    Also in 3 projects that use this

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
  1. Distinctive:

    Safety Model: All changes require explicit user confirmation before application.

    line 31
  2. Distinctive:

    If the task is repeatable and well-defined → create a script

    line 52
  3. Distinctive:

    If the task requires judgment or varies by context → document guidance for Claude

    line 53
  4. Distinctive:

    If both → script handles mechanics, Claude handles decisions

    line 54
  5. Distinctive:

    When this skill is invoked:

    line 98
  6. Very specific:

    When --batch is used, each recommendation analysis is dispatched to a subagent via the dispatch-task operation:

    line 135
  7. Very specific:

    Scan: Run operations/scan-recommendations.md to find pending recommendations (inline — needs file system access)

    line 144
  8. Very specific:

    If a dispatch returns status: fallback, skip that recommendation and report it as "analysis failed — manual review needed."

    line 156

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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:

  1. Scan - Find pending recommendations from lessons learned files
  2. Analyze - Assess feasibility and identify target files
  3. Propose - Generate specific changes for review
  4. 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 ForUse Claude For
File parsing and validationAnalyzing patterns and context
Structured data extractionGenerating documentation
Session/environment setupDesign decisions and tradeoffs
Status checks and reportingSynthesizing recommendations
Template expansionAdapting to novel situations

Why: Scripts provide consistency, testability, and predictable behavior. Claude excels at judgment, synthesis, and handling variability.

When implementing improvements:

  1. If the task is repeatable and well-defined → create a script
  2. If the task requires judgment or varies by context → document guidance for Claude
  3. 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

ArgumentsOperation
(none)List pending recommendations
REC-XXXAnalyze specific recommendation
REC-XXX --proposeGenerate proposed changes
REC-XXX --applyApply with confirmation
--batchProcess 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

OptionTypeDefaultDescription
REC-XXXstringnoneTarget specific recommendation by ID
--proposebooleanfalseShow proposed changes without applying
--applybooleanfalseApply changes (requires confirmation)
--batchbooleanfalseProcess multiple recommendations
--categorystringallFilter by category (Workflow/Commands/Utilities/Skills)
--prioritystringallFilter by priority (HIGH/MEDIUM/LOW)
--limitint10Max recommendations to display
--dry-runbooleanfalseSimulate 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.md

Batch Flow

  1. Scan: Run operations/scan-recommendations.md to find pending recommendations (inline — needs file system access)
  2. Dispatch each: For each recommendation (up to --limit), dispatch a subagent with:
    • prompt: The recommendation's source text, target file paths, and operations/analyze-improvement.md + operations/propose-changes.md instructions
    • task_subject: "Analyze: REC-XXX"
    • max_retries: 1
  3. Review: Parent receives each dispatch_result and presents the proposal to the user
  4. 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 5

Output 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 recommendations
  • operations/analyze-improvement.md - Feasibility analysis
  • operations/propose-changes.md - Generate specific edits
  • operations/apply-improvement.md - Apply with confirmation

References:

  • references/recommendation-categories.md - Category to target mapping
  • references/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 sessions
  • references/improvement-workflow.md - Review cadence and decision criteria
  • improvement-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 (see improvement-loop/references/surface-repo-map.md)

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.