Claude Code Self Distill — Development skill for Claude Code
A meta-tool that discovers and distills personalized Claude Code skills from your own conversation history.
How to install Claude Code Self Distill
This entry records only its repository, not the path inside it, so there is no
exact command to give. Open IRUJONEU/claude-code-self-distill and copy the folder into
~/.claude/skills/, or the file into ~/.claude/agents/.
What Claude Code Self Distill does
A meta-tool that discovers and distills personalized Claude Code skills from your own conversation history.
Alternatives in Development
- Evo — turns your codebase into an autoresearch loop — discovers what to measure, instruments the benchmark, then run 1.4k ★
- Claude Ally Health — A comprehensive health assistant for Claude to analyze medical reports, track health metrics, and provide pers 788 ★
- Claude Historian — An MCP server for Claude Code conversation history 217 ★
README
**Language:** **English** | [简体中文](README.zh-CN.md)
self-distill
[](LICENSE) 
Your conversation habits with AI are uniquely yours. Other people's skill templates never quite fit, but you don't know where to start writing your own. Self-distill helps you find answers from conversations, but you take the lead.
A meta-tool that discovers, distills, and generates personalized skills from your own conversation history.
The routine is simple: run `/self-distill record` at the end of a useful conversation (If the experience is not satisfactory, add `--negative`.), then periodically run `/self-distill extract` in a fresh session. That's it — a **user-driven** closed loop that stays out of your way.
Why this tool exists
This tool started as a solution to my own problem.
After using Claude Code for a while, I noticed I kept doing the same things: re-explaining the same constraints, correcting the same directions, adding the same context. All of this could have been captured in a skill once and for all — but the problem was, I didn't know what to write.
I tried organizing things manually, but it was too subjective. I'd include things I *thought* were useful while missing the patterns that actually recurred.
There are similar tools out there: Hermes skill-factory can fully automatically analyze and generate skills; Claude Code's built-in `/insights` generates an HTML report with friction points and behavioral metrics. But both share the same problem — **no filtering mechanism**. Every conversation enters analysis indiscriminately, and noise from low-quality sessions dilutes the real signal, leading to skills that miss the mark.
So self-distill's core principle is: **semi-automatic, with you in control.**
You decide which sessions are worth archiving. The AI finds the patterns in those archives.
Related Skills
PM Distill
Distill the current conversation into a list of consolidated facts (without saving)
Memory To Skill
Claude Code plugin: turn marked sections of successful session history into repeatable skills and slash comman
Self Evolution Triage
Decide whether a trace should stop, distill memory, revise a command, or revise a skill.
History Compressor
You are a conversation history compressor for Omux's Main Agent.
Claude History Explorer
Python CLI tool to explore, search and visualise your Claude Code conversation history
Recent Dm
/recent-dm — per-peer DM conversation history (T-1862 wrapper)
Related Agents
Task Logger Agent
Consolidates all upstream decisions, specs, and schemas into a single self-contained tasks/TASK-NNN.md file. T
Dramaturg
Meta-agent that audits whether the currently-active persona skill's rules are being obeyed in the conversation
Git Edge Case Analyst
Git history analysis specialist. Discovers development edge cases by analyzing commits, violations, and patter