migrate-to-skills

You can convert Cursor rules and slash commands by migrating .mdc and .md files into the Agent Skills SKILL.md format. This process transforms frontmatter, preserves body content, infers descriptions, and sets invocation flags for project-level and user-level configurations.

Migrating .mdc rule files to a unified skills framework involves transforming them into SKILL.md format. This conversion adapts the frontmatter while preserving the original descriptions and body content, streamlining the transition to a more organized management system.

Yes, migrating slash commands to SKILL.md format preserves existing content. It converts .md command files by inferring descriptions, adding necessary metadata like disable-model-invocation flags, and applying precise content preservation during the frontmatter transformation.

Yes, you can bulk convert project-level and user-level Cursor configurations simultaneously. The migration applies to configurations within the .cursor directory, handling both rules and commands efficiently to consolidate them into a unified skills framework.

Converting slash commands requires inferring descriptions and setting invocation flags because .md command files lack certain metadata. Adding flags like disable-model-invocation and inferring descriptions ensures the new SKILL.md format maintains proper discoverability and function.

The primary limitation of migrating Cursor rules to the Agent Skills format is that it strictly targets .mdc and .md files within the .cursor directory. Files outside this structure or in unsupported formats require manual adjustment before the automated conversion can process them.