skills.rest
elbruno
elbrunoCOMMUNITY
Explore all skills by this author →
Website𝕏@elbrunoGitHub

humanizer

Enforce humanized tone patterns for GitHub issue and discussion responses.

2|Updated Apr 21, 2026
Search Tags:#issue triage#customer communication#tone enforcement#community responses#empathetic writing#PAO drafting#link context
One-click install
npx skills add https://github.com/elbruno/md-to-slides --skill humanizer-elbruno
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: humanizer
Source: https://github.com/elbruno/md-to-slides/tree/main/.copilot/skills/humanizer
Command: npx skills add https://github.com/elbruno/md-to-slides --skill humanizer-elbruno

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents external-facing draft responses from sounding robotic or overly corporate by enforcing a consistent, human, empathetic tone across issue and discussion communications.

Core Features & Use Cases

  • Warm, helpful openings: Start acknowledgments with empathy (e.g., thanks, great question) instead of generic statements.
  • Active, second-person communication: Prefer “we’re looking into this” and “here’s what we found” with direct “you” language.
  • Trustworthy closure and uncertainty handling: End with action-oriented follow-ups while avoiding over-promising and supporting uncertainty transparently.
  • Practical guardrails: Enforce no link-dumping, no profanity/slurs, and avoid open-ended information requests by asking for specific details.

Quick Start

Use the humanizer skill to rewrite an external-facing PAO response so it is warm, human-sounding, and action-oriented.

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 responses sound more empathetic and less corporate?▼

To make GitHub issue responses more empathetic, draft the message using warm acknowledgments, active voice, and second-person phrasing. This ensures community communication remains human-sounding and avoids a robotic corporate tone.

What's the best way to enforce tone guidelines for community responses?▼

Enforce community response tone by applying guardrails that prevent profanity, link-dumping, and open-ended information requests. This requires specific detail gathering and action-oriented follow-ups to maintain empathetic, non-corporate communication.

How do you write a humanized closing message for a discussion thread?▼

Write a humanized discussion closing by using action-oriented follow-ups and uncertainty-safe commitments. This approach supports transparent communication when handling unresolved user concerns without over-promising specific outcomes.

Can I rewrite an existing draft PAO response to be warmer and clearer?▼

You can rewrite an existing PAO response by revising it to include warm openings, direct "you" language, and specific detail requests. This transforms robotic drafts into helpful, action-oriented community messages.

Why do my customer communications sound robotic when addressing user concerns?▼

Customer communications sound robotic when they lack warm acknowledgments, use passive voice, or rely on link-dumping. Revising these messages with active voice and empathetic openings humanizes the tone for issue triage.

Related Skills

Explore More Content & Communication Skills→
mpauloskympaulosky

humanizer

Rewrite PAO drafts with warm, empathetic tone patterns for community responses.

Community
Intermediate
SalesablySalesably
44

follow-up-emails

Generate post-call follow-up emails with structured summaries and next steps.

Official
Intermediate
mysticaltechmysticaltech
3.9k

triage-issue

Triage GitHub issues by analyzing content, detecting duplicates, and drafting maintainer-ready responses.

Community
Intermediate
Leep-GHLeep-GH

humanizer

Draft external-facing responses with warm, human tone and structure.

Community
Intermediate