Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
WHAT: Create Claude Code slash commands - reusable markdown workflows invoked with /command-name. WHEN: User wants to create, make, or add a slash command. User wants to automate a repetitive workflow or document a consistent process for reuse. KEYWORDS: "create a command", "make a slash command", "add a command", "new command", "/command", "automate this workflow", "make this repeatable"
WHAT: Create Claude Code slash commands - reusable markdown workflows invoked with /command-name. WHEN: User wants to create, make, or add a slash command. User wants to automate a repetitive workflow or document a consistent process for reuse. KEYWORDS: "create a command", "make a slash command", "add a command", "new command", "/command", "automate this workflow", "make this repeatable"
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Then review README.md for any prerequisites, environment setup, or post-install checks. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run.
Slash commands are markdown files in .claude/commands/ (project) or ~/.claude/commands/ (global) that expand into prompts when invoked.
--- description: Brief description for /help (required) argument-hint: <required> or [optional] (if takes arguments) --- # Command Title [Instructions for agent to execute autonomously]
Check if in git repo: git rev-parse --is-inside-work-tree Default: Git repo โ .claude/commands/, No git โ ~/.claude/commands/ Override if user explicitly says "global" or "project" Report chosen location before proceeding.
Load references/patterns.md and present options: PatternStructureUse WhenWorkflow AutomationAnalyze โ Act โ ReportMulti-step with clear sequenceIterative FixingRun โ Parse โ Fix โ RepeatFix issues until passingAgent DelegationContext โ Delegate โ IterateComplex tasks, user reviewSimple ExecutionParse โ Execute โ ReturnWrapper for existing tools Ask: "Which pattern is closest to what you want?"
A. Name and Purpose "What should the command be called?" (kebab-case: my-command) "What does it do?" (for description field) B. Arguments "Does it take arguments? Required or optional?" Required: <placeholder>, Optional: [placeholder] C. Workflow Steps "What specific steps should it follow?" "What tools or commands should it use?" D. Constraints "Any specific tools to use or avoid?" "Any files to read for context?"
Load references/best-practices.md for: Template structure Writing style (imperative form) Quality checklist Key principles: Use imperative form: "Run X", not "You should run X" Be explicit: "Run make lint", not "Check for errors" Include expected outcomes Define error handling State success criteria
mkdir -p [directory-path] Write the command file. Report: File location What the command does How to use: /command-name [args]
Suggest: "Test with /command-name [args]" Iterate based on feedback.
Imperative form (verb-first): โ "Run git status" โ "You should run git status" Specific, not vague: โ "Run make lint to check for errors" โ "Check for errors" Include outcomes: โ "Run git status - should show modified files" โ "Run git status" Realistic examples: โ git commit -m "Add OAuth2 authentication" โ git commit -m "foo bar"
1. Check for .PLAN.md 2. Analyze git status/diff 3. Perform actions 4. Report results
1. Run make all-ci (max 10 iterations) 2. Parse errors by category 3. Apply targeted fixes 4. Repeat until success or stuck
1. Present context 2. Invoke subagent with Task tool 3. Iterate with user feedback 4. Save output after approval See references/examples.md for full command examples.
Before finalizing: Name is kebab-case (my-command, not my_command) Description is action-oriented Steps are numbered and specific Tool usage explicitly specified Error handling defined Success criteria stated Uses imperative form
Use underscores in command names (use hyphens) Write vague instructions ("fix errors") Skip error handling Use second person ("You should...") Create commands without testing Leave success criteria undefined
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.