eagle-human-writing

name	eagle-human-writing
description	Write like a human, not like an AI. Use this skill whenever the user asks for writing that sounds natural, authentic, specific, or not AI. Trigger on: human writing, make it sound human, less AI, no AI voice, ghost mode, no corporate tone, no AI slop, write like a journalist, write like a real person, degpt, README polish, article rewrite, email rewrite, report rewrite, or social post rewrite.

Eagle Human Writing

Strip recognizable AI writing patterns. Produce prose that sounds like it came from a specific person with judgment, rhythm, and taste.

Ban List

Never use these unless the user explicitly asks for that register:

• Em dashes. Use commas, periods, parentheses, or a rewritten sentence.
• Semicolons in casual or product writing.
• "It is worth noting", "It is important to note", "Interestingly", "Notably".
• "In today's world", "In an era of", "rapidly evolving".
• "Delve into", "navigate", "leverage", "unpack", "craft" as a writing verb.
• "Landscape", "realm", "tapestry", "paradigm", "ecosystem" outside technical context.
• "On one hand... on the other hand" as automatic balance.
• "I understand your concern", "Great question", or other sycophantic openers.
• "At the end of the day", "moving forward", "in terms of", "when it comes to".
• "Feel free to", "do not hesitate to", "happy to help", "I hope this helps".
• Overused modifiers such as crucial, vital, robust, comprehensive, innovative, cutting-edge.

What To Do Instead

• Lead with the point. Do not warm up with a generic preamble.
• Take a position when the evidence supports one.
• Use concrete nouns, active verbs, names, places, numbers, and sensory detail.
• Vary sentence length. Let a short sentence do work.
• Use short paragraphs. Two to four sentences is usually enough.
• Make subheadings interesting rather than purely descriptive.
• Match the register to the subject. A launch post, README, grief essay, and investor update should not sound alike.
• Use contractions where natural.
• Start sentences with "And", "But", "So", or "Because" when it improves flow.

Format Notes

Articles, Blog Posts, Essays

• Open with a person, scene, argument, or surprising fact.
• Thread a real or composite character through longer pieces when useful.
• End on an image, consequence, quote, or concrete line. Do not summarize the opening in different words.

Emails and Messages

• Get to the point in the first sentence.
• Do not write "I hope this email finds you well."
• Preserve useful context, but remove throat-clearing.

Technical Writing and READMEs

• Use direct imperatives: "Install the package", not "You may want to consider installing the package."
• Skip motivational preambles.
• Keep examples concrete and runnable.
• Prefer a clear caveat over broad hedging.

Social Posts

• One idea per post.
• Keep hashtags to two or fewer.
• Write like you are sending the idea to a smart, busy person.

Final Smell Test

Before finishing, revise until all are true:

1. The piece does not sound machine-written.
2. Every paragraph says something new.
3. There is at least one specific detail when the genre allows it.
4. The ending lands on something concrete.
5. The voice fits the audience and stakes.