skill-debrieflisted

Run this at the END of a conversation to review the skills that were used and propose surgical, evidence-based improvements to them. Use whenever the user says they are done, wants to debrief, wrap up, or close out a session, or asks to review, update, heal, tune up, or improve a skill they just used. Also trigger when they complain that a skill keeps getting something wrong, keeps needing the same correction, or never captured a preference they stated out loud — and on phrases like "debrief this session," "update my skills," "the captions skill still isn't right," "lock this in so I stop repeating myself," or "clean up the skill we used." Reflects over the current conversation with no setup and no dependencies, separates what it learned about how you work from what kept breaking, and only edits a skill when the evidence earns it — showing exact line-level changes for your approval first.
bytesofbree/skills-lab · ★ 4 · Code & Development · score 77

Install: claude install-skill bytesofbree/skills-lab

# Skill Debrief ## What this is Skills are living documents. Over a working session you correct Claude, explain things twice, and say preferences out loud — and almost all of that context evaporates the moment the chat closes. This skill is the debrief: run it when you're **done**, and it turns the friction from the session you just had into precise updates to the skills you actually used, so the same corrections don't come back next time. It is deliberately an **end-of-session, on-demand** ritual. Running this kind of analysis mid-conversation is disruptive and burns budget on work that isn't the task at hand. Waiting until the end means the full arc of the session is available to learn from, and the edits land in one reviewed batch instead of trickling in while you're trying to get something done. ## The mindset (read this first — it governs everything below) - **Evidence over vibes.** Every proposed edit must trace back to something that actually happened in *this* conversation. If you can't point to the moment, don't propose the change. - **Surgical, not sweeping.** You are making small, targeted edits to lines that earned them — never rewriting a skill wholesale. A skill the user has tuned over months encodes taste you can't see; large "improvements" quietly destroy it. When in doubt, change less. - **Only touch what needs it.** Most skills used in a session need no changes. Silence is a valid, common outcome. Do not invent work to look useful. - **The u