managing-slash-commands
Creates, analyzes, updates, and improves slash commands including YAML frontmatter, argument handling, and command authoring workflows. Use when user asks how slash commands work, explaining command syntax and arguments, understanding command structure, describing command vs skill differences, asked to create a new slash command, evaluate existing commands for improvements, optimize commands for effectiveness, suggest converting current logic into a command, update outdated command information, or when user mentions command validation, best practices, or supporting files.
npx skills add majiayu000/claude-skill-registry --skill managing-slash-commands --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Managing Slash Commands This skill enables comprehensive management of slash commands including creation, analysis, improvement, and maintenance. ## When to Use This Skill Activate this skill when: - User requests creation of a new slash command - User asks to analyze or evaluate an existing slash command - User inquires whether current conversation logic should become a slash command - User requests updates to outdated slash command information - User mentions "slash command", "command file", "/command" in context of creation/improvement - You identify that a simple, reusable prompt would benefit from being a slash command ## Core Workflows ### Workflow 1: Creating a New Slash Command When creating a new slash command, follow this structured approach: #### Step 1: Requirements Gathering - Identify the command's primary purpose - Determine if it needs arguments ($ARGUMENTS, $1, $2, etc.) - Assess if bash execution is needed (! prefix) - Verify this should be a command, not a skill (simple prompt vs. complex workflow) - Load creation-guide.md for detailed decision matrix #### Step 2: Command Design - Choose descriptive command name (lowercase-with-hyphens, verb-noun format preferr
- When to Use This Skill
- Core Workflows
- Workflow 1: Creating a New Slash Command
- Workflow 2: Analyzing Existing Slash Commands
- Workflow 3: Suggesting Command vs. Skill Conversion
- Workflow 4: Updating Outdated Slash Commands
- Progressive Disclosure References
- Related Skills Integration
- Command Storage Locations
- Key Principles
- Using Helper Scripts with Slash Commands
- When to Use Scripts vs Interpreted Logic
- Script Organization
- Best Practices for Helper Scripts
What does the managing-slash-commands skill do?
Creates, analyzes, updates, and improves slash commands including YAML frontmatter, argument handling, and command authoring workflows. Use when user asks how slash commands work, explaining command syntax and arguments, understanding command structure, describing command vs skill differences, asked to create a new slash command, evaluate existing commands for improvements, optimize commands for effectiveness, suggest converting current logic into a command, update outdated command information, or when user mentions command validation, best practices, or supporting files.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill managing-slash-commands --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.