plugins/toolkit-skills/skills/reflect/SKILL.md
Analyze session history for learnings and persist to skills. Solves "memory zero" - correct once, never again.
npx skillsauth add spences10/claude-code-toolkit reflectInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Extract learnings from sessions and persist to skill files.
Run /reflect after sessions with:
/reflect # Analyze current session, suggest skill updates
/reflect skill-name # Target specific skill for updates
Note: This is manual-only. Run before ending sessions with learnings.
Auto-detection via Stop hooks doesn't work reliably:
| Issue | Problem | | ------ | ---------------------------------------------- | | #16227 | Stop hook output is silent (not shown to user) | | #10412 | Plugin Stop hooks fail with exit code 2 | | #10875 | Plugin JSON output not captured | | #3656 | Blocking functionality partially removed |
Stop hooks fire but can't communicate back - making them useless for reminders. Other self-improving skill implementations (autoskill, reflect-skill) also use manual triggering for this reason.
Try sources in order, use first available:
If user has ccrecall + mcp-sqlite-tools:
SELECT timestamp, role, content FROM messages
WHERE session_id = (SELECT MAX(session_id) FROM sessions)
ORDER BY timestamp DESC LIMIT 100;
Fallback when ccrecall unavailable:
Note which mode is active:
[reflect] Using: ccrecall.db (full history)
-- or --
[reflect] Using: in-context (current session only)
.claude-plugin/ → update skill in-place.claude/skills/ or global ~/.claude/skills/development
Design and create Claude Skills using progressive disclosure principles. Use when building new skills, planning skill architecture, or writing skill content.
testing
Verify sources before presenting findings. Use when asked to research links or documentation.
tools
Validate, test, and distribute Claude Code plugins and marketplaces. Use when developing plugins, debugging validation errors, or preparing for distribution.
tools
Guide to spences10's Claude Code ecosystem tools. Use when user asks which tool to use, how tools relate, or needs help choosing between MCP servers, skills, or CLIs.