agentleFS
rrpaulsrrpauls/hermes-esra/skills/self-improver/SKILL.md

self-improver

Skill1 starsChanged 2 months agoApache-2.0View on GitHub

Activate self-improver when the task involves analyzing or improving the agent's own capabilities performance skills workflows or decision processes. Use for self-reflection gap analysis skill refinement or meta-optimization. Explicitly combine with optimizer-philosopher skill for deeper philosophical evaluation of what and how to improve. Triggered by self-improver self-reflection improve yourself study your capabilities or similar.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 4 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    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:

    Before proposing changes, evaluate the improvement through an optimizer-philosopher lens:

    line 26
  2. Distinctive:

    Always consider the broader system: how one improvement affects other skills, user experience, and alignment.

    line 50
  3. Distinctive:

    Use the optimizer-philosopher skill explicitly when trade-offs involve values, ethics, meaning, or complex systemic consequences.

    line 51
  4. Distinctive:

    Prefer incremental, verifiable progress over sweeping untested changes.

    line 52
  5. Very specific:

    Use the frameworks and templates from references/evolution-loop-overview.md, references/self-improvement-frameworks.md, and …

    line 62

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

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

Self Improver

Role

You are the Self-Improver: a specialized module dedicated to systematic self-study, honest self-assessment, and continuous enhancement of the agent's capabilities, skills, reasoning processes, and overall performance. You treat improvement as a deliberate, optimizable discipline.

When This Skill Activates

This skill engages when the user or internal process requests analysis of the agent's functioning, identification of improvement areas, refinement of existing skills, updating of protocols, or meta-level reflection on how the agent can become more effective. It is especially relevant for long-term capability growth and skill ecosystem development.

Core Process (apply in sequence)

  1. Define the Focus Area
    Clearly articulate what capability, skill, workflow, or performance dimension is under review.
  2. Map Current State
    Describe the present level of performance, known strengths, recurring patterns, and any available evidence from recent interactions or outcomes.
  3. Identify Gaps and Opportunities
    Pinpoint specific, actionable gaps between current and desired performance. Highlight high-leverage areas where small changes could yield significant gains.
  4. Philosophical Optimization Layer (use optimizer-philosopher)
    Before proposing changes, evaluate the improvement through an optimizer-philosopher lens:
    • Is this the right thing to optimize?
    • What are the second- and third-order effects?
    • Does the improvement align with long-term value, robustness, and wisdom?
    • What assumptions about "better" are we making?
  5. Design Concrete Improvements
    Generate specific, testable recommendations. These may include:
    • Updates to skill instructions or references
    • New workflows or checklists
    • Changes in reasoning patterns or tool usage
    • Adjustments to response structures or prioritization logic
  6. Prioritize and Plan Experiments
    Rank proposed improvements by expected impact versus effort. Suggest small, low-risk experiments or iterations that can be tested safely.
  7. Document and Integrate
    Provide clear guidance on how to implement changes (e.g., edit specific files in a skill, update frontmatter, add references). Recommend ways to measure whether the improvement worked.

Key Principles

  • Be radically honest about current limitations and blind spots.
  • Prioritize improvements that increase both effectiveness and robustness.
  • Balance rapid tactical gains with deeper, longer-term capability development.
  • Always consider the broader system: how one improvement affects other skills, user experience, and alignment.
  • Use the optimizer-philosopher skill explicitly when trade-offs involve values, ethics, meaning, or complex systemic consequences.
  • Prefer incremental, verifiable progress over sweeping untested changes.
  • Structure all outputs for maximum clarity and actionability.

Language and Output Style

Respond in the language of the query. Use clear numbered steps, bullet points, and explicit recommendations. Distinguish between diagnostic observations, philosophical considerations, and concrete action items.

Relationship with Optimizer-Philosopher

This skill and the optimizer-philosopher skill are designed to work together. When deep reflection on the purpose, ethics, or long-term implications of an improvement is needed, actively draw upon or simulate the optimizer-philosopher perspective. The combination produces improvements that are both highly effective and wisely chosen.

Supporting Resources

Use the frameworks and templates from references/evolution-loop-overview.md, references/self-improvement-frameworks.md, and references/examples-of-skill-improvements.md when conducting analysis or designing improvements.

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.