feat: strengthen agent-development skill trigger phrases

[sjnims]

Summary

Update the agent-development skill description to use natural query-style trigger phrases instead of fragments for improved skill discovery and activation.

Problem

Fixes #10

The current trigger phrases include fragments that don't match how users naturally ask questions:

• "agent frontmatter" - fragment, not a question
• "agent tools" - fragment
• "agent colors" - fragment

Solution

Replace fragments with natural user queries that improve skill triggering:

• "agent frontmatter" → "what are the agent frontmatter fields"
• "agent tools" → "how to restrict agent tools"
• "agent colors" → "what colors can agents use"

Added new trigger phrases covering common user intents:

• "design an agent for [task]"
• "how do I write agent descriptions"
• "validate my agent"
• "test agent triggering"

Changes

• plugins/plugin-dev/skills/agent-development/SKILL.md: Updated description field with natural query-style trigger phrases

Testing

• Linting passes
• Description follows established patterns from other skills

---

🤖 Generated with Claude Code

[claude]

Claude finished @sjnims's task —— View job

---

PR Review Complete ✅

Summary

Looks good - This PR successfully improves the agent-development skill's trigger phrases by converting fragments into natural user queries.

---

What's Good

✅ Natural query patterns: The new trigger phrases match how users actually ask questions:

• "what are the agent frontmatter fields" (instead of "agent frontmatter")
• "how to restrict agent tools" (instead of "agent tools")
• "what colors can agents use" (instead of "agent colors")

✅ Intent-based triggers added: New phrases capture common user intents:

• "design an agent for [task]" - proactive design help
• "how do I write agent descriptions" - guidance seeking
• "validate my agent" - quality assurance
• "test agent triggering" - development workflow

✅ Consistency with other skills: The pattern follows established conventions from skill-development and command-development skills:

skill-development: "create a skill", "improve skill description", "validate skill"
command-development: "create a slash command", "use command frontmatter", "organize commands"
agent-development: "create an agent", "write agent descriptions", "validate my agent" ✓

✅ Markdown quality: No linting issues - file passes markdownlint validation

✅ Minimal, focused change: Single line update (+1/-1) keeps the PR scope tight and reviewable

---

Checklist Verification

• YAML frontmatter valid: name, description, version fields present and correct
• Trigger phrases updated: Fragments replaced with natural queries
• Pattern consistency: Follows established skill description patterns
• Markdown linting: Passes markdownlint --config .markdownlint.json
• Version unchanged: Correctly kept at 0.1.0 (trigger phrase improvements don't require version bump)

---

Technical Analysis

Changed line (plugins/plugin-dev/skills/agent-development/SKILL.md:3):

Before:

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...

After:

description: This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "design an agent for [task]", "how do I write agent descriptions", "what are the agent frontmatter fields", "validate my agent", "test agent triggering", "how to restrict agent tools", "what colors can agents use", "autonomous agent", or needs guidance...

Improvements:

1. Fragments → Questions: More natural language matching
2. Added workflow triggers: "validate my agent", "test agent triggering"
3. Better specificity: "what are the agent frontmatter fields" vs "agent frontmatter"
4. Intent capture: "design an agent for [task]" catches proactive requests

This change should improve skill discovery when users ask natural questions about agents.

---