config
Adjust Skill Autopilot settings — mute it, change aggressiveness (teaching/normal/quiet), switch guidance language (en/zh), or…
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".
Claude Code
$ npx -y skills add WinterDDo/claude-code-skill-autopilot --skill evolve --agent claude-code
Codex
$ npx skills add WinterDDo/claude-code-skill-autopilot --skill evolve -a codex -y
Cursor
$ npx skills add WinterDDo/claude-code-skill-autopilot --skill evolve -a cursor -y
Gemini CLI
$ npx skills add WinterDDo/claude-code-skill-autopilot --skill evolve -a gemini-cli -y
GitHub Copilot
$ npx skills add WinterDDo/claude-code-skill-autopilot --skill evolve -a github-copilot -y
OpenCode
$ npx skills add WinterDDo/claude-code-skill-autopilot --skill evolve -a opencode -y
Windsurf
$ npx skills add WinterDDo/claude-code-skill-autopilot --skill evolve -a windsurf -y
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".
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.
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:
3. Apply the discipline:
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.
Adjust Skill Autopilot settings — mute it, change aggressiveness (teaching/normal/quiet), switch guidance language (en/zh), or…
Diagnose whether Skill Autopilot's hooks are actually firing and config is valid. Use when the autopilot seems inactive,…
Show the Skill Autopilot dashboard — what it did for you, before/after comparison, learned rules with evidence, mastered…
Guided first tour of Skill Autopilot — see auto plan mode happen, learn the 4 habit commands (/clear, /btw, /rewind, plan mode),…
Explain what's newly possible — new Claude Code commands after a knowledge-base update, and installed-but-never-used skills. Use…
Shape output for a reader with ADHD: lead with the next action, number multi-step work, restate state across turns, suppress…
Set up the owner profile so a personal agent knows who it works for (first-run setup, \"get to know me\"), or distill colleague,…