creating-commands

Create and test custom slash commands using Test-Driven Development.

Updated Feb 12, 2026
One-click install
npx skills add https://github.com/othercode/profiles --skill creating-commands-othercode
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: creating-commands
Source: https://github.com/othercode/profiles/tree/main/plugins/prompt-engineering/skills/creating-commands
Command: npx skills add https://github.com/othercode/profiles --skill creating-commands-othercode

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the creation and testing of custom slash commands, ensuring they are robust, user-friendly, and integrate seamlessly with existing workflows.

Core Features & Use Cases

  • Command Creation Guidance: Provides best practices and structure for defining new commands.
  • TDD for Commands: Implements a Test-Driven Development approach to command creation, ensuring reliability.
  • Argument Handling: Details how to effectively use $ARGUMENTS, $1, $2, and other placeholders for dynamic command behavior.
  • Use Case: You need to create a new /deploy command for your project. This Skill guides you through defining its arguments, ensuring it references the correct deployment skills, and testing it thoroughly before deployment.

Quick Start

Use the creating-commands skill to define a new /backup command that takes a directory as an argument.

Frequently Asked Questions about creating-commands

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create custom slash commands for my CLI workflow?

To create custom slash commands, define the command structure, handle dynamic arguments using $ARGUMENTS and $1 placeholders, and ensure discoverability through descriptive metadata.

How does Test-Driven Development apply to building custom commands?

Test-Driven Development for custom commands involves writing tests for argument handling and dynamic content injection before implementation, ensuring the command behaves reliably within your development environment.

How do I use placeholders like $ARGUMENTS and $1 for argument handling in commands?

Placeholders like $ARGUMENTS and $1 capture user input passed to the command, allowing you to inject dynamic content and customize command behavior based on the provided arguments during execution.

What is the best way to ensure custom commands are discoverable and integrate with existing workflows?

Ensure custom commands are discoverable by adding clear descriptions, referencing relevant skills for methodology, and using bash execution and file references to seamlessly integrate with existing workflows.

Can I use bash execution and file references to inject dynamic content into commands?

Yes, custom commands support dynamic content injection by executing bash commands and referencing files directly, allowing the command output to adapt based on real-time execution results.

Do I need to reference other skills when creating a new command?

Referencing other skills is recommended to import established methodologies into your command, ensuring it follows best practices and integrates correctly with the broader development environment.