fix(plugin-dev): correct tools format in agent/command examples

[lisaross]

Summary

• Fixes YAML parsing issue where JSON arrays in tools: and allowed-tools: fields are treated as literal strings
• Converts ["Read", "Write"] format to Read, Write (YAML comma-separated format)
• Updates 11 files in the plugin-dev plugin

Problem

The YAML parser interprets:

tools: ["Read", "Write"]

as the literal string ["Read", "Write"] instead of an array, causing agents and commands to receive zero tools silently.

Solution

Changed all instances to the correct YAML format:

tools: Read, Write

Files Changed

Actual frontmatter (causing silent failures):

• agents/agent-creator.md
• agents/plugin-validator.md
• agents/skill-reviewer.md
• commands/create-plugin.md
• skills/plugin-settings/examples/create-settings-command.md

Documentation examples (preventing users from copying incorrect patterns):

• skills/agent-development/SKILL.md
• skills/agent-development/examples/agent-creation-prompt.md
• skills/agent-development/examples/complete-agent-examples.md
• skills/mcp-integration/SKILL.md
• skills/mcp-integration/references/tool-usage.md
• skills/plugin-settings/SKILL.md

Test plan

• [ ] Verify agents receive correct tools after this change
• [ ] Check that allowed-tools in commands work as expected
• [ ] Confirm documentation examples now show correct format

Fixes #13331

🤖 Generated with Claude Code