migrate-to-skills

Converts CURTIS-style rules and slash commands to SwaggerHub format.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Convert Cursor rules and slash commands into Agent Skills format, enabling reuse, standardization, and future automation.

Core Features & Use Cases

  • Migrate project rules from {workspaceFolder}/**/.cursor/rules/*.mdc to .cursor/skills/{rule-name}/SKILL.md with frontmatter including name and description
  • Migrate user commands from ~/.cursor/commands/*.md to .cursor/skills/{command-name}/SKILL.md
  • Preserve the exact body content of the source files during migration and ignore reserved paths (like ~/.cursor/worktrees)

Quick Start

Run the migration to convert all applicable project rules and user commands into SKILL.md formats under the skills directory, preserving the original body content exactly.

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 Skills format?

Migrate Cursor rules by converting .mdc files from the .cursor/rules directory into SKILL.md files with YAML frontmatter, preserving the original body content exactly for reusable automation.

What is the process to convert Cursor slash commands into reusable automation?

Converting Cursor slash commands involves moving .md files from ~/.cursor/commands into a skills directory, generating SKILL.md files with name and description metadata while keeping the body intact.

Does the migration preserve the original content of Cursor rules and commands?

Yes, the migration preserves the exact body content of source files during conversion. It only adds YAML frontmatter with name and description to the new SKILL.md files.

Can I migrate both project rules and user commands in Cursor?

Yes, you can migrate both project rules from .cursor/rules and user commands from ~/.cursor/commands into the standardized Skills directory structure end-to-end.

What limitations apply when migrating Cursor rules to YAML frontmatter?

The migration ignores reserved paths like ~/.cursor/worktrees and only processes valid project rules and user commands, skipping reserved folders to prevent configuration conflicts.