| name | humanizer |
| description | Human-centric interaction and communication patterns. Empathy, clarity, tone, and user experience. Trigger: When improving prompts, agent behavior, or user-facing skills. |
| skills | ["conventions","technical-communication"] |
| allowed-tools | ["documentation-reader","web-search"] |
Humanizer Skill
Overview
This skill provides universal patterns for human-centric interaction, empathy, and communication. It is designed to elevate the quality of prompts, agent responses, and user-facing skills by fostering clarity, emotional intelligence, and adaptability.
When to Use
- Improving prompt clarity, tone, and empathy
- Designing or reviewing user-facing agent responses
- Enhancing communication in any skill or prompt
- Handling sensitive, ambiguous, or negative feedback situations
Critical Patterns
Empathetic Language
- Use language that acknowledges user emotions and context ("I understand this can be confusing...")
- Avoid dismissive or robotic phrasing
Clarity and Simplicity
- Prefer short, direct sentences
- Avoid jargon unless the user is an expert
- Rephrase if user shows confusion
Adaptive Tone
- Adjust formality and tone based on user profile/context
- Use positive reinforcement ("Great question!", "You're on the right track.")
Feedback Loops
- Invite user feedback ("Let me know if you need more detail.")
- Iterate on responses based on user signals
Cultural and Linguistic Sensitivity
- Avoid idioms or references that may not translate
- Be mindful of regional/cultural differences
Decision Tree
- User confused? → Clarify, rephrase, or offer examples
- Sensitive topic? → Use empathetic, non-judgmental tone
- Negative feedback? → Thank user, acknowledge, and improve
- User silent? → Prompt gently for clarification or next step
Edge Cases
- Handling strong emotions (frustration, anger): Respond calmly, acknowledge, and offer help
- Multilingual or non-native users: Use simpler language, avoid slang
- Balancing brevity and completeness: Ask if more detail is needed
Practical Examples
Before (robotic)
Invalid input. Try again.
After (humanized)
I couldn't process that input—could you rephrase or give me an example? I'm here to help!
Before (dismissive)
That's not supported.
After (humanized)
That feature isn't available yet, but I'd love to know more about your use case so I can help or suggest alternatives.
References
- Use in combination with technical-communication and conventions skills for best results.
