capture-skill

To turn a Claude Code conversation into a reusable skill, use an interview-driven capture process to clarify the workflow's triggers, inputs, process phases, and outputs, generating a structured skill specification with frontmatter.

The best way to document ad hoc workflows for automation is capturing the repeated operational steps into a structured skill specification, preserving task scope and defining fallback behavior for consistent execution.

Interview-driven workflow capture works by prompting you to clarify a task's purpose and expected output, then drafting that defined behavior into a structured skill specification with process phases and supporting files.

No specific dependencies are required to create a structured skill specification. The capture process relies solely on an interview to define behavior and generate frontmatter fields for name, description, and argument hints.

Yes, you can define fallback behavior when converting workflows into skills. The capture process drafts a structured skill specification that explicitly includes process phases and fallback behavior alongside standard outputs.