Automate LibreOffice Impress Presentations

LibreOffice Impress guides presentation creation, editing, conversion, and automation around the native ODP format. It outlines creating decks from scratch or templates, defining slide masters and layouts, inserting text and images, drawing shapes and diagrams, managing speaker notes, and controlling animations and transitions. Automation patterns also address data-driven slide creation and dynamic charts.

The concrete examples focus on launching Impress, converting documents through soffice, connecting Python to a UNO service, and replacing placeholders inside an ODP archive. These are starting patterns for a configured LibreOffice environment rather than a bundled presentation-generation service.

Use this skill when a workflow requires editable ODP source, recurring presentations from a template, batch format conversion, or scripting around LibreOffice. It is relevant when a team needs to preserve a presentation source while distributing converted versions.

Do not assume every listed import or export format has identical behavior in every installed release. Candidate inputs include ODP, PPTX, PPT, and PDF; candidate outputs include ODP, PPTX, PDF, HTML, and SWF. Verify the installed filters and resulting layout. The supplied snippets do not prove preservation of fonts, animations, interactivity, or visual fidelity across conversions.

Inputs include an existing presentation or template, structured replacement content, desired slide layouts, and a target format or output path. Outputs may be ODP files, converted decks, PDF exports, or scripted modifications to slide content. Convert a presentation to PDF in headless mode with:

soffice --headless --convert-to pdf presentation.odp

The UNO example assumes a reachable local LibreOffice socket and uses the presentation document service. The template example unpacks an archive, substitutes placeholders in content.xml, and repackages it. Treat that example as a pattern requiring validation of XML escaping, document structure, command results, and output integrity rather than a complete robust templating engine.

Use slide masters, reusable templates, vector graphics where possible, manageable file sizes, versioned ODP source, and thorough conversion checks. Check font handling for PDF distribution. Visual inspection of the final deck remains necessary when layout matters.

Automation options include the soffice command line and Python UNO. The source additionally names ezodf and odfpy for ODF handling and lists related document and workflow skills. Socket troubleshooting includes restarting LibreOffice; inspect the running session before using a process-wide termination example that could affect open documents.

Clarify the required input, permissions, boundaries, and success criteria before proceeding when any are missing. The intended environment must support the chosen operation.