migrate-to-skills

Convert Cursor rules and slash commands into SKILL.md files.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill consolidates and standardizes Cursor-based rules and slash commands by converting them to a unified SKILL.md format, preserving content and enabling centralized discovery and execution.

Core Features & Use Cases

  • Converts .cursor/rules/.mdc files and .cursor/commands/.md files (project) and ~/.cursor/commands/*.md (user) into SKILL.md entries under .cursor/skills/
  • Preserves the exact body content during migration for auditability
  • Generates a minimal frontmatter with name and description to enable discovery

Quick Start

Run the migration tool to convert eligible Cursor rules and commands into SKILL.md entries under the skills directory.

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 and slash commands into a standardized format?

Migrating Cursor rules and slash commands involves converting .mdc rule files and .md command files into a unified SKILL.md format under the .cursor/skills/ directory, preserving exact content while adding standardized frontmatter.

Does the Cursor migration process preserve the original content of my rules?

Yes, the Cursor migration process preserves the exact body content of your project-level and user-level rules during conversion, ensuring auditability while generating minimal frontmatter with name and description for discovery.

What happens to legacy globs and alwaysApply flags when converting to SKILL.md?

When converting to SKILL.md, legacy globs and alwaysApply flags are removed from the files, replacing them with a consistent discovery header that includes only the required name and description frontmatter.

Can I convert both project-level and user-level Cursor commands using this method?

Yes, you can convert both project-level .cursor/commands/*.md files and user-level ~/.cursor/commands/*.md files, creating per-rule skill directories within the .cursor/skills/ structure for centralized skill management.

Why do I need to add frontmatter when migrating Cursor rules into skill directories?

Adding frontmatter with name and description fields is required to enable consistent discovery and centralized execution of the migrated rules within the Cursor ecosystem, satisfying the standardized SKILL.md format requirements.

What is the best way to centralize multiple Cursor rules and commands for unified management?

The best way to centralize Cursor rules and commands is to consolidate them from scattered .cursor/rules and .cursor/commands locations into a standardized SKILL.md format, enabling consistent discovery and execution.