create-slash-command_skill

Overview

This skill automates creating DevAgent slash commands and preparing them for Cursor IDE. It generates a standardized command file in .agents/commands/, creates the required symlink in .cursor/commands/, and validates structure and naming. Use it to produce ready-to-insert snippet commands that follow workflow conventions.

How this skill works

The skill runs scripts to create a new command markdown file from a template, optionally referencing a specific workflow. It then creates a symlink pointing the Cursor commands folder to the new file so the command appears in the IDE. Finally, it validates presence, naming, workflow reference, input placeholder, and README listing.

When to use it

• You need a new slash command snippet for a DevAgent workflow.
• You want the command available inside Cursor IDE without manual symlink work.
• You need to enforce name and structure conventions for new commands.
• You want an automated validation checklist before publishing a command.

Best practices

• Use kebab-case for command filenames (lowercase with hyphens).
• Keep commands simple and self-contained: one Input Context placeholder and clear instructions.
• Reference the appropriate workflow in .devagent/core/workflows/ by name.
• Avoid generic names like help.md or test.md; pick descriptive command names.
• After creation, add the command to .agents/commands/README.md and confirm the symlink exists.

Example use cases

• Create a new research command that inserts a workflow snippet into chat and prompts the user for context.
• Add a clarify-feature command that references a feature-clarification workflow and includes clear input guidance.
• Generate a create-plan command tied to a planning workflow and link it into Cursor for easy reuse.
• Batch-create multiple commands with different workflow references and validate each with the checklist.