humanizer

Enforce warm, human-sounding tone in external PAO responses.

2|1|Updated Mar 25, 2026
One-click install
npx skills add https://github.com/PlagueHO/plagueho.learn --skill humanizer-plagueho
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: humanizer
Source: https://github.com/PlagueHO/plagueho.learn/tree/main/.copilot/skills/humanizer
Command: npx skills add https://github.com/PlagueHO/plagueho.learn --skill humanizer-plagueho

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a structured approach to producing external-facing responses that are warm, human-sounding, and respectful, ensuring consistency with the PAO communication standards.

Core Features & Use Cases

  • Tone enforcement: Apply a warm, empathetic voice to every reply.
  • Pattern guidance: Follow the predefined patterns (warm opening, active voice, second person, empathy markers, etc.) to craft messages.
  • Quality checks: Avoid corporate jargon, avoid excessive certainty, and ensure action-oriented closes.
  • Use Case: When drafting responses to issues in Phase 1, apply these rules to reply to user inquiries, guide conversations, and close threads with clarity and helpfulness.

Quick Start

Draft a warm, human-sounding reply to a user report that follows the 13 tone patterns and ends with a concrete next step.

Frequently Asked Questions about humanizer

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

FAQPage Schema
How do I write warm, empathetic external communications for issue threads?

To write warm, empathetic external communications, apply predefined tone patterns like warm openings, active voice, and second-person phrasing. This ensures your issue and discussion thread replies sound human, respectful, and consistent with PAO communication standards.

What is the best way to apply empathy markers when drafting troubleshooting responses?

Applying empathy markers in troubleshooting responses involves following structured tone patterns that enforce a warm, human-sounding voice. This approach shapes user guidance messages by actively avoiding corporate jargon and ensuring action-oriented closes with concrete next steps.

How do I avoid corporate jargon when writing user guidance messages?

Avoiding corporate jargon in user guidance messages is achieved by enforcing warm tone patterns and running quality checks. This process ensures your external-facing responses use active voice and empathy markers instead of excessive certainty or cold, impersonal language.

Can I use this tone enforcement approach to handle profanity and uncertainty in external replies?

Yes, this tone enforcement approach handles profanity filtering and uncertainty in external replies. It applies strict quality checks to your external-facing PAO responses, ensuring messages remain respectful, clear, and helpful while avoiding excessive certainty or inappropriate language.

Does this communication style skill require any dependencies or components to work?

No, this communication style skill requires no dependencies or components to function. It works standalone to enforce warm, human-sounding tone patterns and quality checks directly when drafting external-facing PAO responses for issue and discussion threads.