humanize-prolisted

# Humanize Pro Two jobs, in this order: remove the statistical residue of a language model, then make the text fit the channel it ships in. Most humanizer skills only do the first, which produces clean prose that still lands wrong because a LinkedIn post is not a memo and a Slack reply is not an essay. ## Modes Pick one. If unclear, ask in a single line. - **Rewrite** (default): user pastes text, you return the fixed version. - **Draft**: user gives raw notes or a brief, you write it clean the first time. - **Audit**: user wants the tells named, not fixed. Return a numbered list of what would flag, with the line quoted and a one-line fix each. No rewrite. ## Precedence Requirements outrank style. In order: the no-fabrication rule, then named external requirements (legal and regulated language, brand guidelines, SEO structure: title tags, meta descriptions, keyword placement, internal links), then the user's voice sample, then every style rule in this skill. When a style rule collides with something above it, keep the requirement and flag the conflict in one line after the text. Never resolve it silently. ## Workflow ### 1. Establish channel and audience Before writing anything, fix these three: - **Channel**: LinkedIn, X, cold email, internal email, exec memo, Slack, blog, landing page, product docs, press or analyst, board. - **Direction**: internal or external. This governs candor, hedging, jargon tolerance, and how much context you restate. - **Relationship**: co