/xiaobei-skill-academic-paper-to-ppt

name: xiaobei-skill-academic-paper-to-ppt
description: "Use for 小北在读研 / XiaoBei academic paper-to-PPT workflows: generate thesis-defense or project-report decks from uploaded papers, literature, reports, technical documents, and optional PPTX visual templates. Produces a source-grounded outline, an imagegen visual scheme, one complete bitmap per slide, an imagegen provenance manifest, and an image-only PPTX. Do not use when the user needs editable slide text or native editable charts."

小北在读研 · Academic Paper to PPT

Core Behavior

When this skill is triggered, execute the workflow in this exact order:

1. Analyze the uploaded source document 2. If the user provides a PPT/PPTX template, analyze the template's visual style and page structure 3. Create `ppt_outline.md` 4. Generate one complete visual preview scheme based strictly on `ppt_outline.md` using `$imagegen`, then immediately display that image inline in the chat 5. Generate every slide page as a full-page image using `$imagegen`; immediately display each completed page image inline in the chat before waiting for the whole deck 6. Create `imagegen_manifest.json` recording the selected `$imagegen` generation method and every generated asset 7. Assemble the generated slide images into a `.pptx` file where each image fills one complete slide 8. Validate that required output files exist and match the imagegen manifest

Never skip stages unless the user explicitly requests only one stage.

Strict image-only contract:

• A final slide image means the whole finished PPT page is baked into one bitmap, including Chinese title, body text, labels, diagrams, tables, and page visual design.
• The final `.pptx` must contain one full-slide image per slide and no editable visible text boxes.
• Background-only slide images are invalid. Do not generate text-free templates, blank layout backgrounds, placeholder panels, blank areas for later text, or editable-text overlays.
• Prompts for final slide images must not include phrases such as `text-free`, `no readable words`, `background template`, `blank areas`, `editable Chinese text`, `text to be added later`, or equivalent wording.
• If `$imagegen` cannot generate complete page images with the required text, retry with shorter full-page prompts or switch to the other allowed `$imagegen` mode. If complete page images still cannot be produced, stop at image generation and report the failed stage. Do not assemble a fallback PPT.

Chat-visible image contract:

• Apply this contract to both built-in `image_gen` and CLI generation. Changing the image backend must not make generated images invisible to the user.
• Stage 2 produces one visual-scheme image. As soon as it exists, show it in the chat with local-image Markdown using its absolute path, for example ``.
• During Stage 3, show each completed slide image individually as soon as it is available. Label it briefly as `第 X/N 页`, then render that page with its absolute local path. A text-only progress message such as “已生成 6 页” does not satisfy this requirement.
• Do not wait until all pages finish before showing them. Do not replace per-page visibility with only a contact sheet, folder path, file count, or final PPTX link.
• In CLI mode, run generation in a monitorable process and poll for newly completed files. After each poll, display every newly completed `slide_XX.png` individually before continuing to wait. Limited concurrency is allowed, but the chat must expose each completed page rather than hiding the batch until completion.
• In built-in mode, the tool result may render automatically; still add the brief `第 X/N 页` label and preserve/copy the selected image into the workspace for manifesting and PPT assembly.
• After all pages are visible, optionally add a complete contact sheet for convenient overview, then provide the final PPTX.

Required image-generation dependency:

• The visual preview and full-slide generation stages must load and follow the installed `$imagegen` skill.
• Use built-in `image_gen` first when the user does not specify a generation mode.
• Use CLI mode when the user explicitly requests it or when a real built-in attempt is unavailable or fails, but only through the runtime, endpoint, and credential mechanism authorized in the current user's `$imagegen` workflow.
• Do not hardcode a maintainer's workstation path, account name, private endpoint, or credential source. Never display, log, or persist credentials.
• In CLI mode, write generated image files under `outputs/imagegen/` and record method `imagegen_cli_fallback` in `imagegen_manifest.json`.
• Use a Python environment with the packages in `requirements.txt` for PowerPoint assembly and validation.
• Do not replace `$imagegen` with textual visual suggestions, SVG/vector/code-native drawings, HTML/CSS/canvas mockups, manual diagrams, or a generic image-generation placeholder.
• When built-in mode is used, copy the selected generated files from `$CODEX_HOME/generated_images/...` or the workspace into `outputs/imagegen/generated_slides/`, and record method `built_in_image_gen` in `imagegen_manifest.json`.
• If an explicitly selected CLI attempt fails to generate real files, try built-in `image_gen` unless the user asked for CLI only. If the default built-in attempt fails, use CLI only when the current environment authorizes and supports that fallback.
• If neither CLI fallback nor built-in `$imagegen` can generate real image files, stop at that stage and report the incomplete stage. Do not assemble a PPT from non-imagegen substitutes.
• A visual preview generated with `$imagegen` is not enough. Every final slide image recorded in `imagegen_manifest.json` must also be generated with `$imagegen`.
• If CLI fallback fails only for long Chinese prompts, that is not permission to generate text-free backgrounds. First shorten each prompt while preserving the requirement that the final image contains the slide title and key visib