doro-command-creator

What This Skill Does

The doro-command-creator skill is a specialized agentic workflow tool designed to help developers and power users turn repetitive, multi-step tasks into standardized Claude Code slash commands. By leveraging a structured markdown approach, this skill guides users through defining clear, imperative instructions that the AI agent can execute autonomously. It handles the organizational heavy lifting, such as determining whether to save a command locally in a project-specific directory or globally for system-wide access.

Installation

You can install this skill directly by running the following command in your terminal: clawhub install openclaw/skills/skills/a2mus/doro-command-creator

Use Cases

This skill is perfect for scenarios involving standard operational procedures (SOPs). For example, if you frequently perform a 'pull-latest-test-and-deploy' workflow, this skill helps you encode those exact steps into a command like /deploy-prep. It is also highly effective for onboarding new team members by codifying best practices into repeatable commands, ensuring that every user follows the same analysis and execution pattern when debugging or refactoring code. It excels in complex task orchestration where manual steps are error-prone.

Example Prompts

1. "I find myself running the same suite of git commands followed by a linter every morning; can you help me create a command for this?"
2. "I need to automate the code review checklist process. Let's make a new command called /review that forces the agent to analyze files for security vulnerabilities first."
3. "Make a global slash command that runs our build script and then parses the test logs for errors."

Tips & Limitations

To get the most out of your commands, always use the imperative voice—for instance, use 'Run X' rather than 'Try to run X'. Be as specific as possible; the agent performs best when it has explicit steps and clear success criteria. Remember that slash commands are only as effective as the documentation within them. Always include a brief 'description' and 'argument-hint' in the frontmatter so that your /help menu remains useful as your collection of commands grows. Keep in mind that while this tool automates the creation process, you should always test the generated command locally before relying on it for critical production pipelines.