human-voice-guard

Detects LLM writing patterns in Korean and English text and rewrites it in natural human voice.

Updated Apr 5, 2026
One-click install
npx skills add https://github.com/Simon-YHKim/eject-button --skill human-voice-guard-simon-yhkim
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: human-voice-guard
Source: https://github.com/Simon-YHKim/eject-button/tree/main/.claude/skills/human-voice-guard
Command: npx skills add https://github.com/Simon-YHKim/eject-button --skill human-voice-guard-simon-yhkim

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? AI-generated text carries recognizable tells—excessive em-dashes, hollow marketing words like "leverage" and "혁신적", rigid 3-bullet structures, and formulaic closings—that make content feel robotic. This Skill scans text for those patterns, rewrites it in a natural human voice, and creates a per-project STYLE.md so future writing stays consistent. ## Core Features & Use Cases - LLM Tell Detection: Identifies Korean and English patterns such as "~을 도와드립니다", "In conclusion", emoji overload, and em-dash overuse, logging each finding with file, line, and suggested fix. - Three Output Modes: audit (findings only), rewrite (in-place correction plus findings and STYLE.md), and init (STYLE.md only for new projects). - CI Regression Prevention: Ships a grep-based voice-lint.sh script that fails builds when banned vocabulary from STYLE.md reappears. - Use Case: Before publishing release notes or store listing copy, run an audit to strip phrases like "seamless" and "강력한", then rewrite in your project's defined persona so the text reads like a person wrote it. ## Quick Start Ask the assistant to check this text for AI-sounding phrasing and rewrite it to sound like a real person wrote it.

Frequently Asked Questions about human-voice-guard

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

FAQPage Schema
How do I make AI-generated text sound more human?

Run the rewrite mode, which scans for known LLM tells like excessive em-dashes, hollow words such as "leverage" and "혁신적", and formulaic closings, then edits the text in place after your approval. It also generates a STYLE.md capturing your project's tone so future text stays consistent.

What LLM writing patterns does this detect in Korean and English?

For Korean it flags overly formal phrasing like "~을 도와드립니다", translated-English sentence structures, and empty marketing words like "혁신적" and "원활한". For English it flags "leverage", "robust", "seamless", "In conclusion", em-dash overuse, and forced bolding.

Can I run an audit without modifying my files?

Yes, audit mode only reports findings as a list of file, line, pattern, original text, and suggestion without editing anything. Rewrite mode is separate and applies corrections only after user approval.

How do I enforce tone consistency in CI for markdown docs?

Use the included voice-lint.sh script, which greps target paths for built-in banned phrases plus any custom entries in the STYLE.md banned vocabulary section. It exits with code 1 on hits, and STRICT=1 also fails on em-dash overuse.

What are the limitations of automated tone checking?

The linter is grep-based, so it catches known phrases but cannot judge whether a sentence genuinely sounds natural in context. Different channels like store listings versus blog posts need different tones, which is why the Skill requires defining a concrete persona in STYLE.md rather than applying one style everywhere.