hjewkes/agent-skills

self-improve

Use when a session produced reusable insights, when the user says "learn from this", "remember this", or "improve yourself", or after completing a complex task where patterns were discovered

First seen Feb 17, 2026

Installation

$ npx skills add hjewkes/agent-skills --skill self-improve

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from hjewkes/agent-skills · top by installs.

npx skills add hjewkes/agent-skills

Browse all from hjewkes/agent-skills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 3
License LICENSE
Default branch main
Open issues 0
Status Active

Skill metadata

Parsed from SKILL.md frontmatter.

Declared agents claude-code

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,939 B
  • docs SUMMARY.md 210 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 164 installs

SKILL.md

Self-Improve

Overview

Session learning loop that captures reusable knowledge and routes it to the right place: project memory, global CLAUDE.md, or a new skill. Builds on skills-management methodology for skill creation (see writing-skills reference).

Process

1. Identify Learnings

After a productive session, review what was learned:

  • Patterns that worked well
  • Mistakes that were caught and corrected
  • Techniques that could be reused
  • Debugging insights
  • Tool usage patterns
  • Project-specific conventions discovered

2. Classify Each Learning

Read [references/classification-routing.md](references/classification-routing.md) for the full routing table (priority 1-5) and draft format per destination. Key rule: the instinct to put things in ~/CLAUDE.md is usually wrong — route to existing skills or project CLAUDE.md first.

3. Confirm with User

Present all proposed changes grouped by destination. For each:

  • What was learned (1 sentence)
  • Where it goes and why
  • Exact content to add/modify

Never auto-apply changes. Always get explicit approval.

4. Apply Approved Changes

Write changes to the approved destinations. For new skills, note that full TDD testing (per skills-management writing-skills reference) should happen in a dedicated session.

Common Mistakes

  • Defaulting to ~/CLAUDE.md — most learnings belong in a more focused location (existing skill, project CLAUDE.md, or memory). ~/CLAUDE.md is the last resort, not the default.
  • Auto-applying changes without user confirmation
  • Saving session-specific context as permanent knowledge
  • Creating skills for one-off solutions
  • Duplicating what's already in CLAUDE.md or existing skills