plugin-slash-command_skill

Overview

This skill generates new Navigator slash commands following established project conventions so you get consistent, ready-to-use command files. It collects command requirements, analyzes similar commands, builds a markdown command file with validated YAML frontmatter, and shows usage examples and next steps.

How this skill works

I prompt for the command name (kebab-case), one-line purpose, complexity (simple|medium|complex), and whether it is user-facing or internal. I scan existing Navigator commands for structure and tone patterns, then compose a markdown file with the appropriate sections. Finally I validate YAML frontmatter, formatting, and examples, and present a summarized usage card with the file path and test instructions.

When to use it

• When you say: “add slash command”, “create command”, “new /nav command”, or “add /nav:[name] command”.
• When you need a consistent markdown command file that matches Navigator style and structure.
• When adding user-facing features that require a documented slash command.
• When creating internal maintenance commands for plugin development.
• When you want automated YAML frontmatter validation and example usage output.

Best practices

• Use kebab-case for the command name and keep the description to one clear, action-oriented sentence.
• Choose complexity honestly: simple for single-step actions, medium for multi-step flows, complex for multi-phase/integrations.
• Write examples with real file paths and realistic outputs to make testing straightforward.
• Keep tone conversational and second-person; use emojis sparingly to match existing commands.
• Run the provided YAML validator and manually test the command in Claude Code before publishing.

Example use cases

• Create /nav:version — a simple informational command that prints plugin and system versions.
• Add /nav:archive-tasks — a medium command to move completed task docs to an archive folder with validation.
• Generate /nav:init — a complex setup command that runs pre-flight checks, config migration, and integration hooks.
• Add internal /nav:cleanup — maintenance command to remove stale temp files used by the plugin.