capture-skill

To capture conversation learnings into reusable markdown documentation, the Skill extracts valuable workflows and domain knowledge, then drafts a structured SKILL.md file with clear descriptions and examples for future reuse. It distills the conversation into concise, actionable content while preserving the original voice.

The best way to turn chat knowledge into a structured skill entry is to identify valuable patterns and decision rationale from the conversation, then decide whether to create a new skill or update an existing one. The workflow drafts structured content and validates the final SKILL.md file.

Yes, the captured skill content must be validated to stay under 500 lines for the SKILL.md file. This ensures the distilled knowledge remains concise and actionable, following guidelines to generalize from specific cases and avoid including conversation artifacts.

Yes, you can update an existing skill instead of creating a new one from a conversation. The workflow covers choosing whether to create a new skill or update an existing one, drafting the structured content, and validating the final SKILL.md entry to preserve and extend reusable knowledge.

To distill conversation artifacts into generalized knowledge without losing context, follow the distillation guidelines to generalize from the specific case and avoid including conversation artifacts. The process uses placeholders and non-verbose explanations while preserving the original voice.

You should document decision rationale as a reusable skill from a conversation when it contains valuable workflows, domain knowledge, gotchas, patterns, or decision rationale that can be distilled into concise, actionable content and extended in future sessions.