humanizer

Applies tone patterns to external-facing community issue and discussion responses.

1|Updated Jul 7, 2026
One-click install
npx skills add https://github.com/seiggy/maf-copilot-studio-demo --skill humanizer-seiggy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: humanizer
Source: https://github.com/seiggy/maf-copilot-studio-demo/tree/main/.squad/templates/skills/humanizer
Command: npx skills add https://github.com/seiggy/maf-copilot-studio-demo --skill humanizer-seiggy

SYSTEM DOCUMENTATION & REQUIREMENTS

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 warm, human tone across all external-facing responses so maintainers communicate consistently and empathetically. ## Core Features & Use Cases - Tone Pattern Library: Provides 13 concrete writing 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 triaging a new bug report, use the troubleshooting template to acknowledge the reporter, explain the suspected cause, and close with an invitation for follow-up. ## Quick Start Draft a reply to this GitHub issue using the humanizer tone patterns and the troubleshooting template.

Frequently Asked Questions about humanizer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write friendly responses to GitHub issues?

Start with a warm acknowledgment like "Thanks for reporting this", use active voice and second person, give specific details rather than vague statements, and close with an action-oriented line such as "Let us know if that helps!" The skill provides templates for common scenarios.

What tone patterns should community responses follow?

Use warm openings, active voice, second-person address, conversational connectors, empathy markers, and specific details. Express uncertainty honestly when unsure, ask for specific information rather than open-ended requests, and add context when sharing links.

What phrases should I avoid in community replies?

Avoid corporate speak like "We appreciate your patience", passive voice like "It has been determined", dismissive statements like "This works as designed", over-promising deadlines, empty acknowledgments, robot signatures, excessive emoji, and bare link-dumping without context.

Can I quote profanity from an original issue report?

No. The skill requires paraphrasing any profanity, slurs, or aggressive language even when quoting the original issue. Responses must remain professional while still acknowledging the reporter's frustration empathetically.

When should I use the technical uncertainty template?

Use it when the cause of a reported issue is not yet confirmed. State what has been ruled out, honestly acknowledge uncertainty, and ask for specific additional context rather than giving false confidence about the diagnosis.