DeckLingo for PPTX

Translate editable PowerPoint decks into Chinese, English, Japanese, and other target languages while preserving layout, glossary consistency, and editabilit...

Security Scan

The package is internally consistent with a PPTX translation tool: it expects Python, bundles scan/translate scripts, and requires no unrelated credentials — but it will send slide text to an online translator (deep-translator/Google) by default and will overwrite files unless you use dry-run/backups.

Purpose & Capability

Name/description match the provided artifacts: Python scripts, README, glossary samples, and a small requirements.txt that lists lxml and deep-translator, which are appropriate for parsing PPTX XML and performing translations. Declared runtime requirement (python/python3) is proportional to the stated purpose. No unrelated binaries, env vars, or config paths are requested.

Instruction Scope

SKILL.md instructs the agent to run the included scan and translate scripts on local .pptx files. The scripts operate at the XML level inside the PPTX zip, read glossary/skip-pattern files if provided, and can overwrite the input file (it creates backups if translating in-place). They do not access system-wide secrets or unrelated files, but they do transmit text to a network translation service via the deep-translator library (GoogleTranslator) — so slide content will leave the host unless you supply/patch an offline translator. Also note minor path inconsistency in examples (.trae/skills/... vs ./scripts/) but that does not change behavior.

Install Mechanism

There is no complex install spec in the package itself; metadata includes a GitHub repo URL as a download target, and the repo contains only local Python scripts and small assets. requirements.txt pins lxml and deep-translator — both traceable PyPI packages. No arbitrary binary downloads, no URL shorteners or personal IPs. The main install risk is bringing in deep-translator which performs network calls for translation.

Credentials

The skill requests no environment variables or credentials. The scripts do not read environment secrets. The only external dependency is network access for translation (deep-translator/Google) which is proportional to a translation tool but has privacy implications for sensitive slide content.

Persistence & Privilege

always:false and normal autonomous invocation are used. The skill does not request elevated agent/system privileges, does not modify other skills, and does not persist unusual global configuration. It writes/overwrites PPTX files and may create a .bak backup when translating in-place (expected behavior).

Assessment

This package appears to do what it says: parse PPTX XML and translate editable text. Before installing/running: 1) Be aware translations are performed via deep-translator (GoogleTranslator) by default — slide text (potentially sensitive) is sent to third-party translation endpoints. If you need privacy, run an offline translator or remove/change the translator implementation. 2) Use the scan-only (--dry-run or the scan script) mode first and keep backups; the translate script can overwrite the original PPTX (it creates a backup suffix when translating in-place). 3) Install dependencies via pip in a controlled environment (requirements.txt: lxml, deep-translator). 4) Confirm paths in SKILL.md examples match where the skill is installed in your runtime. If any of these points are problematic (e.g., you cannot allow network upload of deck contents), do not run the scripts until you replace the online translator with an offline/local engine.

Use this skill for translation tasks on existing .pptx decks when the output must stay editable and visually close to the source.

It is designed to stay tool-agnostic so the same skill package can be used in Codex-style environments, OpenClaw-style environments, and other agent runtimes that can execute local scripts and read SKILL.md.

Install on ClawHub:

clawhub install decklingo-pptx

Best search phrases for this skill:

• translate powerpoint to chinese
• translate pptx to english
• localize presentation deck
• translate speaker notes in powerpoint
• glossary aware ppt translation

What This Skill Covers

• User-selectable translation target language
• User-selectable source language, including English to Chinese workflows
• User-selectable working/output language for the skill itself
• Translation of editable text in slides, speaker notes, layouts, and slide masters
• Terminology control through glossary files
• Verification that requested source-language text no longer remains in editable text objects
• Scan-only and dry-run workflows before writing output

Real Example Prompts

• Translate this PowerPoint from English to Simplified Chinese and keep all speaker notes editable.
• Convert this Chinese lecture deck into fluent English, but keep file names, URLs, and numbers unchanged.
• Localize this PPTX into Japanese using my glossary and tell me if any source-language text remains in layouts or masters.

When To Use It

• Use it when the source deck must remain editable after translation.
• Use it when you need slides, notes, layouts, or masters translated selectively.
• Use it when repeated terminology should stay stable with a glossary.

When Not To Use It

• Do not use it when the deck text is baked into screenshots or flattened images.
• Do not use it when the user wants a full visual redesign rather than translation.
• Do not use it as a generic document translator for PDFs, DOCX, or websites.

Defaults

• source language: auto
• target language: infer from the request; if not clear, use the most obvious requested language
• english -> chinese is a first-class workflow, not a fallback case
• working/output language: use the user's current language by default
• translation scope: slides on, notes on, layouts off, masters off unless the user requests a full inherited-text cleanup

Keep these separate:

• Target language: the language written into the deck
• Working language: the language used in logs, summaries, and user-facing notes

Workflow

1. Determine:
   • input PPTX path
   • output PPTX path
   • source language
   • target language
   • working language
   • whether notes/layouts/masters should be translated
2. Run the scan script first when the deck is unfamiliar or large.
3. Prefer XML-level translation so the deck remains editable and layout drift stays low.
4. Translate paragraph-sized text instead of isolated run fragments whenever possible.
5. Preserve numbers, dates, URLs, filenames, code snippets, and product names unless translation is clearly needed.
6. Re-scan the result and report:
   • output file path
   • paragraph counts
   • glossary usage
   • any remaining source-language text in editable objects

Scripts

Use the bundled scripts:

python .trae/skills/decklingo-pptx/scripts/scan_pptx_text.py \
  --input "path/to/input.pptx" \
  --source-lang zh \
  --include-notes \
  --include-layouts \
  --include-masters

python .trae/skills/decklingo-pptx/scripts/translate_pptx_text.py \
  --input "path/to/input.pptx" \
  --output "path/to/output.pptx" \
  --source-lang auto \
  --target-lang en \
  --ui-lang zh \
  --include-notes \
  --glossary-file ".trae/skills/decklingo-pptx/assets/glossary.sample.json" \
  --report-file "translation-report.json"

Common Options

• --source-lang: source language code, default auto
• --target-lang: target language code such as en, ja, fr, de, zh-CN
• --ui-lang: language for logs and summaries, usually zh or en
• --include-notes: include speaker notes
• --include-layouts: include slide layouts
• --include-masters: include slide masters
• --glossary-file: JSON glossary mapping source terms to preferred translations
• --skip-pattern-file: regex patterns to protect text like URLs, file names, code identifiers, or custom labels
• --report-file: write a machine-readable JSON report
• --dry-run: inspect and translate in memory without writing a new deck
• --backup-suffix: backup suffix used when translating in place, default .bak

When To Load References

• Read references/glossary-schema.md when you need to create or edit a glossary file.
• Read references/translation-modes.md when choosing whether to include notes, layouts, or masters.
• Read references/platform-compatibility.md when packaging the skill for Codex, OpenClaw, or another agent runtime.

Notes

• Reuse or patch a better project-local translator if the repository already contains one.
• If network translation is required, verify connectivity first.
• If the user asks for design cleanup after translation, pair this skill with a slide-layout skill rather than rebuilding the deck here.
• Treat third-party skills and scripts as untrusted code and review them before enabling.
• Minimal runtime requirements: Python 3.10+, lxml, deep-translator, ZIP read/write access.
• Changelog: see references/changelog.md.