migrate-to-skills

Convert Cursor rules and slash commands into Agent Skills format.

Updated Mar 21, 2026
One-click install
npx skills add https://github.com/pulak999/ai-tooling --skill migrate-to-skills-pulak999
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: migrate-to-skills
Source: https://github.com/pulak999/ai-tooling/tree/main/ai-assistant-kit/cursor-skills-cursor/migrate-to-skills
Command: npx skills add https://github.com/pulak999/ai-tooling --skill migrate-to-skills-pulak999

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Cursor projects accumulate rules (.cursor/rules/.mdc) and slash commands (.cursor/commands/.md) that predate the Agent Skills format. Manually converting each file to the .cursor/skills/ structure is repetitive and error-prone, especially when body content must be preserved verbatim. ## Core Features & Use Cases - Rule Migration: Converts "Applied intelligently" rules (those with a description but no globs or alwaysApply) from .mdc files into SKILL.md files with proper name and description frontmatter. - Command Migration: Converts slash commands into skills, inferring the description from the first heading and adding disable-model-invocation so they remain user-triggered. - Parallel Subagent Workflow: Dispatches subagents to handle project rules, project commands, and user commands concurrently, then summarizes results and supports undoing the migration. - Use Case: After upgrading Cursor, run this skill to consolidate all legacy rules and commands across your workspace and home directory into the unified .cursor/skills/ directory. ## Quick Start Ask the assistant to migrate all Cursor rules and slash commands in this project to the Agent Skills format.

Frequently Asked Questions about migrate-to-skills

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

FAQPage Schema
How do I migrate Cursor rules to Agent Skills format?

Move each eligible .mdc rule into .cursor/skills/{name}/SKILL.md, adding a name field and removing globs and alwaysApply from the frontmatter. Only rules with a description but no globs and no alwaysApply: true qualify for migration.

How to convert Cursor slash commands to skills?

Create .cursor/skills/{name}/SKILL.md with frontmatter containing name, a description inferred from the first heading, and disable-model-invocation: true. Copy the original command body verbatim below the frontmatter.

Which Cursor rules should not be migrated to skills?

Rules with globs patterns or alwaysApply: true should stay as rules because they are context-triggered rather than description-discovered. Only "Applied intelligently" rules with a description are candidates for migration.

Can I undo a Cursor rules to skills migration?

Yes, the migration is reversible by reversing the steps: move each SKILL.md body back to its original .mdc or .md path and restore the original frontmatter. Ask the assistant to undo the migration after it completes.

Does the migration change my rule or command content?

No, the body content is copied character-for-character with all whitespace, formatting, and code blocks preserved. Only the frontmatter is modified by adding name and description fields and removing rule-specific keys.