command-builder

Slash commands are defined using YAML frontmatter that specifies descriptions, arguments, and tool permissions. The command-builder Skill automates this structure, enforcing required fields, quoted strings, and proper delimiters so your commands are valid and reusable across workflows.

Yes. Commands support dynamic arguments via `$ARGUMENTS` or positional parameters (`$1-$N`), and can inject file contents using `@path` syntax or shell command outputs with `!command`. This lets you build commands that read files and process data in a single invocation.

The command-builder Skill streamlines command authoring by enforcing YAML structure, argument handling patterns, and tool scoping rules. It eliminates manual formatting, reduces errors, and ensures consistency across all your custom commands.

Commands declare allowed tools in their YAML frontmatter using scoped permissions. The command-builder Skill manages this configuration, ensuring only necessary tools are granted and preventing invalid tool assignments in your command definition.

Slash commands cannot mix `$ARGUMENTS` with positional parameters (`$1-$N`) — the command-builder Skill enforces this constraint. Choose one argument style per command and keep command logic under 125 lines of code to maintain clarity and avoid execution failures.

Yes. The command-builder Skill supports namespace organization within YAML frontmatter, letting you group related commands logically. This keeps your command suite structured and discoverable as your automation workflows grow.