humanizer

Applies warm, conversational tone patterns to external-facing community responses.

Updated Jun 2, 2026
One-click install
npx skills add https://github.com/codebytes/btt --skill humanizer-codebytes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: humanizer
Source: https://github.com/codebytes/btt/tree/main/.squad/templates/skills/humanizer
Command: npx skills add https://github.com/codebytes/btt --skill humanizer-codebytes

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 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.

Frequently Asked Questions about humanizer

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

FAQPage Schema
How do I make GitHub issue replies sound less robotic?

Apply warm openings, active voice, second-person address, and empathy markers instead of corporate phrases. For example, write "We're looking into this" rather than "This is being investigated," and close with an action-oriented line like "Let us know if that helps!"

What tone patterns should community responses follow?

Use 13 patterns including warm openings, conversational connectors, specific details over vague statements, empathetic disagreement, and uncertainty when appropriate. Avoid marketing hype, passive voice, and empty acknowledgments.

How should I respond when I am not sure of the answer?

State the uncertainty directly, such as "We're not 100% sure yet, but here's what we think is happening." List what has been ruled out and ask for one specific piece of additional context rather than an open-ended request.

Can I quote profanity from a user's original issue report?

No. The profanity filter pattern requires paraphrasing any profanity, slurs, or aggressive language even when quoting the original report. Responses must never include such language directly.

What phrases should be avoided in community replies?

Avoid corporate speak like "We appreciate your patience," dismissive lines like "This works as designed" without empathy, over-promising ship dates, robot signatures, excessive emoji, and bare link-dumping without context.