presentation

Design Community

Skill notes

Key Principles

Start with the audience and their key question; every slide should advance toward answering what they need to know, decide, or do Follow the Minto Pyramid Principle: lead with the conclusion or recommendation, then support it with grouped arguments and evidence Apply the "one idea per slide" rule; if a slide requires more than one takeaway, split it into multiple slides with clear transitions Use visual hierarchy to guide attention: large text for key messages, smaller text for supporting detail, and whitespace to prevent cognitive overload

Techniques

Structure the deck with a clear arc: context (why we are here), problem (what is at stake), solution (what we propose), evidence (why it works), and call to action (what happens next) Apply the 30-point font rule as a minimum for body text; if text needs to be smaller to fit, there is too much content on the slide Use data visualizations instead of tables: bar charts for comparison, line charts for trends, pie charts only for 2-3 category proportions

Common Patterns

Situation-Complication-Resolution: Open with the current state, introduce the tension or problem, then present the resolution as your recommendation Problem-Solution-Benefit: Frame each section around a user pain point, the proposed solution, and the measurable benefit it delivers Before and After: Show the current workflow or architecture alongside the proposed improvement, making the value visually self-evident

Pitfalls to Avoid

Do not read slides verbatim; the audience can read faster than you can speak, so slides should support your narrative, not duplicate it Do not use complex animations or transitions that distract from the content; simple fades and builds are sufficient for professional presentations Do not include backup slides in the main flow; place them in an appendix section after the closing slide for reference during Q&A

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Design
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@RightNow-AI · no license declared
Token usage
Lean
Setup complexity
Guided setup
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
  • Write / modify
  • Shell exec
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

Author source file SKILL.md
# Presentation Expert

A communication strategist with extensive experience crafting executive presentations, technical talks, and pitch decks. This skill provides guidance for structuring narratives, designing visually clear slides, and delivering content that engages audiences, whether presenting to investors, engineering teams, or conference attendees.

## Key Principles

- Start with the audience and their key question; every slide should advance toward answering what they need to know, decide, or do
- Follow the Minto Pyramid Principle: lead with the conclusion or recommendation, then support it with grouped arguments and evidence
- Apply the "one idea per slide" rule; if a slide requires more than one takeaway, split it into multiple slides with clear transitions
- Use visual hierarchy to guide attention: large text for key messages, smaller text for supporting detail, and whitespace to prevent cognitive overload
- Rehearse with a timer; knowing your material reduces filler words and ensures you respect the audience's time

## Techniques

- Structure the deck with a clear arc: context (why we are here), problem (what is at stake), solution (what we propose), evidence (why it works), and call to action (what happens next)
- Apply the 30-point font rule as a minimum for body text; if text needs to be smaller to fit, there is too much content on the slide
- Use data visualizations instead of tables: bar charts for comparison, line charts for trends, pie charts only for 2-3 category proportions
- Write presenter notes for every slide with the key talking points and transition sentences to the next slide
- Use progressive disclosure: reveal complex diagrams or lists step by step using builds or animation sequences to maintain focus
- Design a consistent visual language: one primary font, one accent color, consistent alignment grids, and repeating layout templates
- Include a summary slide before the Q&A section that restates the three most important points from the presentation

## Common Patterns

- **Situation-Complication-Resolution**: Open with the current state, introduce the tension or problem, then present the resolution as your recommendation
- **Problem-Solution-Benefit**: Frame each section around a user pain point, the proposed solution, and the measurable benefit it delivers
- **Before and After**: Show the current workflow or architecture alongside the proposed improvement, making the value visually self-evident
- **Demo Sandwich**: Introduce the context before a live demo, perform the demo, then summarize what was shown and why it matters

## Pitfalls to Avoid

- Do not read slides verbatim; the audience can read faster than you can speak, so slides should support your narrative, not duplicate it
- Do not use complex animations or transitions that distract from the content; simple fades and builds are sufficient for professional presentations
- Do not include backup slides in the main flow; place them in an appendix section after the closing slide for reference during Q&A
- Do not overload slides with logos, footers, and decorative elements; every pixel should serve communication, not branding compliance

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.