humaniser

Rewrite AI-generated prose to remove AI tells while preserving tone and facts.

4|1|Updated Apr 2, 2026
One-click install
npx skills add https://github.com/kvokov/oh-my-ai --skill humaniser-kvokov
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: humaniser
Source: https://github.com/kvokov/oh-my-ai/tree/main/skills/humaniser
Command: npx skills add https://github.com/kvokov/oh-my-ai --skill humaniser-kvokov

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

AI-produced prose often sounds robotic, vague, or overblown, so teams need a structured de-AI rewrite that preserves facts, tone, and intent without inventing claims or weakening the author’s stance.

Core Features & Use Cases

  • Interactive intake rounds confirm goal, register, preservation, format, and uncertainty before any edits, making sure critical language stays untouched and the user’s voice guides the rewrite.
  • AI tells hunt list and audit pass strip signposting, promotional fluff, and chatbot artifacts while enforcing a second-pass skepticism that keeps the prose human and direct.
  • Use case: match the rhythm of a stakeholder email or README section, apply the hunt list across the paragraph, and deliver clean copy that feels like the original author without sounding like a pitch deck.

Quick Start

Tell humaniser to rewrite the provided paragraph to remove AI tells while keeping its tone and stated facts.

Frequently Asked Questions about humaniser

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I remove AI artifacts from prose without changing the original meaning?

To remove AI artifacts from prose, you can use an interactive intake process to set preservation rules, then run an audit pass that strips signposting and fluff while keeping facts and the author's stance intact.

What is the best way to rewrite AI drafts so they sound human for stakeholder emails?

The best way to rewrite AI drafts for stakeholder emails is to apply a hunt list across paragraphs to strip chatbot artifacts, calibrate the rhythm to match human tone, and deliver clean copy without sounding like a pitch deck.

How do I de-AI documentation without weakening my original stance or inventing claims?

To de-AI documentation without weakening your stance, an interactive intake process registers preservation rules first, ensuring critical language stays untouched and facts remain unchanged during the rewrite.

Does the de-AI rewriting process support documentation and reports, or just emails?

The de-AI rewriting process supports documentation, emails, and reports, applying a referenced hunt list and audit passes to remove AI artifacts across various formats before publication.

What are common AI tells in generated text that need removal before publication?

Common AI tells in generated text that need removal include signposting, promotional fluff, and chatbot artifacts, which are identified through a referenced hunt list and reshaped to sound human and direct.

How do I start a de-AI rewrite for a README section?

To start a de-AI rewrite for a README section, provide the paragraph to the tool, confirm your goal and register during the interactive intake, and let it apply the hunt list to deliver clean copy that feels like the original author.