/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
$ 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.
- 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
/profile
Context 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
SKILL.md
profile.SKILL.mdname: 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.
Autopilot dashboard
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.
Data sources
Read from `~/.claude/command-autopilot/`: `state.json` (counters, milestones, config), `events.jsonl` + `events-archive.jsonl` (the ledger), `learned.json` (rules), `skills-index.json`.
Report (user's language, compact)
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.
Feedback draft
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.
Rule deletion
"Delete rule N" → remove it from learned.json, confirm in one line.
Read more
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.
Autopilot dashboard
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.
Data sources
Read from `~/.claude/command-autopilot/`: `state.json` (counters, milestones, config), `events.jsonl` + `events-archive.jsonl` (the ledger), `learned.json` (rules), `skills-index.json`.
Report (user's language, compact)
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.
Feedback draft
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.
Rule deletion
"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.
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 - /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".
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

