What problem does it solve? Drafting replies to GitHub issues and discussions often produces robotic, corporate-sounding text that alienates community members. This Skill enforces a consistent, human-sounding tone across all external-facing responses. ## Core Features & Use Cases - Tone Pattern Library: Provides 13 concrete patterns covering warm openings, active voice, empathy markers, and action-oriented closes. - Ready-Made Templates: Includes seven response templates for welcomes, troubleshooting, feature guidance, redirects, acknowledgments, closings, and technical uncertainty. - Anti-Pattern Guardrails: Lists explicit phrases to avoid, such as corporate speak, passive voice, link-dumping, and over-promising. - Use Case: When a maintainer drafts a reply to a bug report, apply these patterns to produce a response like "Thanks for the detailed report! Here's what we think is happening..." instead of "This is being investigated." ## Quick Start Rewrite my draft reply to this GitHub issue so it sounds warm, direct, and human using the humanizer tone patterns.