Use lower-kebab-case for SKILL.md names in hookify and plugin-dev

Skills and commands are now merged, so SKILL.md name fields surface
in the UI as slash commands. Upper Space names like 'Hook Development'
become '/Hook Development', which doesn't work since user-invoked
commands don't support spaces.

Rename all affected SKILL.md name fields to lower-kebab-case:
- hookify: Writing Hookify Rules -> writing-hookify-rules
- plugin-dev: Agent Development -> agent-development
- plugin-dev: Command Development -> command-development
- plugin-dev: Hook Development -> hook-development
- plugin-dev: MCP Integration -> mcp-integration
- plugin-dev: Plugin Settings -> plugin-settings
- plugin-dev: Plugin Structure -> plugin-structure
- plugin-dev: Skill Development -> skill-development

Also update references in plugin-dev/README.md.

plugins/hookify/skills/writing-rules/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: Writing Hookify Rules
+name: writing-hookify-rules
 description: This skill should be used when the user asks to "create a hookify rule", "write a hook rule", "configure hookify", "add a hookify rule", or needs guidance on hookify rule syntax and patterns.
 version: 0.1.0
 ---

plugins/plugin-dev/README.md

@@ -6,13 +6,13 @@ A comprehensive toolkit for developing Claude Code plugins with expert guidance
 
 The plugin-dev toolkit provides seven specialized skills to help you build high-quality Claude Code plugins:
 
-1. **Hook Development** - Advanced hooks API and event-driven automation
-2. **MCP Integration** - Model Context Protocol server integration
-3. **Plugin Structure** - Plugin organization and manifest configuration
-4. **Plugin Settings** - Configuration patterns using .claude/plugin-name.local.md files
-5. **Command Development** - Creating slash commands with frontmatter and arguments
-6. **Agent Development** - Creating autonomous agents with AI-assisted generation
-7. **Skill Development** - Creating skills with progressive disclosure and strong triggers
+1. **hook-development** - Advanced hooks API and event-driven automation
+2. **mcp-integration** - Model Context Protocol server integration
+3. **plugin-structure** - Plugin organization and manifest configuration
+4. **plugin-settings** - Configuration patterns using .claude/plugin-name.local.md files
+5. **command-development** - Creating slash commands with frontmatter and arguments
+6. **agent-development** - Creating autonomous agents with AI-assisted generation
+7. **skill-development** - Creating skills with progressive disclosure and strong triggers
 
 Each skill follows best practices with progressive disclosure: lean core documentation, detailed references, working examples, and utility scripts.
 
@@ -53,7 +53,7 @@ Use this workflow for structured, high-quality plugin development from concept t
 
 ## Skills
 
-### 1. Hook Development
+### 1. hook-development
 
 **Trigger phrases:** "create a hook", "add a PreToolUse hook", "validate tool use", "implement prompt-based hooks", "${CLAUDE_PLUGIN_ROOT}", "block dangerous commands"
 
@@ -73,7 +73,7 @@ Use this workflow for structured, high-quality plugin development from concept t
 
 **Use when:** Creating event-driven automation, validating operations, or enforcing policies in your plugin.
 
-### 2. MCP Integration
+### 2. mcp-integration
 
 **Trigger phrases:** "add MCP server", "integrate MCP", "configure .mcp.json", "Model Context Protocol", "stdio/SSE/HTTP server", "connect external service"
 
@@ -92,7 +92,7 @@ Use this workflow for structured, high-quality plugin development from concept t
 
 **Use when:** Integrating external services, APIs, databases, or tools into your plugin.
 
-### 3. Plugin Structure
+### 3. plugin-structure
 
 **Trigger phrases:** "plugin structure", "plugin.json manifest", "auto-discovery", "component organization", "plugin directory layout"
 
@@ -111,7 +111,7 @@ Use this workflow for structured, high-quality plugin development from concept t
 
 **Use when:** Starting a new plugin, organizing components, or configuring the plugin manifest.
 
-### 4. Plugin Settings
+### 4. plugin-settings
 
 **Trigger phrases:** "plugin settings", "store plugin configuration", ".local.md files", "plugin state files", "read YAML frontmatter", "per-project plugin settings"
 
@@ -132,7 +132,7 @@ Use this workflow for structured, high-quality plugin development from concept t
 
 **Use when:** Making plugins configurable, storing per-project state, or implementing user preferences.
 
-### 5. Command Development
+### 5. command-development
 
 **Trigger phrases:** "create a slash command", "add a command", "command frontmatter", "define command arguments", "organize commands"
 
@@ -151,7 +151,7 @@ Use this workflow for structured, high-quality plugin development from concept t
 
 **Use when:** Creating slash commands, defining command arguments, or organizing plugin commands.
 
-### 6. Agent Development
+### 6. agent-development
 
 **Trigger phrases:** "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "autonomous agent"
 
@@ -172,7 +172,7 @@ Use this workflow for structured, high-quality plugin development from concept t
 
 **Use when:** Creating autonomous agents, defining agent behavior, or implementing AI-assisted agent generation.
 
-### 7. Skill Development
+### 7. skill-development
 
 **Trigger phrases:** "create a skill", "add a skill to plugin", "write a new skill", "improve skill description", "organize skill content"
 
@@ -286,11 +286,11 @@ The hook-development skill includes production-ready utilities:
 ### Working Examples
 
 Every skill provides working examples:
-- **Hook Development**: 3 complete hook scripts (bash, write validation, context loading)
-- **MCP Integration**: 3 server configurations (stdio, SSE, HTTP)
-- **Plugin Structure**: 3 plugin layouts (minimal, standard, advanced)
-- **Plugin Settings**: 3 examples (read-settings hook, create-settings command, templates)
-- **Command Development**: 10 complete command examples (review, test, deploy, docs, etc.)
+- **hook-development**: 3 complete hook scripts (bash, write validation, context loading)
+- **mcp-integration**: 3 server configurations (stdio, SSE, HTTP)
+- **plugin-structure**: 3 plugin layouts (minimal, standard, advanced)
+- **plugin-settings**: 3 examples (read-settings hook, create-settings command, templates)
+- **command-development**: 10 complete command examples (review, test, deploy, docs, etc.)
 
 ## Documentation Standards
 

plugins/plugin-dev/agents/agent-creator.md

@@ -1,34 +1,34 @@
 ---
 name: agent-creator
-description: |
-  Use this agent when the user asks to "create an agent", "generate an agent", "build a new agent", "make me an agent that...", or describes agent functionality they need. Trigger when user wants to create autonomous agents for plugins. Examples:
+description: Use this agent when the user asks to "create an agent", "generate an agent", "build a new agent", "make me an agent that...", or describes agent functionality they need. Trigger when user wants to create autonomous agents for plugins. Examples:
 
-  <example>
-  Context: User wants to create a code review agent
-  user: "Create an agent that reviews code for quality issues"
-  assistant: "I'll use the agent-creator agent to generate the agent configuration."
-  <commentary>
-  User requesting new agent creation, trigger agent-creator to generate it.
-  </commentary>
-  </example>
+<example>
+Context: User wants to create a code review agent
+user: "Create an agent that reviews code for quality issues"
+assistant: "I'll use the agent-creator agent to generate the agent configuration."
+<commentary>
+User requesting new agent creation, trigger agent-creator to generate it.
+</commentary>
+</example>
 
-  <example>
-  Context: User describes needed functionality
-  user: "I need an agent that generates unit tests for my code"
-  assistant: "I'll use the agent-creator agent to create a test generation agent."
-  <commentary>
-  User describes agent need, trigger agent-creator to build it.
-  </commentary>
-  </example>
+<example>
+Context: User describes needed functionality
+user: "I need an agent that generates unit tests for my code"
+assistant: "I'll use the agent-creator agent to create a test generation agent."
+<commentary>
+User describes agent need, trigger agent-creator to build it.
+</commentary>
+</example>
+
+<example>
+Context: User wants to add agent to plugin
+user: "Add an agent to my plugin that validates configurations"
+assistant: "I'll use the agent-creator agent to generate a configuration validator agent."
+<commentary>
+Plugin development with agent addition, trigger agent-creator.
+</commentary>
+</example>
 
-  <example>
-  Context: User wants to add agent to plugin
-  user: "Add an agent to my plugin that validates configurations"
-  assistant: "I'll use the agent-creator agent to generate a configuration validator agent."
-  <commentary>
-  Plugin development with agent addition, trigger agent-creator.
-  </commentary>
-  </example>
 model: sonnet
 color: magenta
 tools: ["Write", "Read"]

plugins/plugin-dev/agents/plugin-validator.md

@@ -1,36 +1,36 @@
 ---
 name: plugin-validator
-description: |
-  Use this agent when the user asks to "validate my plugin", "check plugin structure", "verify plugin is correct", "validate plugin.json", "check plugin files", or mentions plugin validation. Also trigger proactively after user creates or modifies plugin components. Examples:
+description: Use this agent when the user asks to "validate my plugin", "check plugin structure", "verify plugin is correct", "validate plugin.json", "check plugin files", or mentions plugin validation. Also trigger proactively after user creates or modifies plugin components. Examples:
 
-  <example>
-  Context: User finished creating a new plugin
-  user: "I've created my first plugin with commands and hooks"
-  assistant: "Great! Let me validate the plugin structure."
-  <commentary>
-  Plugin created, proactively validate to catch issues early.
-  </commentary>
-  assistant: "I'll use the plugin-validator agent to check the plugin."
-  </example>
+<example>
+Context: User finished creating a new plugin
+user: "I've created my first plugin with commands and hooks"
+assistant: "Great! Let me validate the plugin structure."
+<commentary>
+Plugin created, proactively validate to catch issues early.
+</commentary>
+assistant: "I'll use the plugin-validator agent to check the plugin."
+</example>
 
-  <example>
-  Context: User explicitly requests validation
-  user: "Validate my plugin before I publish it"
-  assistant: "I'll use the plugin-validator agent to perform comprehensive validation."
-  <commentary>
-  Explicit validation request triggers the agent.
-  </commentary>
-  </example>
+<example>
+Context: User explicitly requests validation
+user: "Validate my plugin before I publish it"
+assistant: "I'll use the plugin-validator agent to perform comprehensive validation."
+<commentary>
+Explicit validation request triggers the agent.
+</commentary>
+</example>
+
+<example>
+Context: User modified plugin.json
+user: "I've updated the plugin manifest"
+assistant: "Let me validate the changes."
+<commentary>
+Manifest modified, validate to ensure correctness.
+</commentary>
+assistant: "I'll use the plugin-validator agent to check the manifest."
+</example>
 
-  <example>
-  Context: User modified plugin.json
-  user: "I've updated the plugin manifest"
-  assistant: "Let me validate the changes."
-  <commentary>
-  Manifest modified, validate to ensure correctness.
-  </commentary>
-  assistant: "I'll use the plugin-validator agent to check the manifest."
-  </example>
 model: inherit
 color: yellow
 tools: ["Read", "Grep", "Glob", "Bash"]

plugins/plugin-dev/agents/skill-reviewer.md

@@ -1,35 +1,35 @@
 ---
 name: skill-reviewer
-description: |
-  Use this agent when the user has created or modified a skill and needs quality review, asks to "review my skill", "check skill quality", "improve skill description", or wants to ensure skill follows best practices. Trigger proactively after skill creation. Examples:
+description: Use this agent when the user has created or modified a skill and needs quality review, asks to "review my skill", "check skill quality", "improve skill description", or wants to ensure skill follows best practices. Trigger proactively after skill creation. Examples:
 
-  <example>
-  Context: User just created a new skill
-  user: "I've created a PDF processing skill"
-  assistant: "Great! Let me review the skill quality."
-  <commentary>
-  Skill created, proactively trigger skill-reviewer to ensure it follows best practices.
-  </commentary>
-  assistant: "I'll use the skill-reviewer agent to review the skill."
-  </example>
+<example>
+Context: User just created a new skill
+user: "I've created a PDF processing skill"
+assistant: "Great! Let me review the skill quality."
+<commentary>
+Skill created, proactively trigger skill-reviewer to ensure it follows best practices.
+</commentary>
+assistant: "I'll use the skill-reviewer agent to review the skill."
+</example>
 
-  <example>
-  Context: User requests skill review
-  user: "Review my skill and tell me how to improve it"
-  assistant: "I'll use the skill-reviewer agent to analyze the skill quality."
-  <commentary>
-  Explicit skill review request triggers the agent.
-  </commentary>
-  </example>
+<example>
+Context: User requests skill review
+user: "Review my skill and tell me how to improve it"
+assistant: "I'll use the skill-reviewer agent to analyze the skill quality."
+<commentary>
+Explicit skill review request triggers the agent.
+</commentary>
+</example>
+
+<example>
+Context: User modified skill description
+user: "I updated the skill description, does it look good?"
+assistant: "I'll use the skill-reviewer agent to review the changes."
+<commentary>
+Skill description modified, review for triggering effectiveness.
+</commentary>
+</example>
 
-  <example>
-  Context: User modified skill description
-  user: "I updated the skill description, does it look good?"
-  assistant: "I'll use the skill-reviewer agent to review the changes."
-  <commentary>
-  Skill description modified, review for triggering effectiveness.
-  </commentary>
-  </example>
 model: inherit
 color: cyan
 tools: ["Read", "Grep", "Glob"]

plugins/plugin-dev/skills/agent-development/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: Agent Development
+name: agent-development
 description: This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.
 version: 0.1.0
 ---

plugins/plugin-dev/skills/command-development/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: Command Development
+name: command-development
 description: This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
 version: 0.2.0
 ---

plugins/plugin-dev/skills/hook-development/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: Hook Development
+name: hook-development
 description: This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.
 version: 0.1.0
 ---

plugins/plugin-dev/skills/mcp-integration/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: MCP Integration
+name: mcp-integration
 description: This skill should be used when the user asks to "add MCP server", "integrate MCP", "configure MCP in plugin", "use .mcp.json", "set up Model Context Protocol", "connect external service", mentions "${CLAUDE_PLUGIN_ROOT} with MCP", or discusses MCP server types (SSE, stdio, HTTP, WebSocket). Provides comprehensive guidance for integrating Model Context Protocol servers into Claude Code plugins for external tool and service integration.
 version: 0.1.0
 ---

plugins/plugin-dev/skills/plugin-settings/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: Plugin Settings
+name: plugin-settings
 description: This skill should be used when the user asks about "plugin settings", "store plugin configuration", "user-configurable plugin", ".local.md files", "plugin state files", "read YAML frontmatter", "per-project plugin settings", or wants to make plugin behavior configurable. Documents the .claude/plugin-name.local.md pattern for storing plugin-specific configuration with YAML frontmatter and markdown content.
 version: 0.1.0
 ---

plugins/plugin-dev/skills/plugin-structure/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: Plugin Structure
+name: plugin-structure
 description: This skill should be used when the user asks to "create a plugin", "scaffold a plugin", "understand plugin structure", "organize plugin components", "set up plugin.json", "use ${CLAUDE_PLUGIN_ROOT}", "add commands/agents/skills/hooks", "configure auto-discovery", or needs guidance on plugin directory layout, manifest configuration, component organization, file naming conventions, or Claude Code plugin architecture best practices.
 version: 0.1.0
 ---

plugins/plugin-dev/skills/skill-development/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: Skill Development
+name: skill-development
 description: This skill should be used when the user wants to "create a skill", "add a skill to plugin", "write a new skill", "improve skill description", "organize skill content", or needs guidance on skill structure, progressive disclosure, or skill development best practices for Claude Code plugins.
 version: 0.1.0
 ---

plugins/pr-review-toolkit/agents/code-simplifier.md

@@ -1,42 +1,37 @@
 ---
 name: code-simplifier
-description: |
-  Use this agent when code has been written or modified and needs to be simplified for clarity, consistency, and maintainability while preserving all functionality. This agent should be triggered automatically after completing a coding task or writing a logical chunk of code. It simplifies code by following project best practices while retaining all functionality. The agent focuses only on recently modified code unless instructed otherwise.
+description: Use this agent when code has been written or modified and needs to be simplified for clarity, consistency, and maintainability while preserving all functionality. This agent should be triggered automatically after completing a coding task or writing a logical chunk of code. It simplifies code by following project best practices while retaining all functionality. The agent focuses only on recently modified code unless instructed otherwise.\n\nExamples:\n\n<example>
+Context: The assistant has just implemented a new feature that adds user authentication to an API endpoint.
+user: "Please add authentication to the /api/users endpoint"
+assistant: "I've implemented the authentication for the /api/users endpoint. Here's the code:"
+<function call omitted for brevity>
+<commentary>
+Since a logical chunk of code has been written (authentication feature), use the Task tool to launch the code-simplifier agent to improve the code's clarity and maintainability while preserving functionality.
+</commentary>
+assistant: "Now let me use the code-simplifier agent to refine this implementation for better clarity and maintainability"
+</example>
 
-  Examples:
+<example>
+Context: The assistant has just fixed a bug by adding several conditional checks.
+user: "Fix the null pointer exception in the data processor"
+assistant: "I've added the necessary null checks to prevent the exception:"
+<function call omitted for brevity>
+<commentary>
+After modifying code to fix a bug, use the code-simplifier agent to ensure the fix follows best practices and maintains code quality.
+</commentary>
+assistant: "Let me refine this bug fix using the code-simplifier agent to ensure it follows our best practices"
+</example>
 
-  <example>
-  Context: The assistant has just implemented a new feature that adds user authentication to an API endpoint.
-  user: "Please add authentication to the /api/users endpoint"
-  assistant: "I've implemented the authentication for the /api/users endpoint. Here's the code:"
-  <function call omitted for brevity>
-  <commentary>
-  Since a logical chunk of code has been written (authentication feature), use the Task tool to launch the code-simplifier agent to improve the code's clarity and maintainability while preserving functionality.
-  </commentary>
-  assistant: "Now let me use the code-simplifier agent to refine this implementation for better clarity and maintainability"
-  </example>
-
-  <example>
-  Context: The assistant has just fixed a bug by adding several conditional checks.
-  user: "Fix the null pointer exception in the data processor"
-  assistant: "I've added the necessary null checks to prevent the exception:"
-  <function call omitted for brevity>
-  <commentary>
-  After modifying code to fix a bug, use the code-simplifier agent to ensure the fix follows best practices and maintains code quality.
-  </commentary>
-  assistant: "Let me refine this bug fix using the code-simplifier agent to ensure it follows our best practices"
-  </example>
-
-  <example>
-  Context: The assistant has just refactored a function to improve performance.
-  user: "Optimize the data sorting algorithm for better performance"
-  assistant: "I've optimized the sorting algorithm. Here's the updated implementation:"
-  <function call omitted for brevity>
-  <commentary>
-  After completing a performance optimization task, use the code-simplifier agent to ensure the optimized code is also clear and maintainable.
-  </commentary>
-  assistant: "Now I'll use the code-simplifier agent to ensure the optimized code is also clear and follows our coding standards"
-  </example>
+<example>
+Context: The assistant has just refactored a function to improve performance.
+user: "Optimize the data sorting algorithm for better performance"
+assistant: "I've optimized the sorting algorithm. Here's the updated implementation:"
+<function call omitted for brevity>
+<commentary>
+After completing a performance optimization task, use the code-simplifier agent to ensure the optimized code is also clear and maintainable.
+</commentary>
+assistant: "Now I'll use the code-simplifier agent to ensure the optimized code is also clear and follows our coding standards"
+</example>
 model: opus
 ---