[Feature]: Add debugging-focused example to skill-reviewer agent

[sjnims]

Problem or Need

The skill-reviewer agent has exactly 3 examples (the minimum recommended), all focused on reviewing newly created or modified skills. A common user scenario is missing: debugging why a skill isn't triggering correctly.

Current examples:

1. "I've created a PDF processing skill" (proactive after creation)
2. "Review my skill and tell me how to improve it" (explicit review request)
3. "I updated the skill description, does it look good?" (description modification)

Users frequently encounter skill triggering issues and would benefit from the skill-reviewer agent being invoked for debugging scenarios.

Proposed Solution

Add a 4th example demonstrating the debugging/troubleshooting use case:

<example>
Context: User is having trouble with skill triggering
user: "My skill isn't being loaded when I ask about PDF processing"
assistant: "I'll use the skill-reviewer agent to analyze why the skill isn't triggering."
<commentary>
Skill triggering issue reported, trigger skill-reviewer to diagnose description and trigger phrase quality.
</commentary>
</example>

This extends the agent's coverage to include diagnostic scenarios, not just quality reviews.

Which component would this affect?

Agent

Specific Component

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

Alternatives Considered

• Could add to description trigger phrases instead of example (but examples are more effective for Claude)
• Could create a separate "skill-debugger" agent (but skill-reviewer's capabilities already cover this)

Additional Context

Found during comprehensive subagent review. The skill-reviewer agent is well-structured with:

• 8-step review process
• Clear output format
• Edge cases section

Adding this example would improve discoverability for debugging scenarios without changing the agent's core functionality.

Measurements:

• Current examples: 3 (minimum recommended)
• Recommended: 2-4
• File: 194 lines, 806 words, 6,079 chars
• System prompt: 636 words (lower end of 500-3,000 range, room to expand)

How important is this feature to you?

Medium - Would be nice to have

[sjnims]

PR submitted: #126