migrate-to-skills

Convert Cursor rules and slash commands into Agent Skills format.

3|Updated Jul 2, 2026
One-click install
npx skills add https://github.com/ArangoGutierrez/claude-toolkit --skill migrate-to-skills-arangogutierrez
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: migrate-to-skills
Source: https://github.com/ArangoGutierrez/claude-toolkit/tree/main/.cursor/skills-cursor/migrate-to-skills
Command: npx skills add https://github.com/ArangoGutierrez/claude-toolkit --skill migrate-to-skills-arangogutierrez

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Cursor projects accumulate rules (.cursor/rules/.mdc) and slash commands (.cursor/commands/.md) that need to be consolidated into the newer Agent Skills format (.cursor/skills/). Doing this by hand is 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 plain markdown slash commands into skills, adding frontmatter with name, inferred description, and disable-model-invocation so they remain user-triggered. - Verbatim Body Preservation: Copies the original body content character-for-character without reformatting or modification, and supports undoing the migration on request. - Use Case: You have a project with a dozen .mdc rules and slash commands scattered across .cursor/rules and .cursor/commands; run this migration to consolidate them into .cursor/skills/ with valid SKILL.md files. ## Quick Start Migrate all of my Cursor rules and slash commands in this workspace 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?▼

Read each .mdc rule, extract its description, and write a SKILL.md in .cursor/skills/{name}/ with name and description frontmatter plus the original body copied verbatim. Only rules with a description and no globs or alwaysApply qualify for migration.

How do I convert Cursor slash commands to skills?▼

Create .cursor/skills/{name}/SKILL.md for each command file, adding frontmatter with name from the filename, a description inferred from the content, and disable-model-invocation: true so the command stays user-triggered. Keep the original markdown body unchanged.

Which Cursor rules should not be migrated to skills?▼

Rules with globs or alwaysApply: true should not be migrated because they are context-attached rules rather than 'Applied intelligently' rules. Files under ~/.cursor/worktrees and ~/.cursor/skills-cursor are also excluded.

Can I undo a Cursor rules-to-skills migration?▼

Yes, the migration is reversible. Ask the assistant to undo the migration and it will restore the original .mdc rule files and .md command files by reversing the conversion steps.

Why does the migrated skill body need to be copied verbatim?▼

The body content contains the operational instructions that must behave identically after migration. Reformatting or 'improving' the text risks changing behavior, so the content is copied character-for-character including whitespace and code blocks.