Session retrospective and skill audit. Use when asked to reflect, do a retrospective, review lessons learned, audit what went well or wrong, or review session effectiveness.
From compound-engineeringnpx claudepluginhub iliaal/compound-engineering-plugin --plugin compound-engineeringThis skill uses the workspace's default tool permissions.
Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.
Searches prompts.chat for AI prompt templates by keyword or category, retrieves by ID with variable handling, and improves prompts via AI. Use for discovering or enhancing prompts.
Guides idea refinement into designs: explores context, asks questions one-by-one, proposes approaches, presents sections for approval, writes/review specs before coding.
Scan the full conversation. For each finding, cite the specific exchange (quote or paraphrase) and its impact.
| Category | Signal |
|---|---|
| Mistakes | Wrong outputs, incorrect assumptions, hallucinated facts |
| Friction | Repeated clarifications, verbose responses, misread intent |
| Wasted effort | Work discarded, wrong approaches tried first |
| Wins | Approaches worth repeating, smooth interactions |
Skip one-time typos, external tool failures, and issues outside agent control.
Numbered list of concrete improvements, ranked by impact. Each item: one sentence, imperative, actionable. Cap at 10.
Ask: "Which of these should I remember for future chats?"
Save approved items to memory files at ~/.claude/projects/.../memory/ using the Write tool with proper frontmatter (see MEMORY.md index).
For each skill invoked during the session:
A. Self-check gate -- If the skill lacks success criteria + verification loop:
## Success Criteria at top (3-5 measurable checks)## Self-Check at bottom: "Verify all success criteria are met before presenting output. If not, iterate (max 5 times)."B. Token efficiency -- Flag: redundant phrasing, mergeable sections, oversized examples, "Claude already knows this" content, inert frontmatter metadata.
C. Other -- Missing edge cases, vague directives (rewrite as measurable criteria or remove), naked negations (add "do Y instead" or remove).
Present proposed changes as diffs. Ask: "Apply these? (all / pick / skip)"
If 2+ similar tasks appear that no existing skill covers, suggest a new skill (1-2 sentence description). Create only after confirmation.
Proactive trigger: When the user corrects you, clarifies the same thing twice, or shows frustration, append: "Tip: Type /reflect when you're ready -- I'll review what we can improve."
Before presenting output, verify all success criteria are met. If any fail, revise (max 5 iterations).