โ† All skills
Tencent SkillHub ยท Developer Tools

Command Creator

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"

skill openclawclawhub Free
0 Downloads
0 Stars
0 Installs
0 Score
High Signal

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"

โฌ‡ 0 downloads โ˜… 0 stars Unverified but indexed

Install for OpenClaw

Quick setup
  1. Download the package from Yavira.
  2. Extract the archive and review SKILL.md first.
  3. Import or place the package into your OpenClaw setup.

Requirements

Target platform
OpenClaw
Install method
Manual import
Extraction
Extract archive
Prerequisites
OpenClaw
Primary doc
SKILL.md

Package facts

Download mode
Yavira redirect
Package format
ZIP package
Source platform
Tencent SkillHub
What's included
README.md, SKILL.md, references/best-practices.md, references/examples.md, references/patterns.md

Validation

  • Use the Yavira download entry.
  • Review SKILL.md after the package is downloaded.
  • Confirm the extracted package contains the expected setup assets.

Install with your agent

Agent handoff

Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.

  1. Download the package from Yavira.
  2. Extract it into a folder your agent can access.
  3. Paste one of the prompts below and point your agent at the extracted folder.
New install

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.

Upgrade existing

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.

Trust & source

Release facts

Source
Tencent SkillHub
Verification
Indexed source record
Version
0.1.0

Documentation

ClawHub primary doc Primary doc: SKILL.md 14 sections Open source page

Command Creator

Slash commands are markdown files in .claude/commands/ (project) or ~/.claude/commands/ (global) that expand into prompts when invoked.

Command Structure

--- description: Brief description for /help (required) argument-hint: <required> or [optional] (if takes arguments) --- # Command Title [Instructions for agent to execute autonomously]

Step 1: Determine Location

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.

Step 2: Identify Pattern

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?"

Step 3: Gather Information

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?"

Step 4: Generate Command

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

Step 5: Create File

mkdir -p [directory-path] Write the command file. Report: File location What the command does How to use: /command-name [args]

Step 6: Test (Optional)

Suggest: "Test with /command-name [args]" Iterate based on feedback.

Writing Guidelines

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"

Workflow Automation

1. Check for .PLAN.md 2. Analyze git status/diff 3. Perform actions 4. Report results

Iterative Fixing

1. Run make all-ci (max 10 iterations) 2. Parse errors by category 3. Apply targeted fixes 4. Repeat until success or stuck

Agent Delegation

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.

Quality Checklist

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

NEVER

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

Category context

Code helpers, APIs, CLIs, browser automation, testing, and developer operations.

Source: Tencent SkillHub

Largest current source with strong distribution and engagement signals.

Package contents

Included in package
5 Docs
  • SKILL.md Primary doc
  • README.md Docs
  • references/best-practices.md Docs
  • references/examples.md Docs
  • references/patterns.md Docs