writing-best-practices

Edit professional prose to remove AI-like phrasing and filler while preserving voice.

Updated Jan 17, 2026

Search Tags:#documentation #writing #editing #readability #style #voice

Ready to run

npx skills add https://github.com/heykvnzhao/dotfiles --skill writing-best-practices

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: writing-best-practices
Source: https://github.com/heykvnzhao/dotfiles/tree/main/skills/writing-best-practices
Command: npx skills add https://github.com/heykvnzhao/dotfiles --skill writing-best-practices

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps writers produce clear, direct prose by eliminating AI-sounding phrasing, filler, and vagueness across professional documents.

Core Features & Use Cases

Punchline first, then details.
Be specific. Prefer concrete nouns, numbers, names, and dates over vibes.
Be candid about limitations and tradeoffs.
Keep it tight: short paragraphs, minimal signposting, no generic conclusions.
For voice, read references/preferred-voice.md when needed.

Quick Start

Rewrite the provided draft to be clear, direct, and human-sounding.

Frequently Asked Questions about writing-best-practices

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

FAQPage Schema

How do I remove AI-like phrasing from my documentation?▼

To remove AI-like phrasing from documentation, rewrite drafts to be clear and direct by eliminating filler, prioritizing punchlines, and using concrete nouns. This preserves your preferred voice while ensuring professional prose sounds human.

What is the best way to improve readability for professional blog posts?▼

The best way to improve readability for blog posts is to keep paragraphs tight, minimize signposting, and avoid generic conclusions. Prefer concrete nouns, numbers, and dates over vague descriptions to make the writing direct and human-sounding.

Can I use this editing workflow for UI copy and emails?▼

Yes, you can use this editing workflow for UI copy and emails where preserving the author's voice matters. It applies a frontmatter-driven process to guide edits, enforce preferred voice, and provide practical examples for clear, direct prose.

How do I enforce a specific writing style for technical issues?▼

To enforce a specific writing style for technical issues, the workflow reads a preferred-voice reference file to guide edits. It removes AI-sounding phrasing and vagueness, ensuring your issues maintain a consistent, candid, and specific style.