migrate-to-skills

Convert Cursor rules and commands into standardized SKILL.md directories.

Updated Feb 23, 2019
One-click install
npx skills add https://github.com/JohnWebb4/dotfiles --skill migrate-to-skills-johnwebb4
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: migrate-to-skills
Source: https://github.com/JohnWebb4/dotfiles/tree/main/.cursor/skills-cursor/migrate-to-skills
Command: npx skills add https://github.com/JohnWebb4/dotfiles --skill migrate-to-skills-johnwebb4

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Consolidates Cursor automation into standardized Agent Skills by converting project rules and user commands into SKILL.md entries, enabling easier reuse and sharing.

Core Features & Use Cases

  • Converts Cursor rules (.cursor/rules/*.mdc) into SKILL.md under .cursor/skills with preserved content.
  • Converts Cursor commands (.cursor/commands/*.md) into SKILL.md under .cursor/skills with disable-model-invocation: true and preserves body.
  • Preserves original body content exactly and creates accessible skills for collaboration.

Quick Start

Run the migration tool at repository root to convert all eligible Cursor rules and commands to SKILL.md entries under .cursor/skills.

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 standardized markdown skills?

To migrate Cursor rules, the conversion tool processes .cursor/rules/*.mdc files into SKILL.md directories under .cursor/skills, preserving the original body content exactly while generating required frontmatter.

Can I convert Cursor slash commands into reusable skills?

Yes, you can convert Cursor commands by migrating .cursor/commands/*.md files into SKILL.md entries under .cursor/skills with the disable-model-invocation: true setting, preserving the original command body content.

What is the difference between migrating Cursor rules versus commands?

Migrating Cursor rules generates standard SKILL.md files from .mdc inputs, whereas migrating commands also adds the disable-model-invocation: true frontmatter to prevent automatic model triggering for converted slash commands.

Does migrating Cursor automation preserve custom scripts and assets directories?

Yes, migrating Cursor automation preserves custom directories by identifying and handling optional scripts/, references/, and assets/ folders available in the workspace during the SKILL.md generation process.

What is the best way to consolidate user-level Cursor commands for sharing?

The best way to consolidate user-level Cursor commands is migrating ~/.cursor/commands/*.md files into standardized SKILL.md entries under ~/.cursor/skills, enabling easier reuse and sharing across different projects.