humanizer

Enforces confident, impact-driven tone and voice rules for Connect performance review drafts.

2|Updated Apr 21, 2026
One-click install
npx skills add https://github.com/EirikHaughom/msconnect-agent --skill humanizer-eirikhaughom
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: humanizer
Source: https://github.com/EirikHaughom/msconnect-agent/tree/main/.github/skills/humanizer
Command: npx skills add https://github.com/EirikHaughom/msconnect-agent --skill humanizer-eirikhaughom

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Performance review drafts often sound corporate-hollow, vague, or passive, weakening the impact of real accomplishments. This Skill enforces a consistent, authentic voice for Microsoft Connect form text so results, setbacks, goals, and actions read as confident and specific. ## Core Features & Use Cases - Tone Enforcement: Applies 10 writing patterns covering impact-first bullets, active first-person voice, quantified results, and honest setbacks. - Anti-Pattern Detection: Flags corporate jargon, passive voice, vague impact claims, defensive setbacks, and generic goals. - Concrete Examples: Provides before/after style examples for results bullets, setbacks, goals, and action statements. - Use Case: When drafting Connect form text with the connect-writer skill, apply these rules to transform "Worked on pipeline generation" into "Drove $2M pipeline by onboarding 3 priority ISVs." ## Quick Start Ask the agent to review my Connect draft and rewrite it with confident, impact-driven language following the humanizer guidelines.

Frequently Asked Questions about humanizer

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

FAQPage Schema
How do I make my performance review sound more confident?

Lead every bullet with the impact or outcome rather than the activity, use active first-person voice, and quantify results inline. Replace phrases like "helped improve" with direct statements such as "Delivered 28% ACR growth."

How to write setbacks in a performance review without sounding negative?

Own the setback directly, show what you learned, and describe the corrective action you took. Avoid defensive framing or self-deprecation; structure it as situation, adaptation, and forward-looking result.

What are common mistakes in self-review writing?

Common anti-patterns include passive voice, activity framing like counting meetings attended, vague impact claims, culture checkbox statements without examples, and repetitive "I" openers. This Skill lists 13 specific anti-patterns to avoid.

Does this writing guidance work outside Microsoft Connect reviews?

The patterns are tuned for Connect form fields and reference Microsoft-specific concepts like core priorities and culture behaviors. The general principles of impact-first, quantified writing transfer to other review formats, but examples are Connect-specific.

When should the humanizer skill be applied in the drafting workflow?

Apply it whenever drafting or refining Connect form text, including results, setbacks, goals, and actions. It is designed to run alongside the connect-writer skill, which produces the initial draft content.