migrate-to-skills

Migrating legacy subagents requires converting them into SKILL.md files with standardized frontmatter. The workflow enforces required fields like name and description, while applying subagent context and activation behavior for consistent skill creation.

The unified Agent Skills format uses SKILL.md files to standardize automation workflows. It replaces disparate legacy rules and subagents with a consistent structure, enforcing required frontmatter fields like name and description for reliable activation.

Yes, converting legacy rules to SKILL.md preserves original material for reference. The workflow generates standardized frontmatter and body content for activation without discarding the source subagents or slash commands during the transition.

Required fields for converting subagents into SKILL.md files include name and description. The migration workflow also enforces needed fields such as subagent context, model simplification, and activation behavior to ensure consistent skill creation.

Yes, a single phase-driven workflow supports converting multiple resource types including commands and rules. It handles discovery, classification, approval, and conversion across multiple toolchains to ensure safe and repeatable transitions.