skill-creator

To turn a workflow into a well-structured skill, extract the intent from conversations or task sequences, draft YAML frontmatter with a name and description, define trigger conditions, and add realistic test prompts for evaluation.

Documenting trigger conditions for predictable skill activation involves drafting concise YAML frontmatter alongside a Markdown body that explicitly describes the operational instructions and scenarios where the skill should execute.

Yes, you can extract skill intent from existing prompts and task sequences by applying an evaluation-driven process that captures user goals, defines trigger authoring rules, and translates them into a repeatable skill definition.

You add evaluation criteria and baselines to a skill definition by creating 2–3 realistic test prompts within the Markdown body, enabling continuous evaluation loops that improve skill quality over time.

Yes, YAML frontmatter is required to create a valid skill, and it must include at least a name and a description to ensure the operational instructions in the Markdown body are properly structured.

When adapting third-party workflows into skills, you preserve provenance and licenses by maintaining source references within the skill's optional references or assets during the conversion process.