Menu

Individual skill

presentations

0upvotes

Help choose a presentation's audience, story, outline, or use of evidence and visuals. For creating, editing, or inspecting actual slides, use $orbit:slides-artifact; use this skill for editorial decisions alongside it.

OpenAI/dots/skills/presentations/SKILL.md

Read pinned source

Source commit a2d33761e49b98f6ec1b48f12143264eb9b4ff4f

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Instructions only
Last checked
Nov 10, 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)
71,199
Repository last updated
Nov 10, 2026
License
CC0-1.0

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

# Presentations

Help shape what the audience should understand or decide. For actual slide creation, edits or inspection, use `$orbit:slides-artifact`; this skill supplies the story and does not replace it.

## Find the story

- Read the brief and relevant sources. Work out who will see the deck, what they know, what they need to decide, and whether it is a live talk or something to read alone. Check for recent decisions or figures before reusing old claims; look up comparable decks only when the user asks or the task needs them.
- Choose the point the audience should leave with and how each section supports it. Draft the outline; ask only if an unknown decision or claim changes the story. Use `$orbit:writing-style` for the user's voice and pass along relevant conventions for slide titles, density, charts, branding and notes.
- Match the requested scope. Updating three charts does not call for a new design or a reordered deck. Use a supplied template or established conventions where relevant.

## Shape the slides

- Choose titles and visuals that carry the point. A chart should answer a question; use a table or words when clearer. Put extra detail in notes or an appendix where useful. A deck meant to stand alone needs enough explanation on the slides.
- Ground claims, charts and quotes in actual sources. Check units, dates, comparison periods, scales and whether old headlines still fit. Include sources for important claims. Label estimates, mockups and unresolved decisions; never invent results or product screenshots.
Back to top