Skip to content
Productivity
Skill

/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".

From plugin
claude-code-skill-autopilot
66 skills

Claude Code

$ npx -y skills add WinterDDo/claude-code-skill-autopilot --skill evolve --agent claude-code

SKILL.md

evolve.SKILL.md
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.

Read more
@winterddo
Ships withclaude-code-skill-autopilot

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.

Stars on GitHub

Momentum

stars in total
6
Star history of WinterDDo/claude-code-skill-autopilot on GitHub, a chart by star-history.com

More skills from other plugins.

i-have-adhd

i-have-adhd

Shape output for a reader with ADHD: lead with the next action, number multi-step work, restate state across turns, suppress…

@ayghri@ayghriInstall Skill
ab-test-analysis

ab-test-analysis

Analyze A/B test results with statistical significance, sample size validation, confidence intervals, and ship/extend/stop…

@phuryn@phurynInstall Skill
distilly

distilly

Set up the owner profile so a personal agent knows who it works for (first-run setup, \"get to know me\"), or distill colleague,…

Questions about evolve.

Which coding agents can use evolve?
evolve installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.