config
Adjust Skill Autopilot settings — mute it, change aggressiveness (teaching/normal/quiet), switch guidance language (en/zh), or toggle the auto plan-mode gate.…
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
$ npx -y skills add WinterDDo/claude-code-skill-autopilot --skill profile --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/profileContext preview
The summary Claude sees to decide when to auto-load this skill.
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
name: profile description: 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 give feedback about suggestions.
Every number MUST be traceable to a real entry in the data files. Never fabricate or extrapolate a value claim. If a number is zero, show zero.
Read from `~/.claude/command-autopilot/`: `state.json` (counters, milestones, config), `events.jsonl` + `events-archive.jsonl` (the ledger), `learned.json` (rules), `skills-index.json`.
1. **Value ledger** — counts from events: auto plan-mode entries, skills auto-invoked (top 3 by count, with names), suggestions accepted vs made. One line each, with the period covered. 2. **Before/after** — compare the oldest 7 days of events against the newest 7 (only if ≥14 days of data; otherwise say "still collecting"): self-used commands per week then vs now. This is the user's own growth, shown from their own data. 3. **Learned rules** — each in_force rule with its evidence count and last-confirmed date. If none: "still observing, first rules typically appear after ~10 sessions." 4. **Mastered** — habits with self-use evidence; note that teaching for them has naturally stopped. 5. **Controls** — one line: config skill to quiet/mute, evolve skill to re-distill, "delete rule N" works right here.
If the user is dissatisfied with any suggestion behavior, offer to draft a GitHub issue for `WinterDDo/claude-code-skill-autopilot`: title, what happened, expected behavior, and (only with explicit consent) the relevant anonymized evidence lines. Show the draft; the user files it themselves.
"Delete rule N" → remove it from learned.json, confirm in one line.
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 toggle the auto plan-mode gate.…
Diagnose whether Skill Autopilot's hooks are actually firing and config is valid. Use when the autopilot seems inactive, suggestions never appear, after…
Distill Skill Autopilot's accumulated usage evidence into personalized rules — the self-evolution step. Use when the autopilot announces an evolution window,…
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…
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…