# Create Slash Command Workflows

Teams need consistent slash commands that route micro-skills without confusing syntax. This skill guides command design, validation, handler generation, testing, documentation, and deployment steps.

## Install

```bash
npx skillstore add dnyoussef/when-creating-slash-commands-use-slash-command-encoder
```

## Metadata

- Status: approved
- Slug: dnyoussef-when-creating-slash-commands-use-slash-command-encoder
- Version: 1.0.0
- Author version: 1.0.0
- Skillstore revision: r1
- Version status: valid
- Tree hash: 53e828d03f134646b6f3cae796202183d67c7b268856383de87170b3fca9f88d
- Author: DNYoussef
- GitHub username: DNYoussef
- License: MIT
- Repository: https://github.com/DNYoussef/ai-chrome-extension/tree/main/.claude/skills/workflow/when-creating-slash-commands-use-slash-command-encoder
- Ref: c579efd02184f1128d6741d16e6c8d951d7d4208
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: confirmation\_required
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands, filesystem
- Quality score: 38
- Quality tier: warning
- Public page: https://skillstore.pages.dev/skills/dnyoussef-when-creating-slash-commands-use-slash-command-encoder
- Manifest: https://skillstore.pages.dev/api/skills/dnyoussef-when-creating-slash-commands-use-slash-command-encoder/manifest

## Capabilities

- Defines slash command names, aliases, parameters, flags, and examples.
- Shows how to generate command schemas and handler templates.
- Adds parameter validation, routing logic, and error handling patterns.
- Defines test steps for registration, validation, errors, and integration behavior.
- Creates documentation, help text, command catalogs, and usage examples.
- Covers build, install, registry, and shell completion deployment steps.

## Use Cases

- Standardize Project Commands: Create repeatable slash command patterns for code analysis, testing, and documentation tasks.
- Generate Command Handlers: Plan handler structure, validation rules, routing targets, and error behavior before implementation.
- Prepare Command Documentation: Produce command help text, usage examples, and command catalogs for team adoption.

## Prompt Templates

### Define a Basic Command

```
Use this skill to design a slash command for [task]. Include the command name, required parameters, optional flags, and two examples.
```

### Add Validation Rules

```
Use this skill to create validation rules for [command]. Check required inputs, allowed ranges, default values, and helpful error messages.
```

### Generate and Test a Handler

```
Use this skill to outline a handler for [command]. Include routing, parameter validation, test cases, and expected failure cases.
```

### Build a Command Suite

```
Use this skill to plan a slash command suite for [workflow]. Include command chaining, registry updates, documentation, deployment steps, and review gates.
```

## Limitations

- The examples depend on Claude Flow commands and may need adaptation.
- The skill does not audit generated command code for production security.
- Global installation and shell completion steps require manual review.
- It provides workflow guidance, not a complete command framework.

## Best Practices

- Confirm every shell command before running it in a real project.
- Keep command names short, specific, and consistent with existing workflows.
- Validate required inputs and document failure messages before deployment.

## Anti Patterns

- Installing generated commands globally before reviewing their contents.
- Using broad command names that hide what the command does.
- Skipping tests for required parameters, invalid paths, and expected errors.

## Security Audit

- Audited at: 2026-07-05T12:18:45.098\+00:00
- Summary: Most static backtick findings are Markdown fences, slash-command examples, or JavaScript template literals and are false positives. Real risk remains where the skill instructs agents to run npx claude-flow@alpha, install command bundles globally, and write shell completion files under the home directory. No evidence found for prompt injection or data exfiltration intent.

## Stats

- Views: 176
- Downloads: 6
- Favorites: 0
- Popularity score: 0