xiaobei-skill-academic-paper-to-ppt

小北在读研 · 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 ![PPT 视觉方案](/absolute/path/visual_preview.png).
• 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.