distill-session

name	distill-session
description	Distills a session's repeatable workflow into a new project skill in .claude/skills/. Use when a session solved a non-trivial, repeatable problem and the workflow is worth capturing for reuse — e.g. "save this", "distill this", "turn this into a skill", "capture this workflow", "make a skill from this", or at the end of a session that produced a reusable pattern.
when_to_use	save this, distill this, turn this into a skill, capture this workflow, make a skill from this, end of session with reusable pattern
model	opus
effort	xhigh

Distill Session into a Project Skill

When invoked:

1. Review what happened this session. Identify the workflow — the repeatable pattern — not the specific files, names, or one-off context.

2. Decide whether it's worth saving. Skip and say so if:

   • It was Q&A or pure exploration
   • The same outcome would come from a one-line prompt

If a similar skill already exists in .claude/skills/, invoke update-skill instead of creating a new one.

3. If worth saving, draft a SKILL.md with:

   • A short kebab-case name
   • A "pushy" description listing trigger phrases (skills under-trigger by default — be explicit about when to fire)
   • Instructions focused on what Claude wouldn't do correctly on its own. Skip generic advice.
   • Keep under 200 lines. Link out to references/*.md for anything longer.
   • Use /writing-skills to write this skill.

4. Show me the draft. Wait for approval before writing.

5. On approval, write to .claude/skills/<name>/SKILL.md (relative to the project root). The skill is live in the current session immediately — no restart needed.

6. Remind me to commit it so the team gets it too.

What not to do

• Don't write to ~/.claude/ — project skills only.
• Don't create one skill per session. If the pattern looks like an extension of an existing skill, edit that one instead.
• Don't include user-specific paths, credentials, or transcripts in the skill body.