AiPPT Collaborative Presentation Generator

Problem

Generating decks from topics, documents, or links is less about producing a first draft and more about controlling the process. Without guardrails, outline confirmation can be skipped, template selection happens too late, high-level options are guessed from user intent, and failures silently fall back to another flow. aipptskill packages the AiPPT.cn open API as a collaborative office workflow.

How It Works

The skill first classifies the request into five paths: smart generation, document upload / Word import, PPT import, link-based generation, and single-slide generation. Each path keeps critical stages visible:
- Smart generation: produce an outline with --outline-only, fetch the PPT tree structure, let the user confirm or edit it, then select a template and generate content.
- Document import: after the API returns outline and content, edit the tree structure, write the changes back, and synthesize the deck.
- PPT import / link generation: skip high-level settings and focus on outline edits plus template selection.
- Single slide: confirm title, key message, layout, and visual style only.

High-level options are limited to real enums returned by the API, such as page count, audience, tone, language, and model switching. Credentials are read from secure settings via AIPPT_APP_KEY and AIPPT_SECRET_KEY, not pasted into chat.

Boundaries

It is not a black-box one-click generator. If an endpoint returns unavailable, unauthorized, or 40008, the skill stops and asks the user to enable the capability instead of switching scenarios automatically. Output quality also depends on platform moderation, template availability, and account balance.