home / skills / montagao / skills / un-ai-writing

un-ai-writing skill

/un-ai-writing

This skill rewrites and humanizes text, preserving meaning and facts while removing AI-writing tells to sound natural and confident.

npx playbooks add skill montagao/skills --skill un-ai-writing

Review the files below or copy the command above to add this skill to your agents.

Files (2)
SKILL.md
2.8 KB
---
name: un-ai-writing
description: Rewrite and edit existing text to sound natural and human, removing common AI writing tells while preserving meaning and facts. Use when asked to humanize, de-AI-ify, un-AI, make it sound less robotic, polish an AI draft, or remove AI-writing signs in any prose (emails, docs, posts, essays, scripts).
---

# Un-AI Writing

Make provided text read like a real person wrote it by removing common AI-writing tells and strengthening specificity, voice, and coherence.

## Workflow

1. **Interview the user**
   Ask for:
   - Audience and purpose
   - Desired tone (casual, formal, candid, authoritative, etc.)
   - Format constraints (length, headings, bullets, style guide)
   - Must-keep facts, phrases, or terminology
   - Rewrite intensity (light polish vs. heavy rewrite)
   - Any sensitive claims to preserve exactly

2. **Diagnose AI tells**
   Read the draft and identify likely AI-writing signs using `references/signs_of_ai_writing.md`.
   Do this internally to guide edits. Avoid calling them “AI” in the final output unless the user asks.

3. **Rewrite with intent**
   - Replace generic claims with concrete, specific details where possible
   - Cut fluff, empty transitions, and formulaic sectioning
   - Vary sentence length and structure
   - Prefer simple verbs and direct statements over inflated phrasing
   - Reduce excessive hedging and generic caveats
   - Keep voice consistent across paragraphs

4. **Verify integrity**
   - Preserve meaning and all factual claims
   - Do not add new facts or sources
   - Ensure tone matches the requested audience
   - Remove remaining AI tells from the reference checklist

5. **Deliver**
   Provide the revised text. Optionally include a short bullet list of the most important edits and any open questions.

## Editing Moves

Apply as needed:
- Replace vague modifiers ("significant", "various", "notable") with specifics
- Swap template transitions ("Moreover", "In today's world") for direct links or cut them
- Break up uniform paragraph sizes
- Remove repetitive "rule of three" patterns unless they serve a rhetorical purpose
- Avoid "not X but Y" structures when repeated multiple times
- Use contractions where natural
- Limit em dashes and over-bolded phrases
- Remove filler conclusions ("challenges and future prospects") unless requested

## Special Contexts

- **Wikipedia-like writing**: Keep neutral tone, avoid promotional language, avoid conversational asides, and follow the markup/citation notes in the reference file.
- **Marketing copy**: Keep energy but remove canned phrases; add concrete benefits and proof points supplied by the user.
- **Technical docs**: Preserve exactness and avoid inventing features, metrics, or behavior.

## Reference

Read `references/signs_of_ai_writing.md` when diagnosing or removing AI-writing tells.

Overview

This skill rewrites and edits existing text to sound natural, human, and specific while preserving meaning and facts. It removes common AI-writing tells, tightens phrasing, and restores voice so prose reads like it was written by a person. Use it to humanize drafts, polish AI-generated copy, or de-AI-ify any prose for publication or personal use.

How this skill works

I start by asking a few quick questions about audience, purpose, tone, and any non-negotiable facts or phrasing. I then diagnose mechanical signs of machine-written text and apply targeted edits: cut fluff, swap vague terms for specifics, vary sentence rhythm, and align tone to your instructions. I never add new facts and I preserve all factual claims unless you request changes. The final deliverable is a revised passage and, optionally, a short list of the most important edits and open questions.

When to use it

  • You have an AI draft that feels generic, repetitive, or robotic and needs human polish.
  • You need emails, posts, or scripts to sound like they came from a real person with a clear voice.
  • You want to keep original facts but remove canned phrasing and overused transitions.
  • You need to match a specific tone or audience while keeping content intact.
  • You are preparing copy for marketing, technical docs, or a public-facing article and want natural clarity.

Best practices

  • Provide audience, purpose, desired tone, and any phrases that must stay unchanged.
  • Specify rewrite intensity: light polish keeps most wording; heavy rewrite prioritizes voice and clarity.
  • Flag any sensitive or legally significant claims that must remain verbatim.
  • Share length constraints or style guides up front to avoid rework.
  • Request a brief change log if you want to see the key edits and rationale.

Example use cases

  • Turn a cold, templated product description into a concise, benefit-focused paragraph with personality.
  • Make an AI-generated blog draft read like the author’s voice while preserving all technical facts.
  • Polish customer support replies so they sound empathetic and conversational without altering policy details.
  • Refine a speech or script to include natural pauses and varied sentence length for better delivery.
  • De-AI-ify a LinkedIn post so it feels authentic and specific to your experience.

FAQ

Will you change facts or add new information?

No — I preserve all factual claims. I only rephrase; I won’t invent facts or add sources unless you ask.

Can you keep certain phrases exactly as written?

Yes. Tell me which phrases or terms must remain unchanged and I will preserve them.