feat: add debugging-focused example to skill-reviewer agent

[sjnims]

Summary

Add a 4th example to the skill-reviewer agent demonstrating the troubleshooting use case when users report skills not triggering correctly.

Problem

Fixes #122

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

Solution

Added a new example demonstrating the debugging/diagnostic scenario:

<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 without changing its core functionality.

Alternatives Considered

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

Changes

• plugins/plugin-dev/agents/skill-reviewer.md: Added 4th example for debugging scenario

Testing

• Linting passes
• Example follows existing pattern

---

🤖 Generated with Claude Code

[claude]

Claude finished @sjnims's task in 1m 21s —— View job

---

PR Review: Add debugging example to skill-reviewer agent

Summary

✅ Looks good - This PR successfully addresses issue #122 by adding a relevant debugging example that complements the existing agent examples without changing core functionality.

---

What's Good

1. Addresses Real User Need: The new example fills an important gap by demonstrating the debugging/troubleshooting scenario when skills don't trigger correctly - a common user pain point.

2. Follows Existing Pattern: The 4th example maintains perfect consistency with the existing 3 examples:

   • Uses the same <example> structure
   • Includes Context:, user/assistant dialogue, and <commentary> sections
   • Commentary explains triggering logic clearly
   • Matches the writing style and level of detail

3. Quality Implementation:

   • Example is realistic ("My skill isn't being loaded when I ask about PDF processing")
   • Agent response is appropriate and clear
   • Commentary correctly identifies the trigger scenario
   • Doesn't require any agent functionality changes

4. Technical Correctness:

   • ✅ Markdown linting passes (no issues found)
   • Frontmatter remains valid
   • No syntax or formatting issues
   • Agent description already mentions this scenario should trigger the agent

5. Strategic Placement: Added after the 3 existing examples but before the model/color/tools fields, maintaining logical frontmatter structure.

---

Review Against Agent Criteria

Agent Structure ✅

• YAML frontmatter: Valid and unchanged
• Required fields present: name, description, model, color
• Optional fields appropriate: tools, skills
• <example> blocks: Now 4 examples (above recommended minimum of 3)

Example Quality ✅

• Context is clear and specific
• User query is realistic and common
• Assistant response is appropriate
• Commentary explains trigger logic
• Demonstrates distinct use case from other examples

Trigger Coverage

• Example 1: Proactive after creation ✅
• Example 2: Explicit review request ✅
• Example 3: Description modification review ✅
• Example 4: Debugging/troubleshooting (NEW) ✅

Tool Restrictions ✅

• Maintains read-only tools: Read, Grep, Glob (appropriate for reviewer)

---

Markdown Linting

✅ No issues found - markdownlint passed with no errors or warnings.

---

Checklist Verification

Based on PR description:

• Fixes [Feature]: Add debugging-focused example to skill-reviewer agent #122 - Addresses missing debugging scenario
• Example follows existing pattern - Perfect consistency maintained
• Linting passes - Confirmed via markdownlint
• No core functionality changes - Only adds example
• Extends agent coverage - Adds diagnostic scenario

---

Minor Observations (Not Issues)

1. Example Count: With 4 examples, this agent now has more examples than the recommended minimum (3). This is perfectly fine and beneficial for comprehensive trigger coverage.

2. Description Field: The agent's description field already broadly covers this scenario ("needs quality review"), so this example reinforces existing trigger intent rather than expanding it. This is good - it makes the debugging use case more explicit without requiring description changes.

---

Overall Assessment

Approved - This is a well-executed, focused PR that:

• Solves a real user problem (skill triggering issues)
• Maintains code quality and consistency
• Requires no documentation updates (scope is clear)
• Adds value without complexity

The PR is ready to merge.

---