dmmdea

Humanize Presentations — AI skill for Claude Code

AI community

Remove AI tells from slide decks without destroying the ones that were deliberate.

How to install Humanize Presentations

This entry records only its repository, not the path inside it, so there is no exact command to give. Open dmmdea/humanize-presentations and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Humanize Presentations does

Remove AI tells from slide decks without destroying the ones that were deliberate. An agent skill for de-slopping existing .pptx files.

Alternatives in AI

  • Guizang Ppt Skill — AI-agent Skill for generating polished HTML slide decks: editorial magazine and Swiss layouts, image prompts 24.9k ★
  • Humanizer: Remove AI Writing Patterns — You are a writing editor that identifies and removes signs of AI-generated text to make writing sound more nat 10.5k ★
  • Om Humanize — Voice-calibrated editing — makes Claude-drafted text sound like you wrote it, not like AI wrote it 4.6k ★

README

humanize-presentations

**Remove AI tells from slide decks without destroying the ones that were deliberate.**

[![License: MIT](https://img.shields.io/badge/License-MIT-blue.svg)](LICENSE) [![Agent Skill](https://img.shields.io/badge/type-agent%20skill-8A2BE2.svg)](https://skills.sh/) [![Works with](https://img.shields.io/badge/works%20with-Claude%20Code%20%C2%B7%20Cursor%20%C2%B7%20Codex-lightgrey.svg)](#install)

A skill for AI coding agents that de-slops an existing `.pptx`. It handles what prose humanizers miss: deck-specific tells, the difference between slide text and speaker notes, non-English decks, and the file mechanics that make a repaired deck actually open.


Why this exists

Prose humanizers are excellent at prose. Point one at a slide deck and it does real damage, because its rhythm and voice passes tell you to add sentence fragments, first person, and lived detail. That advice is correct for a speaker's notes and wrong for a slide.

They also miss the tells that actually mark a deck as machine-made. A word list built for essays has nothing to say about topic-label titles, "Thank You / Questions?" slides, or a chart titled `Revenue by Quarter` instead of what the revenue did.

But the harder problem is the opposite one. **Most deck "tells" are also legitimate design choices.** A deck can follow a fixed section cycle because a rubric demanded it, and carry topic titles because the section names mirror an assignment. A checklist run without judgment flags those alongside the real tells, produces thirty findings, and the three that mattered get lost. The opposite failure is worse: a gate wide enough to excuse the rubric also excuses the template, and passes a deck with the section name in the eyebrow and the footer of every slide.

This skill exists to tell those two situations apart.


The core idea: two independent passes

Findings come in two classes, and conflating them is the failure mode this skill is built around.

| | Sentence-le