migrate-to-skills

Convert Cursor rules and slash commands into Agent Skills format.

1|Updated Apr 16, 2026
One-click install
npx skills add https://github.com/PandelisZ/skills --skill migrate-to-skills-pandelisz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: migrate-to-skills
Source: https://github.com/PandelisZ/skills/tree/main/skills/migrate-to-skills
Command: npx skills add https://github.com/PandelisZ/skills --skill migrate-to-skills-pandelisz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts Cursor rules (.cursor/rules/.mdc) and slash commands (.cursor/commands/.md) into the Agent Skills format (.cursor/skills/). This enables centralized skill execution and reusability across agents.

Core Features & Use Cases

  • Migrate project rules that describe behavior (with a description) but lack globs and do not have alwaysApply: true into SKILL.md files.
  • Migrate all slash commands into dedicated SKILL.md entries under .cursor/skills/, preserving the original body exactly.
  • Support for both project-scoped and user-scoped migrations, with clear dry-run capabilities before deletion.

Quick Start

Run the migration to convert all eligible Cursor rules and slash commands into 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?

Yes, you can convert Cursor slash commands into Agent Skills. The migration process takes .cursor/commands/*.md files and moves their preserved body content into dedicated SKILL.md entries under the .cursor/skills/ directory for centralized execution.

What is the difference between Cursor rules and Agent Skills?

Cursor rules are behavior descriptions in .mdc files, while Agent Skills are centralized SKILL.md files that enable reusability across agents. Migrating converts eligible rules lacking globs and alwaysApply flags into the skills format for better execution.

Can I dry-run a migration of Cursor rules before deleting files?

Yes, the migration workflow supports clear dry-run capabilities before deletion. You can verify that rules and slash commands are correctly converted into SKILL.md files before the original .mdc and .md files are permanently removed.

Does the migration handle nested Cursor rule paths?

Yes, the migration process handles nested rule paths. It processes project and user scopes, ensuring that deeply nested .cursor/rules/*.mdc files are correctly mapped into the .cursor/skills/ directory structure without losing content.

Which Cursor rules are eligible for migration to skills?

Eligible Cursor rules describe behavior with a description but lack globs and do not have alwaysApply set to true. All slash commands are eligible. The migration filters rules based on these criteria before generating SKILL.md files.