Humanizer
Tone enforcement patterns for external-facing community responses
Install
npx skills add Azure-Samples/agent-skills-dotnet-demo --skill humanizergit clone --depth 1 https://github.com/Azure-Samples/agent-skills-dotnet-demo.git /tmp/agent-skills-dotnet-demo
mkdir -p ~/.claude/skills
cp -r /tmp/agent-skills-dotnet-demo/.squad/templates/skills/humanizer ~/.claude/skills/humanizerPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
## Context
Use this skill whenever PAO drafts external-facing responses for issues or discussions.
- Tone must be warm, helpful, and human-sounding — never robotic or corporate.
- Brady's constraint applies everywhere: **Humanized tone is mandatory**.
- This applies to **all external-facing content** drafted by PAO in Phase 1 issues/discussions workflows.
## Patterns
1. **Warm opening** — Start with acknowledgment ("Thanks for reporting this", "Great question!")
2. **Active voice** — "We're looking into this" not "This is being investigated"
3. **Second person** — Address the person directly ("you" not "the user")
4. **Conversational connectors** — "That said...", "Here's what we found...", "Quick note:"
5. **Specific, not vague** — "This affects the casting module in v0.8.x" not "We are aware of issues"
6. **Empathy markers** — "I can see how that would be frustrating", "Good catch!"
7. **Action-oriented closes** — "Let us know if that helps!" not "Please advise if further assistance is required"
8. **Uncertainty is OK** — "We're not 100% sure yet, but here's what we think is happening..." is better than false confidence
9. **Profanity filter** — Never include profanity, slurs, or aggressive language, even when quoting
10. **Baseline comparison** — Responses should align with tone of 5-10 "gold standard" responses (>80% similarity threshold)
11. **Empathetic disagreement** — "We hear you. That's a fair concern." before explaining the reasoningDetails
- Skill name
humanizer- Repository
- Azure-Samples/agent-skills-dotnet-demo
- Path
.squad/templates/skills/humanizer/SKILL.md- License
- MIT
- Repo updated
- 10 April 2026
FAQ
What does the Humanizer skill do?
Tone enforcement patterns for external-facing community responses
How do I install the Humanizer skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add Azure-Samples/agent-skills-dotnet-demo --skill humanizer. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Humanizer popular?
It lives in Azure-Samples/agent-skills-dotnet-demo, which has 45 GitHub stars and 11 forks.
Related skills
Agent Collaboration
45Azure-Samples/agent-skills-dotnet-demo
Standard collaboration patterns for all squad agents — worktree awareness, decisions, cross-agent communication
Agent Conduct
45Azure-Samples/agent-skills-dotnet-demo
Shared hard rules enforced across all squad agents
Architectural Proposals
45Azure-Samples/agent-skills-dotnet-demo
How to write comprehensive architectural proposals that drive alignment before code is written
Init Mode
45Azure-Samples/agent-skills-dotnet-demo
Team initialization flow (Phase 1 proposal + Phase 2 creation)
History Hygiene
45Azure-Samples/agent-skills-dotnet-demo
Record final outcomes to history.md, not intermediate requests or reversed decisions
Monitor Experiments
48amplitude/mcp-marketplace
Monitors all active and recently completed experiments across Amplitude projects, triages them by importance, then runs deep analysis and reporting on the most impactful ones. Use when the user asks to "check on experiments", "experiment status", "experiment review", "what experiments are running", or wants a periodic experiment health report.
Browse the most popular Claude skills, all other skills, or write your own with the skills generator.