self-improve
Skill9 starsChanged 7 months agoMITView on GitHub
Run the full self-improvement cycle: scan external sources (GitHub, Reddit, Twitter), classify discoveries, check against registry, capture session learnings, and propose new patterns. Use when starting a session, after completing work, or when you want to pull in external best practices.
39 other projects use a version of this.
Adopted by
Most recently taken up by
- savannahfeder/agentboxtheir own version, first seen Nov 15, 2026
- Hrutin-Suriya-Kotni/until-hiredtheir own version, first seen Nov 15, 2026
- 5uck1ess/devkittheir own version, first seen Nov 15, 2026
- Yeachan-Heo/oh-my-claudecodetheir own version, first seen Nov 9, 2026
- naman10parikh/pennytheir own version, first seen Nov 8, 2026
- DYNO-SOFT/self-improving-looptheir own version, first seen Nov 8, 2026
Used with
Projects with it also use ecosystem-reference, fractal-delegation and 10 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.
naman10parikhSkillecosystem-reference
Quick-access directory of Claude Code ecosystem repos, skills, plugins, MCPs, and patterns. Use when improving the harness.
Also in 5 projects that use this
naman10parikhSkillfractal-delegation
Also in 5 projects that use this
aaronjmarsSkillaeon-update
Pull framework updates from the upstream Aeon repo into this instance - 3-way merges canon's new commits into a PR, never clobbering operator config.
Also in 4 projects that use this
aaronjmarsSkillauto-workflow
Two-mode aeon.yml workflow builder - analyze inspects URLs and emits a tiered, signal-verified skill-enablement plan plus an aeon.yml diff; enable flips slugs to enabled:true and opens a PR.
Also in 4 projects that use this
- +6 more from naman10parikh
- +2 more from aaronjmars
Other versions39 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 39
- Yeachan-Heo/oh-my-claudecode★ 41ksame name
- Yeachan-Heo/oh-my-claude-sisyphus★ 41ksame name
- zereight/gitlab-mcp★ 2.1ksame name
- aaronjmars/aeon★ 794same name
- aeonfun/aeon★ 793same name
- savannahfeder/agentbox★ 419same name
- forefy/.context★ 154same name
- eai-org/agent-toolkit★ 94same name
- nitinjain999/platform-skills★ 71same name
- aaronjmars/miroshark-aeon★ 20same name
29 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 repository44 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- anthropic-multi-agent-research-system-skillSkill
- apply-selectionsSkill
- bootstrap-dogfood-projectSkill
- brainstormSkill
- branch-choiceSkill
- cc-adoption-scoutSkill
- claude-guardianSkill
- continueSkill
- end-sessionSkill
- executing-plansSkill
- five-advisorsSkill
- get-work-doneSkill
- git-branch-lifecycleSkill
- githubSkill
- grill-meSkill
- hook-transcript-fixture-testSkill
- instagramSkill
- linkedinSkill
- modern-data-pipeline-diagramSkill
- pattern-qualitySkill
- platform-event-live-probeSkill
- plugin-lifecycleSkill
- promote-to-coreSkill
- prompt-auto-enhanceSkill
- provision-reportSkill
- redditSkill
- review-new-claude-featuresSkill
- save-sessionSkill
- scan-discovery-reportSkill
- scan-repoSkill
- scan-urlSkill
- skill-evaluatorSkill
- skill-masterSkill
- ssot-workflow-auditSkill
- start-sessionSkill
- synthesize-hubSkill
- synthesize-projectSkill
- twitter-xSkill
- verify-effect-at-destinationSkill
- workflow-doc-reviewerSkill
- writing-plansSkill
- writing-skillsSkill
- youtube-transcriptSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
18 rules. 0 are common, 10 are distinctive, and 8 are very specific to this project.
0
Common
Most of the 33 edited versions we read keep these.
10
Distinctive
This author's own choices. Worth a look.
8
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 34
Read $ARGUMENTS and determine mode:
- Very specific: line 39
No flag or --review → run Step 4 only
- Distinctive: line 45
Search for Claude Code patterns from external sources.
- Very specific: line 49
Use the /github skill to search for patterns:
- Very specific: line 60
Use the /reddit skill to search r/ClaudeAI for recent tips:
- Distinctive: line 101
Read the post-failure capture log for this session:
- Distinctive: line 108
If failures exist, feed them into the learning database as error-fix-lesson triples (even if the fix hasn't been found yet — the error …
- Very specific: line 113
If test-related learnings were captured, also feed them into /test-knowledge:
- Very specific: line 121
Read the most recent session file from .claude/sessions/:
- Distinctive: line 127
If a session file exists, extract learning signals:
- Distinctive: line 182
If auto-queue candidates exist (>=85 confidence, high trust), present them to the user with a recommendation to import.
- Very specific: line 196
Check .claude/learnings.json for pattern detection triggers:
- Very specific: line 203
Check config/urls.yml for degraded or expired sources:
- Distinctive: line 233
MUST NOT auto-import patterns without user approval — auto-queue only PRESENTS candidates
- Distinctive: line 234
MUST NOT degrade source trust without evidence (test failure, user correction, or pattern rejection)
- Distinctive: line 235
MUST run discovery adapter dedup before registering any finding — never create duplicate entries
- Distinctive: line 236
MUST cite the source for every discovery: "found in github:owner/repo" or "seen on reddit:r/ClaudeAI"
- Distinctive: line 238
Default mode is review (read-only) — scanning and learning require explicit flags
“Common” is measured: kept by at least 6 in 10 of the 33 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-Improve — Autonomous Learning & Discovery Pipeline
Single entry point for the hub's self-improvement system. Combines external discovery, session learning, and pattern proposal into one workflow.
Arguments: $ARGUMENTS
Modes
| Mode | Flag | What It Does |
| Review | (default) | Show pending discoveries, session stats, and improvement suggestions |
| Scan | --scan | Search external sources (GitHub, Reddit, Twitter) for new patterns |
| Learn | --learn | Capture learnings from current session + check failure logs |
| Full | --full | Run scan + learn + review in sequence |
STEP 1: Parse Mode
Read $ARGUMENTS and determine mode:
--full→ run Steps 2, 3, 4, 5 in sequence--scan→ run Step 2 only--learn→ run Step 3 only- No flag or
--review→ run Step 4 only
STEP 2: External Discovery Scan
Search for Claude Code patterns from external sources.
2A: GitHub Search
Use the /github skill to search for patterns:
Skill("github", args="search code SKILL.md path:.claude/skills language:markdown stars:>10")For each result, extract name, type, content preview, and whether it has proper frontmatter.
2B: Reddit Scan
Use the /reddit skill to search r/ClaudeAI for recent tips:
Skill("reddit", args="search r/ClaudeAI claude code tips sort:new limit:10")Extract actionable patterns from high-engagement posts (upvotes > 10).
2C: Register Discoveries
For each finding, register via the discovery adapter:
PYTHONPATH=. python scripts/discovery_adapter.py --add '{
"name": "<pattern-name>",
"type": "<skill|agent|rule|hook>",
"source": "<github:owner/repo|reddit:r/subreddit|twitter:@handle>",
"source_trust": "<high|medium|low>",
"content": "<first 200 chars>",
"has_frontmatter": true,
"has_steps": false,
"community_signal": 15
}'Report: how many new discoveries, how many duplicates, how many already in registry.
STEP 3: Session Learning Capture
3A: Run Learn-n-Improve
Invoke the learning skill to capture session outcomes:
Skill("learn-n-improve", args="session")3B: Check Failure Logs
Read the post-failure capture log for this session:
SESSION_ID=${CLAUDE_SESSION_ID:-default}
cat "${TMPDIR:-/tmp}/claude-failure-log/session-$SESSION_ID.jsonl" 2>/dev/nullIf failures exist, feed them into the learning database as error-fix-lesson triples (even if the fix hasn't been found yet — the error context is valuable).
3C: Wire Test Knowledge
If test-related learnings were captured, also feed them into /test-knowledge:
Skill("test-knowledge", args="add <learning-summary>")3D: Analyze Session Checkpoints
Read the most recent session file from .claude/sessions/:
ls -t .claude/sessions/*.md 2>/dev/null | head -1If a session file exists, extract learning signals:
- Blocked tasks — scan for tasks marked
blockedorin-progressthat were never completed. Each blocked task is a potential skill gap or missing capability. Record as a learning with tagsession-blocked. - Decision themes — scan the "Key Decisions" section for recurring
patterns. If the same type of decision appears across multiple session
files (e.g., "chose X over Y for testing"), it may warrant a rule.
Compare against the 3 most recent session files if available:
ls -t .claude/sessions/*.md 2>/dev/null | head -3 - File hotspots — extract the "Working Files" section and count which files appear most frequently across recent sessions. Files modified in 3+ sessions are change hotspots — flag for potential refactoring or dedicated rule creation.
- Session duration signal — if a session has many completed tasks but also many blocked tasks, the session was productive but hit walls. Record the blocked-to-completed ratio as a learning metric.
Feed findings into the learning database:
PYTHONPATH=. python scripts/discovery_adapter.py --add '{
"name": "session-pattern:<pattern-name>",
"type": "rule",
"source": "session:.claude/sessions/<filename>",
"source_trust": "high",
"content": "<finding summary>",
"has_frontmatter": false,
"community_signal": 0
}'Session-derived discoveries get high trust — they come from direct
observation of real work, not external sources.
STEP 4: Review Pending Improvements
4A: Discovery Pipeline Status
PYTHONPATH=. python scripts/discovery_adapter.py --stats4B: Auto-Queue Candidates
PYTHONPATH=. python scripts/discovery_adapter.py --auto-queueIf auto-queue candidates exist (>=85 confidence, high trust), present them to the user with a recommendation to import.
4C: Convergent Evolution
PYTHONPATH=. python scripts/discovery_adapter.py --convergentPatterns found in 3+ independent sources are strong candidates for hub promotion. Highlight these prominently.
4D: Learning Pattern Alerts
Check .claude/learnings.json for pattern detection triggers:
- Tags appearing in >30% of learnings → systemic issue
- Files with 3+ learnings → fragile code hotspot
- Workflow patterns seen 3+ times → skill promotion candidate
4E: Source Health Check
Check config/urls.yml for degraded or expired sources:
PYTHONPATH=. python scripts/check_freshness.pyReport any expired or degraded sources that need attention.
STEP 5: Propose Improvements
Based on findings from Steps 2-4, propose concrete actions:
| Finding | Proposed Action |
| Auto-queue candidate (>=85, high trust) | "Import pattern X — run /skill-factory create <name>" |
| Convergent pattern (3+ sources) | "Promote to hub — pattern X found in N independent sources" |
| Systemic learning tag (>30%) | "Create rule for <tag> — run /claude-guardian" |
| Workflow pattern (3+ repeats) | "Create skill — run /writing-skills" |
| Degraded source | "Review source <url> — trust downgraded due to <reason>" |
| Expired source | "Re-verify or remove <url> — expired <N> days ago" |
Present findings as a prioritized list. Each proposal requires user approval before execution.
CRITICAL RULES
- MUST NOT auto-import patterns without user approval — auto-queue only PRESENTS candidates
- MUST NOT degrade source trust without evidence (test failure, user correction, or pattern rejection)
- MUST run discovery adapter dedup before registering any finding — never create duplicate entries
- MUST cite the source for every discovery: "found in github:owner/repo" or "seen on reddit:r/ClaudeAI"
- Session learning capture (Step 3) MUST run even if external scan is skipped
- Default mode is review (read-only) — scanning and learning require explicit flags
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.

