migrate-to-skills

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

Updated Dec 17, 2024
One-click install
npx skills add https://github.com/LAF-US/IDAHO-VAULT --skill migrate-to-skills-laf-us
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: migrate-to-skills
Source: https://github.com/LAF-US/IDAHO-VAULT/tree/main/.cursor/skills-cursor/migrate-to-skills
Command: npx skills add https://github.com/LAF-US/IDAHO-VAULT --skill migrate-to-skills-laf-us

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Migrates existing Cursor rules and slash commands into the standardized Agent Skills format, streamlining governance and reuse.

Core Features & Use Cases

  • Converts eligible project rules: .cursor/rules/*.mdc with a description but no globs or alwaysApply into SKILL.md entries under .cursor/skills/{skill-name}/SKILL.md.
  • Converts all project and user slash commands: .cursor/commands/*.md into SKILL.md with a name derived from the file, preserving the original body exactly.
  • Consolidates related commands into the skills directory to centralize skill management and discovery.

Quick Start

Start the migration to convert all applicable rules and commands to skills, preserving their bodies 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?

Migrate Cursor rules by converting eligible .mdc project rules with a description and no globs or alwaysApply settings into standardized SKILL.md entries under the skills directory.

Can I convert slash commands to SKILL.md format?

Convert slash commands by transforming all project and user .md command files into SKILL.md entries, deriving the skill name from the original file and preserving the body exactly.

Which Cursor rules are eligible for conversion to SKILL.md?

Eligible Cursor rules include project rules that contain a description but lack globs or alwaysApply flags, ensuring only conditional rules migrate to the SKILL.md format.

Does the migration preserve the original command body content?

Migration preserves the original command body exactly, moving the content into a new SKILL.md file without altering the existing instructions or logic.

What is the best way to consolidate Cursor commands and rules?

Consolidate Cursor commands and rules by migrating both into a centralized skills directory, centralizing management and discovery for standardized SKILL.md entries.