# Business Presentations

> Plan business, executive, product, operations, market, client, strategy, pitch, and decision decks. Use when the audience is non-technical or the deck asks for a decision, resource, proposal, or business update.

- Skill: `yuukias/business-presentations` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add yuukias/business-presentations`
- Raw SKILL.md: https://api.skillmd.com/api/skills/yuukias/business-presentations/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: YuukiAS (https://skillmd.com/u/yuukias)
- Updated: 2026-09-21
- Page: https://skillmd.com/skills/yuukias/business-presentations

---

# Business Presentations

Use this skill for decision-oriented decks. File creation, object editing, export, and rendering should be handled by the official Presentation/Slides capability when available.

## Boundary

- Use for executive summaries, company updates, product proposals, strategy, operations, market, client, and pitch decks.
- Do not use for technical research talks unless the user explicitly frames the audience as business or executive.
- Do not trigger for small edits to an existing PPTX/Google Slides file.
- Use business presentation themes/templates for deck-wide color. Do not use journal-inspired scientific palettes from `palette/` as business deck themes.
- Use `../../shared/deck-plan.schema.json` as the default intermediate representation.
- For Chinese business, executive, product, strategy, or decision slide text, route the final wording pass through `writing-fidelity` plus `chinese-prose` when those writing skills are installed. Keep factual numbers, claims, and source labels stable while making the Chinese read naturally.

## Narrative

Business decks should answer:

```text
answer/request -> problem or opportunity -> evidence and impact -> plan -> resources and risks -> decision and next step
```

## Workflow

1. Clarify the decision, audience, time limit, and required output format.
2. Produce `deck-plan.yaml` for non-trivial decks.
3. Keep each slide tied to one decision-relevant message.
4. Use the CUHK default visual system only when no company, client, course, or event template is specified.
5. Apply the shared writing handoff before final deck creation: Chinese slide text gets `writing-fidelity` plus `chinese-prose`; English scientific slide prose can use `scientific-prose` when the deck includes research evidence.
6. Route editable deck creation to official Presentation/Slides and keep visual QA evidence.

## References

- `../../shared/deck-plan.schema.json`
- `../../shared/template-routing.md`
- `../../shared/ppt-skill-routing.md`
- `../../shared/source-fidelity.md`
- `../../shared/visual-qa.md`