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.
Resources
1Install
npx skillscat add yuukias/ai-skills-collection/business-presentations Install via the SkillsCat registry.
SKILL.md
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 stepWorkflow
- Before any non-trivial presentation work, read
../../shared/presentation-end-to-end-pre-execution-runbook.mdin full, then read../../shared/pre-execution-cumulative-acceptance-contract.mdand derive task classification, Critic requirement, history scope, freeze state, locks, and round allowlist. - Read and apply
../../shared/authoring-production-workflow.mdfor every non-trivial deck. ChatGPT/Planner owns audience, narrative, page jobs, visible copy, layout semantics and locks; Codex owns production and autonomous Producer/Reviewer repair loops. - Clarify the decision, audience, time limit, and required output format.
- Produce
deck-plan.yamlfor non-trivial decks and keep each slide tied to one decision-relevant message. - For materially new visual systems, prove shared components and a small representative golden-page pack before building the complete deck. The user must not receive the first visual prototype as a full deck.
- 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. - For non-trivial production or revision, freeze an authority bundle and explicit round allowlist, then apply
../../shared/anti-shortcut-production-contract.md. The executor must produce a proof-carrying patch manifest and may not turn a local repair into a full-deck rewrite, add unapproved visible prose, delete required content to solve layout pressure, or alter validation rules. - Route editable deck creation to official Presentation/Slides and keep visual QA evidence. Apply
../../shared/independent-review-contract.md: the Codex Parent Controller must coordinate fresh Producer and fresh read-only Reviewer contexts inside one Goal; the user must not relay intermediate completion blocks or act as first QA. - Existing-deck revisions must converge monotonically: open issues shrink, accepted/locked slides and components grow, and unrelated changes remain zero. A recurrence of an accepted issue triggers root-cause repair of the shared primitive, authority, or detector rather than another broad candidate.
- Final delivery still requires one complete whole-deck regression even when intermediate user review is delta-only.
References
../../shared/presentation-end-to-end-pre-execution-runbook.md../../shared/pre-execution-cumulative-acceptance-contract.md../../shared/authoring-production-workflow.md../../shared/deck-plan.schema.json../../shared/template-routing.md../../shared/ppt-skill-routing.md../../shared/source-fidelity.md../../shared/visual-qa.md../../shared/anti-shortcut-production-contract.md../../shared/independent-review-contract.md