How do I install the Cursor Migrate To Skills skill?

Run npx skillmds@latest add kunanonj/cursor-migrate-to-skills in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Cursor Migrate To Skills safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Cursor Migrate To Skills?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Cursor Migrate To Skills free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Cursor Migrate To Skills?

KunanonJ (@kunanonj) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Cursor Migrate To Skills by kunanonj

Name: Cursor Migrate To Skills
Author: KunanonJ

Cursor Migrate To Skills

Convert 'Applied intelligently' Cursor rules (.cursor/rules/*.mdc) and slash commands (.cursor/commands/*.md) to Agent Skills format (.cursor/skills/). Use when you want to migrate rules or commands to skills, convert .mdc rules to SKILL.md format, or consolidate commands into the skills directory.

KunanonJ Updated Sep 17, 2026

File contents

Migrate Rules and Slash Commands to Skills

Convert Cursor rules ("Applied intelligently") and slash commands to Agent Skills format.

CRITICAL: Preserve the exact body content. Do not modify, reformat, or "improve" it - copy verbatim.

Locations

Level	Source	Destination
Project	`{workspaceFolder}/*/.cursor/rules/.mdc`, `{workspaceFolder}/.cursor/commands/*.md`	`.cursor/skills/`
User	`~/.cursor/commands/*.md`	`~/.cursor/skills/`

Notes:

Cursor rules inside the project can live in nested directories. Be thorough in your search.
Ignore anything in ~/.cursor/worktrees
Ignore anything in ~/.cursor/skills-cursor (reserved for Cursor's internal built-in skills)

Finding Files to Migrate

Rules: Migrate if rule has a description but NO globs and NO alwaysApply: true.

Commands: Migrate all - they're plain markdown without frontmatter.

Conversion Format

Rules: .mdc → SKILL.md

# Before: .cursor/rules/my-rule.mdc
---
description: What this rule does
globs:
alwaysApply: false
---
# Title
Body content...

# After: .cursor/skills/my-rule/SKILL.md
---
name: my-rule
description: What this rule does
---
# Title
Body content...

Changes: Add name field, remove globs/alwaysApply, keep body exactly.

Commands: .md → SKILL.md

# Before: .cursor/commands/commit.md
# Commit current work
Instructions here...

# After: .cursor/skills/commit/SKILL.md
---
name: commit
description: Commit current work with standardized message format
disable-model-invocation: true
---
# Commit current work
Instructions here...

Changes: Add frontmatter with name (from filename), description (infer from content), and disable-model-invocation: true, keep body exactly.

Notes

name must be lowercase with hyphens only
description is critical for skill discovery
Optionally delete originals after verifying migration works

Workflow

Create the skills directories if they don't exist
Find files to migrate in both project and user directories
For rules, check if it's an "applied intelligently" rule (has description, no globs, no alwaysApply: true). Commands are always migrated.
Make a list of files to migrate. If empty, done.
For each file, read it, then write the new skill file preserving the body content EXACTLY.
Delete the original file.
Summarize the results. Let the user know they can ask to undo the migration.

CRITICAL: Copy the body content character-for-character. Do not reformat, fix typos, or "improve" anything.

---name: cursor-migrate-to-skillsdescription: Convert 'Applied intelligently' Cursor rules (.cursor/rules/*.mdc) and slash commands (.cursor/commands/*.md) to Agent Skills format (.cursor/skills/). Use when you want to migrate rules or commands to skills, convert .mdc rules to SKILL.md format, or consolidate commands into the skills directory.---# Migrate Rules and Slash Commands to SkillsConvert Cursor rules ("Applied intelligently") and slash commands to Agent Skills format.**CRITICAL: Preserve the exact body content. Do not modify, reformat, or "improve" it - copy verbatim.**## Locations| Level | Source | Destination ||-------|--------|-------------|| Project | `{workspaceFolder}/**/.cursor/rules/*.mdc`, `{workspaceFolder}/.cursor/commands/*.md` | `.cursor/skills/` || User | `~/.cursor/commands/*.md` | `~/.cursor/skills/` |Notes:- Cursor rules inside the project can live in nested directories. Be thorough in your search.- Ignore anything in ~/.cursor/worktrees- Ignore anything in ~/.cursor/skills-cursor (reserved for Cursor's internal built-in skills)## Finding Files to Migrate**Rules**: Migrate if rule has a `description` but NO `globs` and NO `alwaysApply: true`.**Commands**: Migrate all - they're plain markdown without frontmatter.## Conversion Format### Rules: .mdc → SKILL.md```markdown# Before: .cursor/rules/my-rule.mdc---description: What this rule doesglobs:alwaysApply: false---# TitleBody content...``````markdown# After: .cursor/skills/my-rule/SKILL.md---name: my-ruledescription: What this rule does---# TitleBody content...```Changes: Add `name` field, remove `globs`/`alwaysApply`, keep body exactly.### Commands: .md → SKILL.md```markdown# Before: .cursor/commands/commit.md# Commit current workInstructions here...``````markdown# After: .cursor/skills/commit/SKILL.md---name: commitdescription: Commit current work with standardized message formatdisable-model-invocation: true---# Commit current workInstructions here...```Changes: Add frontmatter with `name` (from filename), `description` (infer from content), and `disable-model-invocation: true`, keep body exactly.## Notes- `name` must be lowercase with hyphens only- `description` is critical for skill discovery- Optionally delete originals after verifying migration works## Workflow1. Create the skills directories if they don't exist2. Find files to migrate in both project and user directories3. For rules, check if it's an "applied intelligently" rule (has `description`, no `globs`, no `alwaysApply: true`). Commands are always migrated.4. Make a list of files to migrate. If empty, done.5. For each file, read it, then write the new skill file preserving the body content EXACTLY.6. Delete the original file.7. Summarize the results. Let the user know they can ask to undo the migration.**CRITICAL: Copy the body content character-for-character. Do not reformat, fix typos, or "improve" anything.**

Frequently asked questions