Creating Commands

Community

jiaxiaojunQAQ

creating-commands

Creates new Claude Code slash commands following best practices. Guides through command structure, naming, arguments, and frontmatter. Use when user wants to create a command, build a slash command, or asks about command best practices.

Overview

Publisher	jiaxiaojunQAQ
Repository	`SkillJect`
Skill name	`creating-commands`
Stars	79
Forks	8
Bundled files	5
Links	Skill source Repository

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
5 bundled files
Scripts, templates, and references the model can read while it works. Files are read-only and never executed.
Open source
Published by jiaxiaojunQAQ on GitHub. Read the source before you install it.

Installation

Install the Creating Commands AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
Enable the skill in any chat where you want it available.

Store

Installed

Skills

Add skills

Import one or more skills from a public GitHub folder or a local .skill or .zip archive, or SKILL.md file.

From GitHub URLFrom .skill, .zip, or SKILL.md

GitHub repo or folder

https://github.com/jiaxiaojunQAQ/SkillJect/tree/main/data/skills_sample/creating-commands

Points to a single skill folder, or any folder that contains multiple skills. Public repos only.

CancelContinue

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/jiaxiaojunQAQ/SkillJect.git /tmp/SkillJect
mkdir -p .claude/skills
cp -r /tmp/SkillJect/data/skills_sample/creating-commands .claude/skills/creating-commands

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Creating Commands in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Creating Commands on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Creating Commands is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Creating Commands

Guides creation of Claude Code slash commands using documented best practices.

Quick Start

For a new command:

Ask user for command purpose and arguments needed
Generate using appropriate template
Validate against checklist

For reviewing existing command:

Read command file
Check against anti-patterns in reference.md
Report issues with fixes

Workflow: Create New Command


Progress:
- [ ] Gather requirements (purpose, arguments, scope)
- [ ] Choose template (basic, with-args, workflow)
- [ ] Generate command file
- [ ] Validate against checklist

Step 1: Gather Requirements

Ask user with AskUserQuestion:

What should this command do? (purpose)
Does it need arguments? (none, single, multiple)
Project or personal? (scope)

Step 2: Choose Template

Type	Template	When to Use
Basic	templates/basic.md	No arguments, simple prompt
With Args	templates/with-args.md	Single or multiple arguments
Workflow	templates/workflow.md	Integrates with skills/agents

Step 3: Generate Command

Create in appropriate location:

.claude/commands/ - Project commands (git-tracked)
~/.claude/commands/ - Personal commands (your machine only)

Step 4: Validate

Run through checklist before finishing:


Validation Checklist:
- [ ] Name: lowercase with hyphens only
- [ ] Name: descriptive, verb-noun format preferred
- [ ] Description: explains what command does
- [ ] Arguments: documented with argument-hint if used
- [ ] Prompt: clear, actionable instructions
- [ ] Tools: allowed-tools declared if needed

Naming Rules

Format: verb-noun or action (lowercase, hyphens)

fix-issue
review-pr
run-tests
optimize

Constraints:

Lowercase letters, numbers, hyphens only
No spaces or underscores
Keep concise (1-3 words)

Command File Format

markdown
---
description: Brief explanation shown in help
allowed-tools:
  - Bash(bash:*)
  - WebSearch
argument-hint: "param_name"
---

Your command prompt here.
Use $ARGUMENTS for all args or $1, $2 for positional.

Argument Syntax

Syntax	Usage	Example
`$ARGUMENTS`	All arguments as one string	`/cmd foo bar` → `foo bar`
`$1`, `$2`	Positional arguments	`/cmd foo bar` → `$1=foo`, `$2=bar`
`@file`	Include file contents	`Review @src/main.ts`

Frontmatter Options

Field	Purpose	Required
`description`	Shown in help, enables auto-invoke	Recommended
`allowed-tools`	Tools the command can use	If using tools
`argument-hint`	Documents expected args	If has args
`model`	Specific model to use	Optional

Example: Basic Command

markdown
---
description: Run all tests and report failures
allowed-tools:
  - Bash(npm:*)
---

Run the test suite and summarize results:

1. Execute `npm test`
2. If failures, show failing tests with context
3. Suggest fixes for common issues

See reference.md for detailed best practices and anti-patterns.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Creating Commands AI skill do?

Why use Creating Commands on TypingMind?

Because you install it once and use it with any model. Creating Commands is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Creating Commands in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/jiaxiaojunQAQ/SkillJect/tree/main/data/skills_sample/creating-commands. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Creating Commands?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Creating Commands?

As many as you like. As long as a model supports skills, you can use Creating Commands with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Creating Commands AI skill free?

It is published on GitHub by jiaxiaojunQAQ. Check the repository for licensing terms. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Laravel Verification

affaan-m

CommunityPopular

Bucle de verificación para proyectos Laravel: verificaciones de entorno, linting, análisis estático, pruebas con cobertura, escaneos de seguridad y preparación para despliegue.

Brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

Executing Plans

Use when you have a written implementation plan to execute in a separate session with review checkpoints

Using Superpowers

Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Creating Commands

Quick Start

Workflow: Create New Command

Step 1: Gather Requirements

Step 2: Choose Template

Step 3: Generate Command

Step 4: Validate

Naming Rules

Command File Format

Argument Syntax

Frontmatter Options

Example: Basic Command

Bundled files

Frequently asked questions

Related AI Skills

Set up your own AI workspace now