Rewrite community responses into warm, human-sounding language.
npx skills add https://github.com/sachinnair90/gitgloss --skill humanizer-sachinnair90
Please help me install this Agent Skill. Skill: humanizer Source: https://github.com/sachinnair90/gitgloss/tree/main/.copilot/skills/humanizer Command: npx skills add https://github.com/sachinnair90/gitgloss --skill humanizer-sachinnair90
This Skill helps you write external-facing responses that sound warm, helpful, and natural instead of robotic, corporate, or overly formal.
Use the humanizer skill to rewrite this public reply so it sounds warm, specific, empathetic, and conversational.
High-intent search queries and answers about installing and using this skill.
To humanize community responses, rewrite them using active voice, direct second-person address, and conversational language. This replaces robotic corporate phrasing with warm, specific guidance for issue replies and troubleshooting updates.
The best way to make support acknowledgments feel less robotic is to avoid empty acknowledgments and link-dumping. Rewrite responses to include specific asks, empathetic language, and natural conversational phrasing.
Yes, this approach works for welcome messages and feature guidance comments. It applies active voice, second-person address, and empathy to common community workflows like redirects, closings, and troubleshooting updates.
You should avoid passive voice in discussion comments whenever you need to provide specific asks and direct guidance. Using active voice ensures your external-facing communication sounds natural, warm, and directly helpful to the reader.
acmelemeDraft community responses with warm, human-sounding tone and empathy markers.
elbrunoEnforce humanized tone patterns for GitHub issue and discussion responses.
mpauloskyRewrite PAO drafts with warm, empathetic tone patterns for community responses.
jonnymuirAudit community response drafts for tone and empathy guidelines.
