skill-extractor

To document debugging workarounds as reusable knowledge, you provide structured input detailing the problem, solution, context, and verification steps to generate a new skill file. This captures non-obvious solutions for future team reference.

Capturing project-specific patterns from a work session requires defining the problem, solution, context, and verification for the new skill. This process transforms hard-won discoveries into structured documentation for continuous learning.

Creating a new SKILL.md file from a workflow discovery involves feeding the extracted problem, context, and solution into the skill creation process. This generates a reusable skill document for workflow optimization.

Yes, structured input is required to extract knowledge into a new skill. You must define the problem, solution, context, and verification to successfully create a new reusable skill file.

Non-obvious solutions suitable for reusable code skills include project-specific patterns, complex build error workarounds, and workflow discoveries. These are transformed into structured files to facilitate team knowledge sharing.