skills.rest
cuongnm-dev
cuongnm-devCOMMUNITY
Explore all skills by this author →
GitHub

migrate-to-skills

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

Updated Aug 23, 2026
Search Tags:#automation#skills#commands#frontmatter#rules#migrate#cursor
One-click install
npx skills add https://github.com/cuongnm-dev/team-ai-config --skill migrate-to-skills-cuongnm-dev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: migrate-to-skills
Source: https://github.com/cuongnm-dev/team-ai-config/tree/main/cursor/skills-cursor/migrate-to-skills
Command: npx skills add https://github.com/cuongnm-dev/team-ai-config --skill migrate-to-skills-cuongnm-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This migration tool consolidates Cursor rules and slash commands into the Skill format, allowing teams to manage behavior as discrete skills and keep a single source of truth for automation.

Core Features & Use Cases

  • Migrate project rules from .cursor/rules/*.mdc to SKILL.md under .cursor/skills/{skill-name}/
  • Migrate user & project commands from .cursor/commands/*.md into SKILL.md files
  • Preserve the original body content verbatim and keep it in the SKILL.md body for traceability

Quick Start

Run the migration workflow to convert eligible Cursor rules and commands into SKILL.md files 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 the Skills format?▼

Migrate `.cursor/rules/*.mdc` files into `SKILL.md` files under `.cursor/skills/{skill-name}/` directories, ensuring the frontmatter includes `name` and `description` while preserving the original body content verbatim.

What is the best way to convert Cursor slash commands into SKILL.md files?▼

Convert user and project commands from `.cursor/commands/*.md` into `SKILL.md` files, preserving the exact body content for traceability and removing the original files after a successful migration to consolidate automation behavior.

Does migrating to Skills delete my original Cursor commands and rules?▼

Yes, migrating to Skills removes the original Cursor commands and rules from your project and user directories after successfully converting them into the `.cursor/skills/` structure and validating the new `SKILL.md` files.

What frontmatter is required when converting Cursor rules into Agent Skills?▼

When converting Cursor rules into Agent Skills, the new `SKILL.md` frontmatter must include the `name` and `description` fields to ensure the migrated automation behavior is properly registered and identifiable.

Why consolidate Cursor rules and commands into a single Skills format?▼

Consolidating Cursor rules and commands into the Skills format allows teams to manage behavior as discrete skills and maintain a single source of truth for project automation within the `.cursor/skills/` directory.

Can I apply this migration to both project and user Cursor directories?▼

Yes, you can apply the migration workflow to both project and user directories to convert eligible `.cursor/rules/*.mdc` and `.cursor/commands/*.md` files into structured `SKILL.md` automation files.

Related Skills

Explore More Software Engineering Skills→
fredericpoitevinfredericpoitevin

migrate-to-skills

Migrate Cursor rules and slash commands into SKILL.md files under .cursor/skills.

Community
Intermediate
LiuHarry1LiuHarry1
4

migrate-to-skills

Convert Cursor rules and slash commands into SKILL.md files under .cursor/skills.

Community
Advanced
AVIDS2AVIDS2
618

valid-skill

Validate SKILL.md frontmatter and Markdown body against the Agent Skills standard.

Community
Basic
JohnWebb4JohnWebb4

migrate-to-skills

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

Community
Intermediate