humanizer

Enforces warm, human-sounding tone patterns in external-facing community responses.

2|Updated Jul 24, 2026
One-click install
npx skills add https://github.com/elbruno/ElBruno.MagenticUI --skill humanizer-elbruno
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: humanizer
Source: https://github.com/elbruno/ElBruno.MagenticUI/tree/main/.squad/templates/skills/humanizer
Command: npx skills add https://github.com/elbruno/ElBruno.MagenticUI --skill humanizer-elbruno

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 provides tone enforcement patterns so every external-facing response reads as warm, helpful, and human. ## Core Features & Use Cases - Tone Pattern Library: 13 concrete patterns covering warm openings, active voice, empathy markers, and action-oriented closes. - Ready-Made Templates: Seven example responses for welcomes, troubleshooting, feature guidance, redirects, acknowledgments, closings, and technical uncertainty. - Anti-Pattern Guardrails: Explicit list of banned behaviors such as corporate speak, passive voice, link-dumping, and over-promising. - Use Case: When a PAO agent 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 "Your issue has been logged." ## Quick Start Ask the agent to draft a reply to a community issue using the humanizer tone guidelines and templates.

Frequently Asked Questions about humanizer

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

FAQPage Schema
How do I make AI-drafted community responses sound more human?▼

Apply tone patterns such as warm openings, active voice, second-person address, and empathy markers. The skill provides 13 concrete patterns plus seven ready-made templates for common scenarios like troubleshooting and feature guidance.

What tone guidelines should AI agents follow when replying to GitHub issues?▼

Replies should be warm, specific, and action-oriented: acknowledge the reporter, explain findings in active voice, and close with a clear next step. Avoid corporate speak, passive voice, and empty acknowledgments.

What phrases should be avoided in automated community responses?▼

Avoid corporate speak like "We appreciate your patience", passive constructions like "It has been determined", dismissive phrases like "works as designed", robot signatures, excessive emoji, and bare link-dumping without context.

Can automated responses quote profanity from original issue reports?▼

No. The skill mandates a profanity filter: never include profanity, slurs, or aggressive language even when quoting the original report. Paraphrase the relevant content instead.

How is response tone quality measured against a baseline?▼

Responses should align with the tone of 5-10 gold standard reference responses, targeting greater than 80 percent similarity. This baseline comparison keeps drafted replies consistent with the desired community voice.