How do I install the Claude Command skill?

Run npx skillmds@latest add emz1998/claude-command in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Claude Command safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Claude Command?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Claude Command free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Claude Command?

Emz1998 (@emz1998) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Claude Command by emz1998 — Agent Skill

Name: Claude Command
Rating: 4.666666666666667 (3 reviews)
Author: Emz1998

File contents

Goal: Create or update custom commands following template standards

IMPORTANT: Keep command content high-level and concise. Do not dive into implementation details.

Context

$0 =
$1 = or
$2 = (conditionally required)

Instructions

If `Action to be performed` is `create`

If command-name or instructions are not provided, then you should exit and ask the user to provide a command name and instructions.

Create a new command in the .claude/commands/ directory with the name of the command-name
Configure the command with the instructions provided by the user.
Validate the command.md file against the acceptance criteria and the template from .claude/skills/claude-command/templates/command.md.
Save the command.md file to the .claude/commands/command.md file.

If `Action to be performed` is `update`

If command-name or instructions are not provided, then you should exit and ask the user to provide a command name and instructions.

Update the existing command in the .claude/commands/ directory with the name of the command-name
Configure the command with the instructions provided by the user.
Re-validate the command.md file against the acceptance criteria and the template from .claude/skills/claude-command/templates/command.md.

If `Action to be performed` is `delete`

If command-name is not provided, then you should exit and ask the user to provide a command name.

Delete the existing command in the .claude/commands/ directory with the name of the command-name
Delete the command.md file from the .claude/commands/command.md file.

If `Action to be performed` is `list`

List all existing commands in the .claude/commands/ directory.

Note: Supporting files should be store within the command folder. E.g. .claude/commands/ Note: The folder name and the command name should be the same.

Workflow

Read the template from .claude/skills/claude-command/templates/command.md
Read skills-docs.md from .claude/skills/claude-command/references/skills-docs.md
Analyze user requirements and determine command location
Implement the task based on the instructions above.
Report completion with command details and location

Rules

DO NOT deviate from template structure (YAML frontmatter + all sections)
NEVER save commands outside .claude/commands/ directory
DO NOT grant excessive tool permissions - apply least-privilege
DO NOT skip validation step.

Acceptance Criteria

Command saved to correct location with complete YAML frontmatter
All template sections populated
Command saved to correct location with correct YAML frontmatter
Report delivered with command details and location

---name: claude-commanddescription: Use PROACTIVELY this skill when you need to create or update custom commands following best practices---**Goal**: Create or update custom commands following template standards**IMPORTANT**: Keep command content high-level and concise. Do not dive into implementation details.## Context- $0 = <action-to-be-performed>- $1 = <command-name> or <instructions>- $2 = <instructions> (conditionally required)## Instructions### If `Action to be performed` is `create`> If `command-name` or `instructions` are not provided, then you should exit and ask the user to provide a command name and instructions.- Create a new command in the `.claude/commands/` directory with the name of the `command-name`- Configure the command with the `instructions` provided by the user.- Validate the `command.md` file against the acceptance criteria and the template from `.claude/skills/claude-command/templates/command.md`.- Save the `command.md` file to the `.claude/commands/command.md` file.### If `Action to be performed` is `update`> If `command-name` or `instructions` are not provided, then you should exit and ask the user to provide a command name and instructions.- Update the existing command in the `.claude/commands/` directory with the name of the `command-name`- Configure the command with the `instructions` provided by the user.- Re-validate the `command.md` file against the acceptance criteria and the template from `.claude/skills/claude-command/templates/command.md`.### If `Action to be performed` is `delete`> If `command-name` is not provided, then you should exit and ask the user to provide a command name.- Delete the existing command in the `.claude/commands/` directory with the name of the `command-name`- Delete the `command.md` file from the `.claude/commands/command.md` file.### If `Action to be performed` is `list`- List all existing commands in the `.claude/commands/` directory.> **Note**: Supporting files should be store within the command folder. E.g. `.claude/commands/`> **Note**: The folder name and the command name should be the same.## Workflow1. Read the template from `.claude/skills/claude-command/templates/command.md`2. Read skills-docs.md from `.claude/skills/claude-command/references/skills-docs.md`3. Analyze user requirements and determine command location4. Implement the task based on the instructions above.5. Report completion with command details and location## Rules- DO NOT deviate from template structure (YAML frontmatter + all sections)- NEVER save commands outside `.claude/commands/` directory- DO NOT grant excessive tool permissions - apply least-privilege- DO NOT skip validation step.## Acceptance Criteria- Command saved to correct location with complete YAML frontmatter- All template sections populated- Command saved to correct location with correct YAML frontmatter- Report delivered with command details and location

Frequently asked questions

Claude Command