Menu

Individual skill

slide-density-rules

0upvotes

Fix slides that are documents in landscape mode — the one-point-per-slide rule, the projection-vs-reading fork that decides density, the text diet (headlines and evidence, prose to notes), and the glance test. Use when asked my slides are too busy, how much text per slide, fix this wall-of-bullets deck, or make this readable from the back of the room. Produces the density diagnosis, the per-slide fixes (split, strip, or move-to-notes), the projection/document fork decision, and the glance-test results.

skills/slide-density-rules/SKILL.md

Read pinned source

Source commit f7c90bc09ee05dc25cf257bdb1826f2c2552c2cb

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 9, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,539
Repository last updated
Nov 9, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Slide Density Rules Skill

The wall-of-bullets slide fails twice simultaneously: the audience reads instead of listening (reading speed beats talking speed, so they finish and disengage while the presenter catches up), and nothing on it is retained because everything competed. The fix starts with a fork most decks never take: is this *projected* (accompanying a live talk — then slides are billboards: one point, big, glanceable) or *read* (sent as a document — then it's a doc wearing slide clothes, and density is fine but it should be built as a [outline-before-prose](../outline-before-prose/SKILL.md) memo-deck on purpose)? Hybrid decks that try both do both badly; the rules below are the fork, then the diet.

## What This Skill Produces

- **The fork decision** — projected / reading-deck / both-needed (= two artifacts, honestly)
- **The density diagnosis** — per slide: points-per-slide count, the glance-test verdict
- **The fixes** — split (two points → two slides), strip (prose → the speaker's mouth), demote (detail → notes/appendix)
- **The glance test results** — three seconds per slide: what survives, what was noise

## Required Inputs

Ask for these if not provided:
Back to top