presentation
- Repo stars 17,717
- Author updated Live
- Author repo openfang
- Domain
- Design
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 88 / 100 · community maintained
- 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 special requirements
- Permissions
-
- Read-only
- Write / modify
- Shell exec
- Network behavior
- Local-only
- Install commands
- 26 variants
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools,默认拥有全部工具权限。
---
name: presentation
description: Presentation expert for slide structure, storytelling, visual design, and audience engagement A…
category: design
runtime: no special runtime
---
# presentation output preview
## PART A: Task fit
- Use case: Presentation expert for slide structure, storytelling, visual design, and audience engagement 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, wheth….
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “Key Principles / Techniques / Common Patterns” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “Presentation expert for slide structure, storytelling, visual design, and audience engagement 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, wheth…”.
- **02** When the source has headings, the agent prioritizes “Key Principles / Techniques / Common Patterns” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files, run shell commands; mostly runs locally; usually needs no extra API key.
## Running Rules
- read files, write/modify files, run shell commands; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options. The source does not require a stable slash command. After installation, invoke the skill by name and describe the task.
Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, write/modify files, run shell commands.
Start with a small task and check whether the result follows “Key Principles / Techniques / Common Patterns”. Inspect diffs, logs, previews, or tests before expanding scope.
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: presentation
description: Presentation expert for slide structure, storytelling, visual design, and audience engagement A…
category: design
source: RightNow-AI/openfang
---
# presentation
## When to use
- Presentation expert for slide structure, storytelling, visual design, and audience engagement A communication strategi…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.
## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.
## Execution rules
- Organize steps around “Key Principles / Techniques / Common Patterns” and keep inference separate from source facts.
- read files, write/modify files, run shell commands; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding the task.
## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies. The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "presentation" {
input -> user goal + target files + boundaries + acceptance criteria
context -> Key Principles / Techniques / Common Patterns
rules -> SKILL.md triggers / order / output contract
runtime -> no special runtime | read files, write/modify files, run shell commands | mostly runs locally
guardrails -> usually needs no extra API key + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
} 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
Decide Fit First
Design Intent
How To Use It
Boundaries And Review