evylegzhanin/agent-with-sandbox/presentation

Presentations and Slide Decks (python-pptx)

When the user asks for a presentation, slide deck, PowerPoint, or .pptx with plots, charts, figures, visuals, or key insights, the .pptx is the primary artifact.

Load python-scripts via read_skill if you have not already; use code in every write_python_file call, then run_python_file. Each script must include imports, slide logic, and prs.save(...) — no import-only stubs.

Split deck builders before the first write

Deck builders almost always exceed 120 lines and are prone to tool-call truncation. Before the first write_python_file, split into at least two staged files:

• deck_helpers.py — Presentation setup, color constants, add_bg_rect, add_title_bar, and other text/layout helpers (~15–80 lines)
• deck_build.py — from deck_helpers import *; one function per slide section; prs.save("/workspace/out/....pptx") at the end (~40–120 lines)

Stage helpers first with write_python_file, then deck_build.py, then run_python_file("deck_build.py"). Do not send a single monolithic deck script in one tool call.

Building with python-pptx

from pptx import Presentation
from pptx.util import Inches
prs = Presentation()
slide = prs.slides.add_slide(prs.slide_layouts[0])
slide.shapes.title.text = "Executive Summary"
# content slides: layouts[1] for title + body
# charts: slide.shapes.add_picture("/workspace/out/chart.png", Inches(1), Inches(1.5), width=Inches(8))
prs.save("/workspace/out/report.pptx")

Use exact import names (RGBColor, Inches, Pt from pptx.util).

Structure and layout

• Prefer a clear arc: title slide, sections with consistent headings, content slides, then a short summary or takeaways slide.
• Reuse fonts, sizes, and colors across slides for a coherent look.
• When using blank layouts, set title and body text explicitly.

Images and charts

If you generate chart/image files (for example .png), do both:

1. Save the image files under /workspace/out.
2. Insert those files into slides via add_picture(...) before saving the presentation.

• Never skip add_picture silently when a chart path is required — raise FileNotFoundError if missing.
• Do not satisfy a presentation request by leaving plots only as separate files when they belong on slides.

Splitting large decks

Generate and save chart files in one staged script pair, then build the deck in a follow-on pair that uses those paths. Files under /workspace/out persist across calls in the same task.