Image-to-Editable-PPT Skill

Convert slide images, PDFs, and image-based PPTX files into editable PowerPoint decks.

Stars
★ 3k
Last updated
1mo ago
License
MIT
Primary language
Python

At a glance

How it runs
Agent plugin / skill
Works with
Platform-specificCodex
Cost
Free software; you pay for model usage
Setup effort
Medium · a few setup steps
You'll need
Baidu PaddleOCR-VL Tokenimage_gen.imagegen or Codex OAuthShell / CLINetwork accessLocal filesystem
Typical use
Convert a single slide image to an editable PowerPoint for adjusting text and element positions.
Not a fit if
  • Users who want to generate a brand-new deck: this only rebuilds image-based slides
  • Non-Codex environments without Codex OAuth: multi-page jobs need page worker dispatch

What does this agent do, and when should you use it?

image-to-editable-ppt-skill is a Codex skill for converting slide images, PDFs, and image-based PPTX files into editable PowerPoint presentations. It normalizes input into per-page tasks and rebuilds them as .pptx: readable text is restored as native text boxes, simple geometry as PowerPoint shapes, and complex visuals are kept as separate image assets with source records. The skill uses a multi-agent collaborative workflow, supporting single-page and multi-page inputs, with multi-page inputs dispatched to page workers for parallel processing. It automatically installs the editppt CLI tool and prefers Codex's built-in image_gen.imagegen for image generation/editing, falling back to third-party APIs when needed. Text correction relies on Baidu PaddleOCR-VL, requiring a free Token. The skill recommends running with full access permissions in Codex due to long execution times and automated steps. Output is always a .pptx file, preserving original slide notes.

The skill performs the following operations: it creates a dedicated task directory and normalizes input into pages/page_NNN/source.png files; based on page count, single-page inputs are rebuilt locally by the main agent, while multi-page inputs are dispatched to page workers according to max_concurrent_pages; page rebuilders complete page reconstruction, self-check, and corrections, creating manifests; finally, the main agent uses editppt run finalize to rebuild the final .pptx in page order, copying slide notes and running deck validation. Image generation and editing prefer Codex's built-in image_gen.imagegen; if unavailable or error, it falls back to the editppt image CLI (using Codex OAuth or OpenAI-compatible API). Text correction calls Baidu PaddleOCR-VL to generate per-page text annotations (bounding boxes, font sizes, groups), improving text restoration accuracy. The output directory structure includes input, final, pages subdirectories, and the final .pptx file.

  1. Convert a single slide image to an editable PowerPoint for adjusting text and element positions.
  2. Convert multiple images or multi-page PDFs into a single multi-page .pptx file.
  3. Convert image-based PPT pages into a more easily editable .pptx, preserving original slide notes.
  4. Replicate a single-page visual design while keeping text editable.
  5. Compare source images with output pages to locate missing text, misalignments, or asset gaps.

How do you install or deploy this agent?

To install the skill in a Codex environment, use the following command:

Install the image-to-editable-ppt skill from https://github.com/ningzimu/image-to-editable-ppt-skill

After installation, the skill automatically installs the editppt CLI tool. To enable text correction, obtain a free Access Token from Baidu AI Studio at https://aistudio.baidu.com/account/accessToken. If a third-party image API fallback is needed, provide the service details and the AI will configure credentials in the user-level config file ~/.editppt/config.yaml (Windows: %USERPROFILE%\.editppt\config.yaml).

How do you use this agent?

In Codex, use the $image-to-editable-ppt directive with image, PDF, or .pptx file paths, for example:

$image-to-editable-ppt Convert this image to an editable PPT.
$image-to-editable-ppt Convert <path-to-deck.pdf> to an editable PPT.

The skill automatically handles task directory creation, page worker dispatch (using multi-agent mechanisms), OCR correction, image asset generation, and final .pptx generation. The output file is located in the final directory.

What are this agent's strengths and limitations?

Pros
  • Restores text as native text boxes, preserving editability;
  • Supports multiple input formats (images, PDFs, image-based PPTs);
  • Parallel processing of multi-page inputs via page workers improves efficiency;
  • Automatically installs required CLI tools, reducing manual setup.
Limitations
  • Dependent on the Codex environment and not directly usable on other platforms;
  • Recommended to run with full access permissions; otherwise frequent approval interruptions may occur;
  • Complex visual elements (e.g., photos, illustrations) are only kept as separate image assets, not guaranteed internally editable;
  • High conversion cost; a 10-page PPT may consume significant tokens and up to 5 hours of quota.

How does this agent compare with similar options?

Unlike codex-ppt-skill, which generates new PPTs from articles, reports, outlines, or ideas, this skill focuses on converting existing images/PDFs/image-based PPTs into editable .pptx files.

Key facts side by side with the most closely related agents.

Agent Source review Form / cost Stars Updated Language Full support on
Image-to-Editable-PPT Skill This agent 53 · Major gaps Agent plugin / skillFree + model costs ★ 3k 1mo ago Python Codex
Dashi PPT Skill — AI-Powered Presentation Generator 41 · Major gaps CLIFree + model costs ★ 9.7k 1mo ago JavaScript Codex · Claude Code
ReelMimic Style-Mimicking Video Studio 50 · Major gaps — ★ 3.6k today JavaScript Codex · Claude Code
Paper2Poster 28 · Major gaps CLIFree + model costs ★ 4k 4mo ago Python Codex · OpenAI API

How does FollowAgents rate this agent?

FollowAgents source review · FARS-2.1
Major gaps
53/ 100 5-point scale 2.7 / 5
This review covers the source as of Aug 09, 2026. The project has shipped 2 stable release(s) since, which have not been re-reviewed. The score and verdict describe the reviewed version only. Recent releases ↓
Trust 12/29
Reliability 8/14
Adaptability 12/18
Convention 11/18
Effectiveness 7/13
Verifiability 3/8
Why each dimension lost points
Trust12 / 29 · 2.1/5

Evidence: README explicitly requires full access and describes OCR, image generation/editing, file I/O, subagent dispatch, but no least-privilege option; user confirmation: README mentions AI asks for OCR token, but not all external calls; data flow transparency: README details input normalization, output structure, steps, but no data flow diagram; sensitive data: API keys stored in user-level config with masking, but no encryption; dependency security: no dependency list or vulnerability scan; external effects: third-party APIs called, but data scope not specified; rollback: no rollback mechanism; source attribution: asset provenance mentioned, but not all outputs. Deductions: lack of least privilege, user confirmation, dependency security, rollback evidence.

Reliability8 / 14 · 2.9/5

Evidence: README and tests show CLI design and coverage for concurrency, formula rendering, backend selection, but no full test results; dependency availability: external OCR token and image backend required, but no availability guarantees; failure messages: error handling mentioned, but limited examples. Deductions: dependency availability not fully addressed, failure message evidence limited.

Adaptability12 / 18 · 3.3/5

Evidence: README clearly defines use cases (images, PDFs, image-based PPT to editable PPT), distinguishes single-page vs multi-page; capability boundaries clear (no new PPT generation, complex visuals as assets); trigger precision: usage examples provided; environment fit: requires skill loading, file I/O, CLI execution, but not detailed agent compatibility. Deductions: environment fit details insufficient.

Convention11 / 18 · 3.1/5

Evidence: README provides detailed information architecture (repo structure, output structure); install notes simple; naming stable (CLI commands, file naming); examples and FAQ via docs link; known limitations listed; MIT license; CHANGELOG.md and versioning present; maintenance responsibility: support channels provided, but maintainer identity not explicit. Deductions: maintenance responsibility not explicit.

Effectiveness7 / 13 · 2.7/5

Evidence: Output is editable PPTX, README shows conversion examples; marginal value: addresses image-to-editable PPT need, but high cost (token consumption); cost-benefit: README warns high cost, recommends Pro users, but no specific cost data. Deductions: cost-benefit evidence insufficient.

Verifiability3 / 8 · 1.9/5

Evidence: README claims (conversion quality, cost) supported by examples and warnings, but no reproducible verification steps; cross-source: external article and docs mentioned, but no independent verification; fact vs inference: known issues vs expected outcomes distinguished, but some claims (e.g., 'not 100% replication') are inferences. Deductions: verification evidence insufficient.

Risks and how to mitigate them
  • This skill requires full access and may perform OCR, image generation/editing, file I/O, subagent dispatch; ensure trusted environment.
  • Third-party API credentials (e.g., OCR token, API key) are stored in user-level config; ensure config file permissions are secure.
  • Conversion cost is high and may consume significant tokens; use cautiously based on actual needs.
Evidence confidence: Low Reviewed Aug 09, 2026 Reviewed revision fb869763127f New commits since this review; the score may not cover them
See the full review method →

Recent releases

Latest entries from the project's GitHub Releases. Notes are quoted from upstream as written, not rewritten or tested by FollowAgents.

  1. v0.4.0
    Release notes excerpt
    Features - Build native PowerPoint tables with editable cells, proportional row and column sizing, rectangular merges, and shared build, preview, and validation support. (#38) Improvements - Reuse verified page assets during local recovery and load worker references by task instead of requiring every reference in full. Preserve OCR setup and blocked-OCR user interaction. (#38) …
    View on GitHub ↗
  2. v0.3.3
    Release notes excerpt
    Features - Build native editable Bézier paths with dash styles and endpoint arrows, keeping each continuous curve in one PowerPoint object. (#36) Fixes - Emit valid slide-size metadata and complete theme style lists to avoid PowerPoint repair prompts. (#36) - Render diagonal and curved dashed strokes in previews and validate path contracts, stroke styles, and declared logical-line uniqueness. (#36) Documentation - Specify structural curve granularity, document curve editing, and distinguish editable paths from data-linked charts. (#36) …
    View on GitHub ↗
  3. v0.3.2
    Release notes excerpt
    Features - Prefer the agent built-in image_gen.imagegen tool for image generation and editing, with explicit fallback to Codex OAuth and then an OpenAI-compatible API only for defined failure conditions, while recording the actual producing backend. (#22) Fixes - Scope editppt image process-sheet intermediate images and split reports by job id, and reject an existing alpha output before copying a new source sheet. (#22) …
    View on GitHub ↗

FAQ

Can this skill run without a Baidu OCR Token?
Yes, but it falls back to a built-in offline detector that only performs geometric measurements (knows text location and size, but not content), reducing text restoration quality. We recommend obtaining the free Token for best results.
How are pages assigned for multi-page inputs?
Multi-page inputs are dispatched to page workers according to the max_concurrent_pages concurrency slots. Page workers are subagents, and this mechanism must be supported, otherwise it won't work.
Does it work in non-Codex environments like Claude Code or OpenClaw?
It supports them, but you need to configure a third-party API fallback (e.g., OpenAI-compatible API), and the built-in image_gen.imagegen may not be available, relying on CLI fallback or external APIs.
Can it 100% replicate the original page?
No, there is no guarantee of 100% replication. Some image elements and text positions may have slight offsets, especially for complex visual elements.
View on GitHub ↗ Install ↓

Related agents