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.md
source 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

DurationSuggested slidesUse case
5 min5-8Elevator pitch, quick update
15 min10-15Project report, proposal
30 min15-25Detailed report, training
60 min25-40Deep training, workshop

2. Storyline design

Classic structures

Reporting (most common)

  1. Cover slide
  2. Agenda / table of contents
  3. Background and purpose
  4. Core content (3-5 chapters)
  5. Summary and next steps
  6. Q&A / Thank you

Persuasion (proposals / sales)

  1. Pain point / problem statement (build empathy)
  2. Current state analysis (data support)
  3. Proposed solution (core value proposition)
  4. Case studies / expected results
  5. Implementation plan
  6. Call to action

Training

  1. Learning objectives
  2. Concept explanation
  3. Case studies
  4. Hands-on exercises
  5. Key takeaways recap
  6. 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 typeRecommended layout
Key metricLarge number + small annotation
ComparisonSide-by-side or before/after
ProcessFlowchart / timeline
CategoriesIcon + text grid
QuoteLarge centered text + attribution
Team introPhoto + 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?