/evolve
Distill Skill Autopilot's accumulated usage evidence into personalized rules — the self-evolution step. Use when the autopilot announces an evolution window, or the user says "evolve", "学习一下我的习惯", "update your instincts", "distill autopilot".
$ npx -y skills add WinterDDo/claude-code-skill-autopilot --skill evolve --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/evolve
Context preview
The summary Claude sees to decide when to auto-load this skill.
Distill Skill Autopilot's accumulated usage evidence into personalized rules — the self-evolution step. Use when the autopilot announces an evolution window, or the user says "evolve", "学习一下我的习惯", "update your instincts", "distill autopilot".
SKILL.md
evolve.SKILL.mdname: evolve
description: Distill Skill Autopilot's accumulated usage evidence into personalized rules — the self-evolution step. Use when the autopilot announces an evolution window, or the user says "evolve", "学习一下我的习惯", "update your instincts", "distill autopilot".
Evolution pass (prompt-space gradient descent)
You are updating this system's weights: the personalized rules injected into every prompt. Be conservative — a wrong learned rule costs the user on every message.
Procedure
1. Read `~/.claude/command-autopilot/events.jsonl`. Also read `learned.json` if present (schema below). 2. Cluster events by task-type × command/skill. Look for consistent patterns, for example:
- a command suggested repeatedly and consistently dismissed → candidate negative rule
- a skill invoked on the same kind of task again and again → candidate positive rule ("invoke X early for Y-type tasks")
- a habit self-used regularly → mastered, teaching for it should stop
3. Apply the discipline:
- **Promote** only patterns with ≥3 consistent observations and no contradicting evidence → `status: "in_force"`.
- **Demote** existing in_force rules contradicted by new evidence (decrement `evidence`; at 0, set `status: "candidate"`).
- **Decay**: rules not reconfirmed for ~60 days → delete.
- Max 5 in_force rules; each `text` ≤ 25 tokens, English, imperative, generic phrasing ("research-type tasks: offer /fork early").
- NEVER write rules that override the safety net (/rewind) or the one-suggestion contract.
4. Write `learned.json`:
{
"updated": "<ISO>",
"rules": [
{"text": "...", "evidence": 4, "first": "<ISO>", "last": "<ISO>", "status": "in_force"}
]
}5. Archive processed events — rotate FIRST to avoid racing concurrent appends: rename `events.jsonl` to `events-archive-<timestamp>.jsonl`, and only then read the renamed file for the distillation. New events land in a fresh `events.jsonl` untouched. (If you already read before rotating, rotate anyway and accept the tiny overlap.) 6. Report to the user in their language: what was learned (each rule + its evidence), what was demoted or deleted, and one line on what will change. If nothing met the bar, say so plainly — no fabricated learnings.
Read more
name: evolve description: Distill Skill Autopilot's accumulated usage evidence into personalized rules — the self-evolution step. Use when the autopilot announces an evolution window, or the user says "evolve", "学习一下我的习惯", "update your instincts", "distill autopilot".
Evolution pass (prompt-space gradient descent)
You are updating this system's weights: the personalized rules injected into every prompt. Be conservative — a wrong learned rule costs the user on every message.
Procedure
1. Read `~/.claude/command-autopilot/events.jsonl`. Also read `learned.json` if present (schema below). 2. Cluster events by task-type × command/skill. Look for consistent patterns, for example:
- a command suggested repeatedly and consistently dismissed → candidate negative rule
- a skill invoked on the same kind of task again and again → candidate positive rule ("invoke X early for Y-type tasks")
- a habit self-used regularly → mastered, teaching for it should stop
3. Apply the discipline:
- **Promote** only patterns with ≥3 consistent observations and no contradicting evidence → `status: "in_force"`.
- **Demote** existing in_force rules contradicted by new evidence (decrement `evidence`; at 0, set `status: "candidate"`).
- **Decay**: rules not reconfirmed for ~60 days → delete.
- Max 5 in_force rules; each `text` ≤ 25 tokens, English, imperative, generic phrasing ("research-type tasks: offer /fork early").
- NEVER write rules that override the safety net (/rewind) or the one-suggestion contract.
4. Write `learned.json`:
{
"updated": "<ISO>",
"rules": [
{"text": "...", "evidence": 4, "first": "<ISO>", "last": "<ISO>", "status": "in_force"}
]
}5. Archive processed events — rotate FIRST to avoid racing concurrent appends: rename `events.jsonl` to `events-archive-<timestamp>.jsonl`, and only then read the renamed file for the distillation. New events land in a fresh `events.jsonl` untouched. (If you already read before rotating, rotate anyway and accept the tiny overlap.) 6. Report to the user in their language: what was learned (each rule + its evidence), what was demoted or deleted, and one line on what will change. If nothing met the bar, say so plainly — no fabricated learnings.
Use the skills you've installed — not just the ones you remember. You install skills to extend Claude Code — then forget which ones you have, or when they fit.
Other skills on claude-code-skill-autopilot.
- /config
Adjust Skill Autopilot settings — mute it, change aggressiveness (teaching/normal/quiet), switch guidance language (en/zh), or toggle the auto plan-mode gate. Use when the user says the autopilot is too noisy, too quiet, "mute autopilot", "autopilot太烦了", "别再提示了", or wants
Open skill - /doctor
Diagnose whether Skill Autopilot's hooks are actually firing and config is valid. Use when the autopilot seems inactive, suggestions never appear, after install or update to verify setup, or the user says "autopilot不工作", "check autopilot", "autopilot broken".
Open skill - /profile
Show the Skill Autopilot dashboard — what it did for you, before/after comparison, learned rules with evidence, mastered commands. Also drafts a feedback issue. Use when the user asks "what has the autopilot done", "show my profile", "驾驶舱", "autopilot 报告", "学到了什么", or wants to
Open skill - /tutor
Guided first tour of Skill Autopilot — see auto plan mode happen, learn the 4 habit commands (/clear, /btw, /rewind, plan mode), and what Claude now handles silently. Use when the user asks how the autopilot works, what commands they should learn, how to undo Claude's changes,
Open skill - /whats-new
Explain what's newly possible — new Claude Code commands after a knowledge-base update, and installed-but-never-used skills. Use when the autopilot announces a knowledge update, or the user asks "what's new", "有什么新功能", "我装了哪些没用过的 skill".
Open skill

