extract-skill_skill

Overview

This skill captures learnings, patterns, and multi-step workflows discovered during a conversation and saves them as a reusable skill file. It helps turn ad-hoc solutions, gotchas, and decision rationale into concise, actionable instructions you can reuse across sessions. Use it when you want to preserve what worked or update an existing skill with new insights.

How this skill works

Scan the current conversation to identify workflows, domain facts, fixes, and patterns worth preserving. Confirm scope and destination (new or existing skill file and storage location), then distill the final working approach into a compact, generalizable skill with examples and commands. Save the resulting skill file and verify it’s clear, focused, and easy to apply later.

When to use it

• You say “extract a skill”, “save this for next time”, or similar intent.
• A workflow or pattern emerged through trial-and-error and should be preserved.
• You found non-obvious configuration, gotchas, or fixes worth documenting.
• You want to update an existing skill with new, validated steps.
• Conversation includes reusable command sequences or templates.

Best practices

• Extract the final working solution; omit irrelevant failed attempts unless the failure is instructive.
• Replace hardcoded values with placeholders and include examples showing how to fill them.
• Include the ‘why’ for non-obvious steps so future users understand trade-offs.
• Keep the skill concise and focused—aim for clear steps and short examples.
• Confirm destination (personal vs project scope) and get user approval before saving or overwriting.

Example use cases

• Turn a discovered installation sequence into a reusable installation skill with commands and environment placeholders.
• Save a debugging checklist assembled during troubleshooting (commands, logs to check, common fixes).
• Update an existing automation skill with a new, more robust command pattern found in the session.
• Capture a multi-step configuration (service, env vars, permissions) that is likely to repeat across machines.
• Convert a pattern of shell one-liners and scripts into a documented utility skill.