Fix YAML frontmatter parsing errors in agent description fields

Use YAML block scalars (|) for multi-line description fields that contain
<example> blocks with colons and special characters. Without block scalars,
the YAML parser fails because it interprets lines like 'user:' and
'assistant:' as new key-value pairs.

Affected files:
- plugins/plugin-dev/agents/agent-creator.md
- plugins/plugin-dev/agents/skill-reviewer.md
- plugins/plugin-dev/agents/plugin-validator.md
- plugins/pr-review-toolkit/agents/code-simplifier.md

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>
+  <example>
-Context: User wants to create a code review agent
+  Context: User wants to create a code review agent
-user: "Create an agent that reviews code for quality issues"
+  user: "Create an agent that reviews code for quality issues"
-assistant: "I'll use the agent-creator agent to generate the agent configuration."
+  assistant: "I'll use the agent-creator agent to generate the agent configuration."
-<commentary>
+  <commentary>
-User requesting new agent creation, trigger agent-creator to generate it.
+  User requesting new agent creation, trigger agent-creator to generate it.
-</commentary>
+  </commentary>
-</example>
+  </example>
 
-<example>
+  <example>
-Context: User describes needed functionality
+  Context: User describes needed functionality
-user: "I need an agent that generates unit tests for my code"
+  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."
+  assistant: "I'll use the agent-creator agent to create a test generation agent."
-<commentary>
+  <commentary>
-User describes agent need, trigger agent-creator to build it.
+  User describes agent need, trigger agent-creator to build it.
-</commentary>
+  </commentary>
-</example>
+  </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>
+  <example>
-Context: User finished creating a new plugin
+  Context: User finished creating a new plugin
-user: "I've created my first plugin with commands and hooks"
+  user: "I've created my first plugin with commands and hooks"
-assistant: "Great! Let me validate the plugin structure."
+  assistant: "Great! Let me validate the plugin structure."
-<commentary>
+  <commentary>
-Plugin created, proactively validate to catch issues early.
+  Plugin created, proactively validate to catch issues early.
-</commentary>
+  </commentary>
-assistant: "I'll use the plugin-validator agent to check the plugin."
+  assistant: "I'll use the plugin-validator agent to check the plugin."
-</example>
+  </example>
 
-<example>
+  <example>
-Context: User explicitly requests validation
+  Context: User explicitly requests validation
-user: "Validate my plugin before I publish it"
+  user: "Validate my plugin before I publish it"
-assistant: "I'll use the plugin-validator agent to perform comprehensive validation."
+  assistant: "I'll use the plugin-validator agent to perform comprehensive validation."
-<commentary>
+  <commentary>
-Explicit validation request triggers the agent.
+  Explicit validation request triggers the agent.
-</commentary>
+  </commentary>
-</example>
+  </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>
+  <example>
-Context: User just created a new skill
+  Context: User just created a new skill
-user: "I've created a PDF processing skill"
+  user: "I've created a PDF processing skill"
-assistant: "Great! Let me review the skill quality."
+  assistant: "Great! Let me review the skill quality."
-<commentary>
+  <commentary>
-Skill created, proactively trigger skill-reviewer to ensure it follows best practices.
+  Skill created, proactively trigger skill-reviewer to ensure it follows best practices.
-</commentary>
+  </commentary>
-assistant: "I'll use the skill-reviewer agent to review the skill."
+  assistant: "I'll use the skill-reviewer agent to review the skill."
-</example>
+  </example>
 
-<example>
+  <example>
-Context: User requests skill review
+  Context: User requests skill review
-user: "Review my skill and tell me how to improve it"
+  user: "Review my skill and tell me how to improve it"
-assistant: "I'll use the skill-reviewer agent to analyze the skill quality."
+  assistant: "I'll use the skill-reviewer agent to analyze the skill quality."
-<commentary>
+  <commentary>
-Explicit skill review request triggers the agent.
+  Explicit skill review request triggers the agent.
-</commentary>
+  </commentary>
-</example>
+  </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/pr-review-toolkit/agents/code-simplifier.md

@@ -1,37 +1,42 @@
 ---
 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.\n\nExamples:\n\n<example>
+description: |
-Context: The assistant has just implemented a new feature that adds user authentication to an API endpoint.
+  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.
-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>
+  Examples:
-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>
+  <example>
-Context: The assistant has just refactored a function to improve performance.
+  Context: The assistant has just implemented a new feature that adds user authentication to an API endpoint.
-user: "Optimize the data sorting algorithm for better performance"
+  user: "Please add authentication to the /api/users endpoint"
-assistant: "I've optimized the sorting algorithm. Here's the updated implementation:"
+  assistant: "I've implemented the authentication for the /api/users endpoint. Here's the code:"
-<function call omitted for brevity>
+  <function call omitted for brevity>
-<commentary>
+  <commentary>
-After completing a performance optimization task, use the code-simplifier agent to ensure the optimized code is also clear and maintainable.
+  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>
+  </commentary>
-assistant: "Now I'll use the code-simplifier agent to ensure the optimized code is also clear and follows our coding standards"
+  assistant: "Now let me use the code-simplifier agent to refine this implementation for better clarity and maintainability"
-</example>
+  </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>
 model: opus
 ---