Document to Deck, Without the Wall of Text
Convert a long document into a deck outline with one idea per slide.
A document is read at the reader's pace. A deck is read at the speaker's. Converting one to the other means restructuring, not reformatting.
That is the gap this drop closes. It is a content & writing skill built for Gemini, and it takes about ten minutes to set up the first time. After that it runs in under a minute.
Who should use it
Anyone who has pasted a report into slides and called it a deck.
How it works
The skill file does five things, in this order.
1. Name the audience decision. What you want them to do when the deck ends.
2. Build the argument spine. Six to eight assertions that carry the case in order.
3. Write assertion headlines. 'Revenue fell 8% on two accounts', not 'Revenue Overview'.
4. Assign the evidence. One chart or fact per slide, supporting that headline only.
5. Cut to the spine. Anything not supporting an assertion goes to the appendix.
What comes back
A slide-by-slide outline with assertion headlines, evidence, and an appendix list.
The mistake to avoid
If you read only the headlines in sequence, they should form a complete argument. If they do not, the deck has no spine and no amount of design will fix it.
Running it
Save the prompt as a Gem so it is reusable, or paste it into Gemini with your files attached. If the task touches Sheets, Docs or Gmail, run it from the Workspace side panel so it can read the file you already have open.
Where this fits
On its own, one skill saves an hour a week. The compounding happens when three or four of them run in sequence on the same input, the same transcript that produces a scope of work also produces the follow-up email and the project brief. That is the point at which it stops being a prompt and starts being an internal tool. If you want that wired into the systems your team already uses, that is the work 67 Digital does.
In the file
Convert this document into a presentation outline.
The audience is {who} and I want them to {specific decision or action}.
1. ARGUMENT SPINE, six to eight assertions that carry the case in order. Each
is a full sentence with a subject and verb. Test: reading only these in
sequence must form a complete, persuasive argument.
2. SLIDES, one per assertion. For each: the assertion as the headline (never a
topic label like "Overview"), the single piece of evidence that proves it,
and the visual form that evidence should take.
3. OPENING SLIDE, the one fact or question that earns the next ten minutes.
4. CLOSING SLIDE, the decision requested, with the options.
5. APPENDIX, everything in the document that does not support the spine.
Do not delete it; list it.
Maximum 30 words of body text per slide.
<document>{paste}</document>