self-evolve

To convert an improvised workflow into a reusable skill, the system detects successful multi-step outcomes and saves them as a SKILL.md file under workspace/skills, including optional directories for scripts and assets.

The best way to save repeating task patterns is to generalize the successful approach into a reusable skill unit with valid frontmatter, storing it under workspace/skills/self-evolve for rapid future reuse.

Yes, you can include custom scripts when creating workspace skills by placing them in the workspace/skills/self-evolve/scripts/ directory alongside the generated SKILL.md file.

You should generalize an improvised solution into a reusable skill after completing non-trivial, improvisation-heavy tasks or long workflows, ensuring the process is review-driven and non-redundant.

No, generating a SKILL.md file does not require manual frontmatter configuration because the process automatically ensures the skill unit includes valid frontmatter with the required name and description fields.

A limitation when saving reusable skills is that the process follows a minimal, governed approach to ensure skills are useful and non-redundant, meaning unreviewed or poorly generalized workflows may not be saved effectively.