docs-voice

Review Patcher Markdown documentation for robotic voice patterns and propose clearer rewrites.

27|1|Updated Feb 20, 2024

Search Tags:#documentation #tone #editing #voice #rewrite #myst markdown

Ready to run

npx skills add https://github.com/liquidz00/Patcher --skill docs-voice-liquidz00

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: docs-voice
Source: https://github.com/liquidz00/Patcher/tree/main/.claude/skills/docs-voice
Command: npx skills add https://github.com/liquidz00/Patcher --skill docs-voice-liquidz00

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you rewrite Patcher documentation so it sounds direct, clear, and human instead of robotic or overexplained.

Core Features & Use Cases

Voice Review: Check docs for awkward preambles, heading-restating openings, hedged passive voice, jargon, and em-dashes.
Rewrite Suggestions: Propose cleaner alternatives that lead with user value and keep the meaning intact.
Apply Mode Guidance: Distinguish between review-only feedback and in-place rewrites when the user explicitly asks for edits.
Use Case: A docs maintainer can scan a guide before publishing and quickly fix tone issues that make Patcher documentation feel verbose or AI-written.

Quick Start

Review docs/guides/export.md for voice issues and suggest concise rewrites without editing the file.

Frequently Asked Questions about docs-voice

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

FAQPage Schema

How do I make my documentation sound less robotic and more human?▼

To fix robotic documentation voice, scan Markdown files for passive phrasing, hedged language, jargon, and em-dashes, then apply rewrites that lead with user value. This removes verbose, AI-written patterns while preserving technical syntax.

How do I edit Markdown files to remove passive voice and jargon?▼

Edit Markdown files by targeting lead paragraphs and repeated headings for passive phrasing and jargon, then proposing clearer alternatives. This process preserves existing cross-references, code blocks, and directive syntax during tone cleanup.

Can I rewrite MyST markdown documentation without breaking cross-references?▼

Yes, you can rewrite MyST markdown documentation without breaking cross-references. The voice review process specifically preserves existing cross-references, code blocks, and directive syntax while proposing tone improvements and rewrites.

What's the best way to review docs for tone before publishing?▼

The best way to review docs for tone before publishing is to scan for diminishing language, awkward preambles, and em-dashes. Use review-only feedback to quickly fix verbose issues that make documentation feel AI-written before applying changes.

Does the voice review edit files in place or only suggest changes?▼

Voice review provides review-only feedback by default to suggest changes. It distinguishes between proposing cleaner alternatives and performing in-place edits, only applying direct changes to the file when explicitly requested.

Why does my documentation still sound robotic after editing?▼

Documentation may still sound robotic if repeated headings, diminishing language, or hedged passive voice remain. Targeting these specific patterns and replacing em-dashes with direct phrasing ensures the text leads with user value.