AiPPT Presentation Generator

Problem

Many presentation tools compress the workflow into “enter a topic, click generate,” but real office work often requires iterating from documents, existing decks, web links, or single-page requests. Without outline confirmation, template selection, and scenario routing, results often need rework and can create risks such as accidental content edits, credential leakage, or silent fallbacks.

How It Works

• The skill routes requests into smart generation, document upload / Word import, PPT import, link-to-PPT, and single-page generation.
• Credentials are read from environment variables or secure platform settings, such as AIPPT_APP_KEY and AIPPT_SECRET_KEY, rather than pasted into chat.
• Advanced settings are fetched from real senior_options, so only API-returned options like page count, audience, scene, tone, and language are shown, and passed as an object string such as {"page":3,"group":6,"scene":18,"tone":40,"language":47}.
• Structure before content: after generating or reading an outline, it fetches the PPT tree structure, lets users confirm, reorder pages, and edit content, then selects a template and synthesizes PPTX; enterprise templates are prioritized when present, and the template count defaults to 6 under initial configuration.

Boundaries

It fits workflows that need controlled generation and human confirmation: topic-based decks, document conversion, PPTX remixing, URL summarization, and single slides. It depends on AiPPT.cn Open Platform capabilities; if a capability is not enabled, the flow stops and tells the user to enable it instead of silently switching scenarios. Output should not include real AK / SK, token, signature, or internal request headers. For users who only want one-click black-box generation, the workflow may feel longer, but it trades speed for reviewable outlines, editable structure, and clearer security boundaries.