Desktop presentation
Presentation creation — slide outline planning, per-slide content design, speaker notes drafting, visual layout suggestions, storyline building.
install
source · Clone the upstream repo
git clone https://github.com/openyak/openyak
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/openyak/openyak "$T" && mkdir -p ~/.claude/skills && cp -r "$T/backend/app/data/skills/presentation" ~/.claude/skills/openyak-desktop-presentation && rm -rf "$T"
manifest:
backend/app/data/skills/presentation/SKILL.mdsource content
Presentation Creation
When the user asks you to help create a presentation outline, slide content, or speaker notes, follow this workflow:
1. Clarify requirements
- Topic: What is the presentation about?
- Audience: Executives, clients, team, general public? What's their knowledge level?
- Duration: How long is the presentation? (determines slide count)
- Purpose: Report, propose, train, persuade, share?
- Style: Formal, business, creative, academic?
Duration and slide count guide
| Duration | Suggested slides | Use case |
|---|---|---|
| 5 min | 5-8 | Elevator pitch, quick update |
| 15 min | 10-15 | Project report, proposal |
| 30 min | 15-25 | Detailed report, training |
| 60 min | 25-40 | Deep training, workshop |
2. Storyline design
Classic structures
Reporting (most common)
- Cover slide
- Agenda / table of contents
- Background and purpose
- Core content (3-5 chapters)
- Summary and next steps
- Q&A / Thank you
Persuasion (proposals / sales)
- Pain point / problem statement (build empathy)
- Current state analysis (data support)
- Proposed solution (core value proposition)
- Case studies / expected results
- Implementation plan
- Call to action
Training
- Learning objectives
- Concept explanation
- Case studies
- Hands-on exercises
- Key takeaways recap
- Practice / assignments
3. Per-slide design principles
Content principles
- One slide, one message: Each slide should convey a single core idea
- Title = conclusion: Write conclusion-driven titles, not descriptive ones
- Good: "Q3 revenue grew 35% YoY"
- Bad: "Q3 revenue overview"
- Less is more: No more than 6 bullet points per slide, keep each point concise
- Visualize data: Use charts over tables, tables over text
Visual layout suggestions
| Content type | Recommended layout |
|---|---|
| Key metric | Large number + small annotation |
| Comparison | Side-by-side or before/after |
| Process | Flowchart / timeline |
| Categories | Icon + text grid |
| Quote | Large centered text + attribution |
| Team intro | Photo + bio cards |
Color suggestions
- Business: Navy, gray, white
- Tech: Dark background + blue-green accents
- Creative: Bold contrasting colors, gradients
- Academic: White background + single accent color
4. Output format
Outline output
## Slide 1: Cover - Title: [presentation title] - Subtitle: [date / occasion / presenter] ## Slide 2: [slide title] - Point 1 - Point 2 - Point 3 - [Visual suggestion]: Use a bar chart for comparison ## Slide 3: [slide title] ...
Speaker notes output
For each slide, provide:
- Opening line (hook attention)
- Transition phrase (connect to previous slide)
- Key talking points (how to present data/conclusions)
- Closing summary
5. Presentation tips
- Opening: Start with a question, story, or surprising data point
- Pacing: Spend more time on important slides, move quickly through transitions
- Interaction: Include questions or discussion points where appropriate
- Closing: Recap key points + clear call to action
6. Quality checklist
- Is the storyline coherent? (Is there a logical thread from start to finish?)
- Does each slide have only one core message?
- Do titles convey conclusions?
- Is there too much text? (Can it be further condensed?)
- Are data charts clear and readable?
- Does the total slide count match the presentation duration?
- Does the last slide have a clear call to action?