← ClaudeAtlas

import-commandlisted

Convert Cursor custom commands (.cursor/commands/*.md) to Claude Code skills (.claude/skills/*/SKILL.md). Use when the user says "import command to skill", "convert command to skill", or "migrate cursor command".
koborin-ai/site · ★ 9 · AI & Automation · score 79
Install: claude install-skill koborin-ai/site
# import-command Convert Cursor custom commands to Claude Code skills. ## Trigger Examples - "Import command to skill" - "Convert command to skill" - "Migrate cursor command to skill" - "Turn this command into a skill" ## Format Differences ### Cursor Command Format ```markdown # /command-name ## Overview [Description] ## Usage [Usage pattern] ## Prerequisites [Prerequisites] ## Execution Flow (steps) [Steps] ## AI considerations [AI guidance] ## Notes [Notes] ## Examples [Examples] ``` ### Claude Code Skill Format ```markdown --- name: skill-name description: [What it does and when to use it. Include trigger phrases.] --- # skill-name [One-line overview] ## Trigger Examples - "Trigger phrase 1" - "Trigger phrase 2" ## Prerequisites (optional) - [Prerequisite] ## Execution Flow ### 1. [Step name] - [Details] ## Notes - [Note] ``` ## Conversion Rules ### 1. Command Name → Skill Name - Remove leading `/` - Keep kebab-case: `/commit-push-pr` → `commit-push-pr` ### 2. Overview → Description (Frontmatter) - Combine "Overview" and "Usage" into a concise description - Add trigger phrases based on the command name and purpose - This is the most important part: description determines when the skill triggers ### 3. Usage → Trigger Examples - Convert usage patterns to natural language trigger phrases - Example: `/check-secrets [--strict]` → "Check for secrets", "Scan for leaks" ### 4. Execution Flow (steps) → Execution Flow - Keep the step structure -