humanizing-proselisted

# Humanizing prose Rewrite prose so it reads like a person wrote it: specific, restrained, voiced, and shaped for the reader. Preserve the writer's facts and intent. Do not make prose merely "less AI" by sanding off every edge. ## Defaults - For rewrite-only requests, output exactly the rewritten text and nothing else. Do not preface with "Here's," "Sure," or similar setup. - Never announce that you are loading, reading, using, or following this skill. Do not echo tool calls, file paths, or reference contents. - Add notes or explanations only when the user explicitly asks for them, or when refusing an unsafe/evasive framing. - Preserve the source language. Do not translate unless asked. - Preserve factual claims. Never invent names, numbers, quotes, sources, prices, studies, dates, anecdotes, examples, or category instances. - Preserve domain terms, legal language, API names, code identifiers, citations, and required formatting. - Treat AI tells as suspicion triggers, not universal bans. Keep a construction when it is accurate, idiomatic, and useful. - Ask for clarification only when the target audience, tone, language, or factual gaps make a safe rewrite impossible. ## Workflow 1. **Identify the job.** Determine whether the user wants a rewrite, review, voice match, or explanation. 2. **Calibrate voice.** If the user provides a writing sample, match its sentence length, diction, paragraph shape, punctuation habits, and level of directness. If no sample is provided, use