humanize-ppt

humanize-ppt

Catalogue stub — full skill: LearnPrompt/humanize-ppt

Decision tree

1. Is the full skill already installed?

   • Global: f=~/.agents/skills/humanize-ppt/SKILL.md; [ -f "$f" ] && ! grep -q "^das:" "$f" && echo "installed" || echo "pointer"
   • Project: f=.agents/skills/humanize-ppt/SKILL.md; [ -f "$f" ] && ! grep -q "^das:" "$f" && echo "installed" || echo "pointer"
   • installed → the skill is installed as humanize-ppt, invoke it and proceed
   • pointer → go to step 2

2. Detect scope, then install:

   [ -e ~/.agents/skills/humanize-ppt ] && echo "global" || echo "project"
   

Global:

npx skills add LearnPrompt/humanize-ppt --skill humanize-ppt -g -y

Project:

npx skills add LearnPrompt/humanize-ppt --skill humanize-ppt -y

Claude Code: send a command as a chat message starting with ! to run it without leaving the conversation.

Heads-up

• Requires: A downstream renderer skill (it never renders slides itself): guizang-ppt-skill for Chinese decks, frontend-slides for English HTML decks
• License: MIT (LICENSE file; GitHub reports it as non-standard)
• Download size: ~40 MB.

Invoke after install

• Skill name: humanize-ppt
• Run it before rendering (brief mode) and again after rendering with the rendered deck as input (checkup mode)
• Trigger phrases: "humanize ppt", "presentation outline director", "audience state transfer outline", "presentation checkup"

What it does

Treats a deck as an audience state-transfer artifact rather than an information container. From notes, transcripts, documents, or links it writes a deck brief, an AST outline, a slide plan with a per-page media decision (photo, system diagram, short process clip, or nothing), speaker intent, and a style brief for the next agent. After a downstream skill renders the deck, a checkup pass compares each rendered page to its outline page, flags pages that can only be looked at rather than spoken from, and writes fix instructions, for up to three rounds before handing back to a human. It owns the story and the check, not the visuals.

When NOT to use

• You only want one good-looking template page with no outline or checkup → use a renderer directly: html-ppt, frontend-slides, kami, or guizang-ppt
• Markdown-driven developer decks → use slidev-skill or marp-slides
• Linting slide quality for Marp decks → use marp-slide-quality