skill-creator

To convert recurring workflows into reusable documentation, you capture the conversation intent and save it as a structured SKILL.md file. This preserves the task instructions for standardizing future sessions.

Creating a skill requires a YAML frontmatter section containing the name and description fields. The main body is a SKILL.md file, which can be accompanied by optional scripts, references, and assets directories.

You automate capturing repeat task steps by outlining the intent, designing a name, and writing the SKILL.md body. This process applies a consistent template to standardize conventions for future activation.

Yes, you can include external scripts and references when building knowledge-management skills. The structure supports optional scripts, references, and assets directories to extend the skill's functionality.

The best way to organize and name skills is to follow a guided workflow that captures intent, designs a name, and writes the SKILL.md. Confirming with the user before saving ensures consistent organization.

You need to use a SKILL.md file for workflow automation when you want to save recurring conversational steps as structured skills. This allows you to standardize conventions and activate them in future tasks.