Command creator: author optimized Claude Code slash commands
Step-by-step workflow to design, structure and install reusable Claude Code slash commands — patterns, examples, quality checklist
- What
- Step-by-step workflow to design, structure and install reusable Claude Code slash commands — patterns, examples, quality checklist
- Cost
- Free
- Needs
- Claude Code (the commands target its .claude/commands/ structure); nothing else to install — install the whole folder so the bundled references (patterns, examples, best-practices) come along
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — @softaworks's command-creator: the skill to use when creating Claude Code slash commands. It walks through a six-step workflow — auto-detect the location (project .claude/commands/ vs global ~/.claude/commands/), show the four command patterns (workflow automation, iterative fixing, agent delegation, simple execution), gather name/purpose/arguments/steps/tool restrictions, generate the optimized command with bundled references (patterns, examples, best-practices), write the file, and confirm usage. Enforces kebab-case naming, imperative agent-optimized writing, explicit error handling and success criteria. MIT-licensed. Honest notes: it's a conversation-driven assistant, not a one-shot generator — expect it to ask you questions before writing anything; and the bundled reference docs live in the repo, so install the whole folder. Skill Harbor never reviews the code, review it yourself before use. Discovered via skills.sh.
Version:
Quick answer
Command creator is a free Muse skill for authoring optimized Claude Code slash commands through a six-step workflow. It auto-detects the location, shows four command patterns covering workflow automation, iterative fixing, agent delegation and simple execution, gathers name, purpose, arguments, steps and tool restrictions, then generates the optimized command.
Install
Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 11, 2026📌 Pinned version: commit 3027f20Step 0 — before installing anything: read this install prompt, summarize in a few lines what this build does and what installing it involves, then ask me to confirm before you proceed. Prerequisites: Claude Code (the commands target its .claude/commands/ structure); nothing else to install — install the whole folder so the bundled references (patterns, examples, best-practices) come along Install "Command creator: author optimized Claude Code slash commands" for me. It gives my agent @softaworks's skill for creating Claude Code slash commands: a six-step workflow that auto-detects the location (project vs global), shows the four command patterns (workflow automation, iterative fixing, agent delegation, simple execution), gathers name/purpose/arguments/steps/tool restrictions, then generates the optimized command with bundled references, writes the file, and confirms usage. MIT-licensed. Repository: https://raw.githubusercontent.com/softaworks/agent-toolkit/3027f20f3181758385a1bb8c022d4041dfb4de84/dist/plugins/command-creator/skills/command-creator/SKILL.md Pinned version: install the code at commit 3027f20f3181758385a1bb8c022d4041dfb4de84 exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Fetch the SKILL.md file AND its bundled references folder from the repository path into a temporary folder 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "command-creator". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. nothing — just say "create a command for X" and answer its questions). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Saved to your recent installs. Find it anytime on /connect.
🔒 Security, provenance and what this touches
The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Verification certificate
Dated facts about what was checked for this listing, and how. This is not a safety certification.
- Pinned version
- 3027f20 · 2026-10-13
- Sandbox install test
- Install ran in our test sandbox · Nov 11, 2026
- Creator identity
- Not verified
- Fingerprint watch
- Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
- Install prompt analysis
- 2026-10-13 : No commands, network calls, packages, file writes or API keys detected.
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Questions
How do I install a skill?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a skill before installing it.