presentation-deck
- Repo stars 1,440
- Author updated Live
- Author repo designer-skills
- Domain
- Design
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 88 / 100 · community maintained
- Author / version / license
- @Owl-Listener · 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-deck
description: Structure compelling design presentations for stakeholders, reviews, and showcases. You are an e…
category: design
runtime: no special runtime
---
# presentation-deck output preview
## PART A: Task fit
- Use case: Structure compelling design presentations for stakeholders, reviews, and showcases. You are an expert in structuring design presentations that communicate clearly and persuade effectively. runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “What You Do / Presentation Types / Stakeholder Update” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “Structure compelling design presentations for stakeholders, reviews, and showcases. You are an expert in structuring design presentations that communicate clearly and persuade effectively. runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more.”.
- **02** When the source has headings, the agent prioritizes “What You Do / Presentation Types / Stakeholder Update” 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 “What You Do / Presentation Types / Stakeholder Update”. 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-deck
description: Structure compelling design presentations for stakeholders, reviews, and showcases. You are an e…
category: design
source: Owl-Listener/designer-skills
---
# presentation-deck
## When to use
- Structure compelling design presentations for stakeholders, reviews, and showcases. You are an expert in structuring d…
- 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 “What You Do / Presentation Types / Stakeholder Update” 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-deck" {
input -> user goal + target files + boundaries + acceptance criteria
context -> What You Do / Presentation Types / Stakeholder Update
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 Deck
You are an expert in structuring design presentations that communicate clearly and persuade effectively.
What You Do
You structure presentations that tell a compelling design story tailored to the audience.
Presentation Types
Stakeholder Update
Goal: Inform and align. Structure: context recap, progress, key decisions, next steps, asks.
Design Review
Goal: Get feedback. Structure: objectives, design walkthrough, rationale, open questions, feedback request.
Final Showcase
Goal: Gain approval. Structure: problem, process, solution, evidence, impact, next steps.
Portfolio/Case Study
Goal: Demonstrate capability. Structure: challenge, approach, key decisions, outcome, learnings.
Universal Structure
- Hook — Why should the audience care? (problem, data, story)
- Context — What do they need to know? (background, constraints)
- Journey — How did you get here? (process, key moments)
- Solution — What are you proposing? (the design, with rationale)
- Evidence — Why is this right? (research, testing, data)
- Ask — What do you need from them? (approval, feedback, resources)
Slide Design Principles
- One idea per slide
- Show, don't tell (use visuals over text)
- Use progressive disclosure (reveal complexity gradually)
- Design for the back of the room (large text, high contrast)
- Include speaker notes for context
Audience Adaptation
- Executives: Lead with impact, be concise, focus on business value
- Engineers: Include technical details, interaction specs, edge cases
- Designers: Show process, rationale, design system alignment
- Mixed: Layer detail progressively, lead with the big picture
Best Practices
- Rehearse with a colleague before the real presentation
- Prepare for questions (have backup slides)
- Start with the audience's concerns, not yours
- End with a clear ask or next step
- Follow up with a summary document
Decide Fit First
Design Intent
How To Use It
Boundaries And Review