migrate-to-skills

Convert Cursor .mdc rules and .md commands into SKILL.md files.

5|2|Updated Jan 10, 2017
One-click install
npx skills add https://github.com/brujack/dotfiles --skill migrate-to-skills-brujack
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: migrate-to-skills
Source: https://github.com/brujack/dotfiles/tree/main/.cursor/skills-cursor/migrate-to-skills
Command: npx skills add https://github.com/brujack/dotfiles --skill migrate-to-skills-brujack

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a safe, repeatable way to convert legacy Cursor "Applied intelligently" rules and plain slash command markdown files into the Agent Skills SKILL.md format so they can be discovered and invoked consistently by Cursor and related tooling. It enforces exact body preservation and required frontmatter to avoid accidental content changes during migration.

Core Features & Use Cases

  • Rule conversion: Transform .mdc rule files that contain a description and lack globs/alwaysApply into .cursor/skills/{name}/SKILL.md while preserving the body verbatim.
  • Command conversion: Convert slash command .md files into skills with name, inferred description, and disable-model-invocation set to true to keep slash commands explicit.
  • Use case: Consolidate scattered project- and user-level Cursor rules and commands into a unified skills directory for easier maintenance, discovery, and versioning.

Quick Start

Run the migrate-to-skills skill to scan project and user Cursor directories and convert eligible .mdc rules and .md commands into .cursor/skills/{name}/SKILL.md while preserving each file's body exactly.

Frequently Asked Questions about migrate-to-skills

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I convert Cursor rules to skills format?

Migrating Cursor .mdc rules to skills involves transforming files with a description but no globs or alwaysApply into .cursor/skills/{name}/SKILL.md. The process preserves file bodies verbatim and adds required frontmatter for consistent agent discovery and invocation.

What is the difference between Cursor applied intelligently rules and skills?

Cursor applied intelligently rules are .mdc files with a description but no globs or alwaysApply settings, whereas skills use a structured SKILL.md format with required frontmatter. Migrating rules to skills consolidates scattered configurations into a unified directory for easier maintenance and versioning.

How do I migrate Cursor slash commands to SKILL.md files?

Migrating Cursor slash commands to SKILL.md files converts plain .md command files into skills with an inferred description and disable-model-invocation set to true. This keeps slash commands explicit while adopting the unified skills directory structure.

Can I migrate both project and user-level Cursor rules at the same time?

Yes, you can migrate both project and user-level Cursor rules simultaneously. The migration process scans both project and user Cursor directories to convert eligible .mdc rules and .md commands into the .cursor/skills/{name}/SKILL.md format.

Does converting Cursor commands to skills change the original file content?

No, converting Cursor commands to skills does not change the original file content. The migration enforces exact body preservation verbatim and only adds required frontmatter fields to avoid accidental content changes during the conversion process.

What happens to original Cursor rule files after migration to skills?

After migration to skills, the original Cursor rule files can optionally be removed. The process first verifies the converted .cursor/skills/{name}/SKILL.md files before optionally deleting the original .mdc and .md files from the project or user directories.