# Humanizer Human Guide ## What This Is For When the user wants to rewrite or edit text to remove the telltale signs of AI generation and make it sound like a person wrote it. It gives the agent a clearer input/output frame for humanizer: what context to ask for, what decisions to make, and what usable artifact to return. Use this as a human-readable version of the Humanizer agent skill. It is meant for marketers, operators, founders, and other non-coders who want the workflow without reading agent-specific implementation instructions. ## When To Use This - Use this when you need a repeatable process for humanizer. - Use this when the task needs judgment, examples, constraints, or a clear output format rather than a one-off prompt. - Use this when you want to hand an AI assistant enough context to produce a usable marketing artifact. ## When Not To Use This - Do not use this when you only need a quick factual answer. - Do not use this when the work depends on private data you cannot share with the assistant. - Do not use this as a replacement for legal, compliance, financial, or medical review. ## What You Need Before Starting - The goal or business outcome you want. - The audience, customer segment, or market context. - Any source material the assistant should respect, such as notes, briefs, examples, URLs, or brand guidance. - Constraints such as tone, length, channel, deadline, region, or approval requirements. - A clear definition of what a good final answer should look like. ## Step-By-Step Workflow 1. State the job clearly: "Use the Humanizer guide to help me with..." 2. Add context: audience, goal, offer, channel, source material, and constraints. 3. Ask the assistant to identify missing inputs before producing the final output. 4. Have the assistant follow the skill-specific guidance below. 5. Review the result against the final checklist and ask for revisions where needed. ## Skill-Specific Guidance - **Em dashes.** Never produce an em dash. Use a comma, period, colon, semicolon, or parentheses instead. - **Copula.** Use "is," "are," "was," "were," "has," and "have." Do not substitute "serves as," "stands as," "represents," "marks," "boasts," "features," or "offers" when a plain copula works. - **Significance claims.** Delete every sentence that tells the reader something is important, significant, or consequential. Replace with a specific fact or delete entirely. - **Groups.** Do not force ideas into groups of three. If the third item feels like filler, delete it. - **Negative parallelism.** Do not use "not just X, it's Y," "not only... but also," "it's not about X, it's about Y," or any variant. State what it is. - **Chatbot residue.** Delete "I hope this helps," "Let me know," "Great question," "Certainly," "Of course," "Would you like me to," "Here is a," and "You're absolutely right." - **Closings.** Do not end with balanced wisdom, generic optimism, or an unobjectionable sentence. End with a concrete image, specific fact, unresolved question, or arguable claim. - **Formatting.** No emojis in body text. No bold-label-colon list items. No title case in headings. Use straight quotes, not curly quotes. No decorative boldface on terms that do not need emphasis. - Give the writer a first name, approximate age, and reason they are writing this piece. - What does this writer know well about the subject? - What does this writer not know well, or find boring? - What is this writer's honest, debatable opinion about the main claim? ## Decision Points And Nuance The original skill emphasizes: Hard rules, Before you rewrite: build a writer, What human writing actually does, Uneven density, Register mixing, Genuine uncertainty, Structural lopsidedness, Sentence length as a byproduct, Opinions that cost something, First person that means something. Use these questions to steer the work: - What is the intended audience or buyer? - What source material must be preserved? - What should the assistant optimize for: clarity, persuasion, accuracy, speed, creativity, or conversion? - What examples represent the desired quality bar? - What should the assistant avoid? ## Common Mistakes - **Em dashes.** Never produce an em dash. Use a comma, period, colon, semicolon, or parentheses instead. - **Copula.** Use "is," "are," "was," "were," "has," and "have." Do not substitute "serves as," "stands as," "represents," "marks," "boasts," "features," or "offers" when a plain copula works. - **Significance claims.** Delete every sentence that tells the reader something is important, significant, or consequential. Replace with a specific fact or delete entirely. - **Groups.** Do not force ideas into groups of three. If the third item feels like filler, delete it. - **Negative parallelism.** Do not use "not just X, it's Y," "not only... but also," "it's not about X, it's about Y," or any variant. State what it is. - **Closings.** Do not end with balanced wisdom, generic optimism, or an unobjectionable sentence. End with a concrete image, specific fact, unresolved question, or arguable claim. - **Formatting.** No emojis in body text. No bold-label-colon list items. No title case in headings. Use straight quotes, not curly quotes. No decorative boldface on terms that do not need emphasis. - Do not touch the text until you have silently answered these questions: ## Copy-And-Paste Prompt ```text Use the Humanizer human guide. My goal: [Describe the business outcome] Audience: [Describe who this is for] Context and source material: [Paste notes, examples, links, or existing copy] Constraints: [Tone, length, channel, timeline, must-include items, must-avoid items] Before producing the final output, ask me for any missing information that would materially improve the result. ``` ## Final Checklist - [ ] The output matches the original goal. - [ ] The audience and context are reflected in the answer. - [ ] Important constraints and source material were preserved. - [ ] The assistant made the relevant decisions explicit. - [ ] The final artifact is ready to use, review, or hand to the next person. ## Source This guide was generated from the Profound skill entry for `humanizer`. ## Source Skill Notes These notes preserve the nuance from the original skill. Use them as supporting reference when the workflow above feels too generic. # Humanizer You are a writing editor. Your job is to take AI-generated text and make it read like a specific person wrote it. Not a generic "good writer." A person, with uneven knowledge, real opinions, and no interest in sounding balanced. This skill has two layers. Layer 1 is a set of hard rules you must follow on every rewrite. They are non-negotiable. Layer 2 is generative guidance that tells you what human writing actually does, so you can create it rather than just removing bad patterns. ## Hard rules These 10 rules are absolute. They override any other instruction. 1. **Em dashes.** Never produce an em dash. Use a comma, period, colon, semicolon, or parentheses instead. 2. **Banned words.** If any of these words appear in your draft, rewrite the sentence using a concrete fact, specific date, or named source: pivotal, crucial, vital, testament, landscape as a figurative noun, tapestry as a figurative noun, underscore as a verb, highlight as a verb, showcase, foster, garner, delve, vibrant, enduring, intricate, interplay, additionally, enhance, align with. 3. **Copula.** Use "is," "are," "was," "were," "has," and "have." Do not substitute "serves as," "stands as," "represents," "marks," "boasts," "features," or "offers" when a plain copula works. 4. **Significance claims.** Delete every sentence that tells the reader something is important, significant, or consequential. Replace with a specific fact or delete entirely. 5. **Groups.** Do not force ideas into groups of three. If the third item feels like filler, delete it. 6. **Negative parallelism.** Do not use "not just X, it's Y," "not only... but also," "it's not about X, it's about Y," or any variant. State what it is. 7. **Chatbot residue.** Delete "I hope this helps," "Let me know," "Great question," "Certainly," "Of course," "Would you like me to," "Here is a," and "You're absolutely right." 8. **Closings.** Do not end with balanced wisdom, generic optimism, or an unobjectionable sentence. End with a concrete image, specific fact, unresolved question, or arguable claim. 9. **Filler phrases.** Replace mechanically: "in order to" becomes "to"; "due to the fact that" becomes "because"; "at this point in time" becomes "now"; "it is important to note that" becomes nothing; "has the ability to" becomes "can." 10. **Formatting.** No emojis in body text. No bold-label-colon list items. No title case in headings. Use straight quotes, not curly quotes. No decorative boldface on terms that do not need emphasis. ## Before you rewrite: build a writer Do not touch the text until you have silently answered these questions: - Give the writer a first name, approximate age, and reason they are writing this piece. - What does this writer know well about the subject? - What does this writer not know well, or find boring? - What is this writer's honest, debatable opinion about the main claim? - If this writer had to cut the piece by a third, what would they lose first? These answers create asymmetry. The writer knows some things and not others. They care about some parts and rush others. Without this, you will produce omniscient narration with even coverage, which reads as AI. ## What human writing actually does Removing AI patterns is not enough. You must create the properties that make writing feel human. ### Uneven density The section the writer cares about gets the most words. The section they find boring gets compressed or skipped. ### Register mixing A real writer's vocabulary is lumpy. They might use a technical term from a paper, then use "stuff" in the next sentence. ### Genuine uncertainty When a real writer does not know something, they skip it, say they do not know, or state it with less confidence. ### Structural lopsidedness At least one paragraph should be noticeably longer because the writer had more to say. At least one should be short because the writer had less. ### Sentence length as a byproduct Write each sentence at whatever length the thought requires. Do not plan sentence length or deploy staccato rhythm as a device. ### Opinions that cost something A real opinion is specific and debatable. If the piece calls for a point of view, commit to one. ### First person that means something If you use first person, say something specific to an actual cognitive state. If first person adds nothing real, do not use it. ## Second-generation tells Avoid these cleaned-up-AI patterns: - **Performed cleverness.** Unexpected adjective-noun pairings designed to sound witty. - **Staccato deployment.** Three short sentences in a row followed by a longer one. - **Wisdom-shaped objects.** Sentences shaped like insight that say nothing debatable or specific. - **Omniscient casual.** A relaxed voice that knows everything and admits no gaps. - **Perfect structural balance.** Every paragraph has the same weight and role. ## Pattern reference ### 1. Inflated language Replace significance inflation and promotional language with a specific fact, date, named source, or nothing.