migrate-to-skills

Convert Cursor rules and slash commands into Agent Skills format.

Updated Apr 15, 2026
One-click install
npx skills add https://github.com/shoshoavi/agentic_worflows --skill migrate-to-skills-shoshoavi
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: migrate-to-skills
Source: https://github.com/shoshoavi/agentic_worflows/tree/main/cursor/skills-cursor/migrate-to-skills
Command: npx skills add https://github.com/shoshoavi/agentic_worflows --skill migrate-to-skills-shoshoavi

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, leaving configuration fragmented across legacy locations. This Skill migrates those files into the unified .cursor/skills/ directory structure without altering their content. ## 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. - Verbatim Preservation: Copies body content character-for-character, guaranteeing no reformatting or content drift during migration. - Use Case: After upgrading Cursor, run this Skill to consolidate a project's scattered .mdc rules and command files into the skills directory, then optionally delete the originals. ## Quick Start Migrate all of my 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?▼

Identify rules with a description but no globs and no alwaysApply: true, then create a SKILL.md in .cursor/skills/{rule-name}/ containing name and description frontmatter plus the original body copied verbatim. Delete the original .mdc file after verifying the migration.

How do I convert Cursor slash commands to skills?▼

Create a SKILL.md in .cursor/skills/{command-name}/ with frontmatter containing name, a description inferred from the first heading, and disable-model-invocation: true. Keep the original markdown body exactly as-is so the command still works when triggered via the slash menu.

Which Cursor rules should not be migrated to skills?▼

Rules with globs or alwaysApply: true should stay as rules because they rely on automatic application behavior that skills do not provide. Only "Applied intelligently" rules with just a description are candidates for migration.

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

Yes, the migration is reversible by performing the inverse steps: recreate the original .mdc rule or .md command files from the generated SKILL.md content and remove the skill directories. Ask the assistant to undo the migration after it completes.

Does migrating commands to skills change how they are triggered?▼

No, because the migration adds disable-model-invocation: true to the frontmatter, which prevents automatic model invocation. The commands remain explicitly user-triggered through the slash menu, matching their original behavior.