YuukiAS 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.jsonas the default intermediate representation. - For Chinese business, executive, product, strategy, or decision slide text, route the final wording pass through
writing-fidelitypluschinese-prosewhen those writing skills are installed. Keep factual numbers, claims, and source labels stable while making the Chinese read naturally.
Narrative
Business decks should answer:
answer/request -> problem or opportunity -> evidence and impact -> plan -> resources and risks -> decision and next step
Workflow
- Clarify the decision, audience, time limit, and required output format.
- Produce
deck-plan.yamlfor non-trivial decks. - Keep each slide tied to one decision-relevant message.
- Use the CUHK default visual system only when no company, client, course, or event template is specified.
- Apply the shared writing handoff before final deck creation: Chinese slide text gets
writing-fidelitypluschinese-prose; English scientific slide prose can usescientific-prosewhen the deck includes research evidence. - 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