powerpoint
NousResearch/hermes-agent · Agent Skill
使用 python-pptx 函式庫建立、讀取和編輯 PowerPoint (.pptx) 簡報,支援離線檔案操作。
前往安裝 ↓總覽
| 發布者 | |
|---|---|
| 儲存庫 | NousResearch/hermes-agent ↗ |
| 技能資料夾 | powerpoint |
| 星 | 243,171 |
| 附帶檔案 | 1 |
| 授權 | MIT |
| 最近更新 | 2026年8月11日 |
| 連結 | 技能原始碼 ↗ · 儲存庫 ↗ |
Mozgi 檢查
我們在技能檔案中發現的內容。詳細資訊需訂閱。
安裝
技能就是一個含 SKILL.md 的資料夾。選擇你的代理,在專案根目錄的終端機(macOS、Linux 或 Windows 的 Git Bash)執行指令。
把提示貼到 Claude、Codex 或其他助理:它會自行檢查並安裝技能。
Install the “powerpoint” skill from mozgi.io (https://mozgi.io/skills/powerpoint/) for me. 1. Download the archive: https://mozgi.io/skills/powerpoint/download If it fails, take the skill folder from the source: https://github.com/NousResearch/hermes-agent/tree/main/skills/productivity/powerpoint 2. Read SKILL.md and the other files. Check the skill is safe: no hidden commands, no sending data elsewhere, no scripts doing something other than described. If anything looks suspicious, stop and tell me. 3. Put the “powerpoint” folder into your agent's skills folder: .claude/skills/ for Claude Code, .agents/skills/ for Codex, .cursor/skills/ for Cursor, .gemini/skills/ for Gemini CLI. Inside the project if we are in one, otherwise in the home folder (~/.claude/skills/ etc.). 4. Make sure <skills folder>/powerpoint/SKILL.md exists. 5. Briefly tell me what this skill does and offer to try it on my task. If you cannot do a step yourself, tell me what to click or type.
git clone --depth 1 --branch main https://github.com/NousResearch/hermes-agent.git /tmp/hermes-agent mkdir -p .claude/skills cp -r /tmp/hermes-agent/skills/productivity/powerpoint .claude/skills/powerpoint
重新啟動 Claude Code — 技能就會出現在清單中,手動呼叫:/powerpoint。要套用到所有專案,請放在 ~/.claude/skills。
git clone --depth 1 --branch main https://github.com/NousResearch/hermes-agent.git /tmp/hermes-agent mkdir -p .agents/skills cp -r /tmp/hermes-agent/skills/productivity/powerpoint .agents/skills/powerpoint
Codex 會從目前資料夾往上到儲存庫根目錄,在 .agents/skills 中尋找技能;用 /skills 或 $powerpoint 呼叫。所有專案:~/.agents/skills。
git clone --depth 1 --branch main https://github.com/NousResearch/hermes-agent.git /tmp/hermes-agent mkdir -p .cursor/skills cp -r /tmp/hermes-agent/skills/productivity/powerpoint .cursor/skills/powerpoint
Cursor 啟動時會載入技能;在 Agent 聊天輸入「/」呼叫。Cursor 也會讀取 .claude/skills 與 .agents/skills。所有專案:~/.cursor/skills。
git clone --depth 1 --branch main https://github.com/NousResearch/hermes-agent.git /tmp/hermes-agent mkdir -p .gemini/skills cp -r /tmp/hermes-agent/skills/productivity/powerpoint .gemini/skills/powerpoint
任務符合時,Gemini CLI 會提議啟用技能,由你確認。所有專案:~/.gemini/skills。
安裝前請先檢視 SKILL.md 與相關檔案。點擊檔案即可預覽。
SKILL.md 內容
作者原文 · 唯讀Powerpoint Skill
Create, inspect, and edit PowerPoint (.pptx) presentations using the
python-pptx library. Five helper scripts cover deck creation from a JSON
spec, structured read-back, in-place edits, template-driven brand decks,
and slide rendering — all offline, no PowerPoint installation required.
When to Use
- The user asks to build a slide deck, report presentation, or pitch deck.
- You need to extract text, notes, tables, chart data, or images from a
.pptx someone shared.
- You need to update an existing deck: replace text, refresh or patch
chart data, swap a logo, duplicate/remove/reorder slides, set
backgrounds, footers, hyperlinks, or speaker notes.
- You must produce an on-brand deck from a company .pptx template.
- Do NOT use this for .ppt (legacy binary) files — convert them first with
soffice --convert-to pptx old.ppt if LibreOffice is available.
Prerequisites
- Python 3.10+ with
python-pptxinstalled
(pip install python-pptx).
- Optional: LibreOffice (
soffice) plus poppler (pdftoppmor
pdftocairo) for rendering slides to PNGs and for PDF export.
pptx_render.py detects both with shutil.which and degrades
gracefully (reports {"rendered": false, "missing": [...]}, exit 0)
when absent — all create/read/edit operations work without them.
- Check availability via
terminal:
python -c "import pptx; print(pptx.__version__)" and which soffice pdftoppm.
How to Run
All scripts live in scripts/, take --help, print JSON to stdout, and
exit non-zero on failure. Run them with terminal:
python scripts/pptx_create.py deck.json out.pptx
python scripts/pptx_read.py deck.pptx --outline # full JSON outline
python scripts/pptx_read.py deck.pptx --notes # speaker notes
python scripts/pptx_read.py deck.pptx --images ./img # export pictures
python scripts/pptx_edit.py deck.pptx --replace-text "Old Corp" "New Corp"
python scripts/pptx_edit.py deck.pptx --chart-data update.json
python scripts/pptx_edit.py deck.pptx --duplicate-slide 2
python scripts/pptx_edit.py deck.pptx --remove-slide 3 --move-slide 2 0
python scripts/pptx_from_template.py brand.pptx out.pptx --values vals.json
python scripts/pptx_render.py deck.pptx --outdir ./render # slide PNGs
Author JSON specs with write_file; inspect script output and generated
JSON with read_file.
Quick Reference
| Task | Command |
|---|---|
| New deck from spec | pptx_create.py spec.json out.pptx |
| 16:9 vs 4:3 | "slide_size": "16:9" or "4:3" in the spec |
| Outline as JSON | pptx_read.py deck.pptx --outline |
| Export images | pptx_read.py deck.pptx --images DIR |
| Replace text | pptx_edit.py deck.pptx --replace-text OLD NEW |
| Replace chart data | pptx_edit.py deck.pptx --chart-data spec.json |
| Patch one series | same flag, spec with "ops" (see below) |
| Swap picture | pptx_edit.py deck.pptx --swap-image N NAME new.png |
| Duplicate slide | pptx_edit.py deck.pptx --duplicate-slide N |
| Remove slide | pptx_edit.py deck.pptx --remove-slide N |
| Reorder slide | pptx_edit.py deck.pptx --move-slide FROM TO |
| Slide background | pptx_edit.py deck.pptx --set-background N RRGGBB |
| Hyperlink runs | pptx_edit.py deck.pptx --hyperlink N TEXT URL |
| Slide number on | pptx_edit.py deck.pptx --enable-slide-number N |
| Footer text | pptx_edit.py deck.pptx --set-footer N TEXT |
| Set notes | pptx_edit.py deck.pptx --set-notes N TEXT |
| Append notes | pptx_edit.py deck.pptx --append-notes N TEXT |
| Fill template | pptx_from_template.py tpl.pptx out.pptx --values v.json |
| Render slide PNGs | pptx_render.py deck.pptx --outdir DIR |
Procedure
1. Create a deck
Write a JSON spec (see pptx_create.py --help for the full format), then
run pptx_create.py. Per slide you can set: layout (title,
title_content, section, two_content, title_only, blank), title,
subtitle, bullets (strings, or dicts with level 0-4, size pt,
bold, italic, font, color hex, link URL for a hyperlink),
background (solid hex), footer (text; enables the layout's footer
placeholder), slide_number (true; enables the layout's slide-number
placeholder), images (path + left/top/width/height in inches), tables
(rows as list-of-lists), shapes (rectangle, rounded_rectangle, oval,
diamond, right_arrow, chevron, with fill hex + optional text),
charts (bar, bar_h, line, pie with categories + series), and
notes (speaker notes).
2. Read a deck
pptx_read.py deck.pptx --outline returns slide size, layout inventory,
and per slide: layout name, all shape texts, table cells, image inventory
(filename/ext/bytes), chart categories/series/values, and speaker notes.
Use --images DIR to dump embedded pictures to files, then
vision_analyze on any exported image if you need to see its content.
3. Edit a deck
pptx_edit.py combines operations in one pass; use --output to keep the
original. Text replacement scans slide shapes, table cells, and notes.
Image swap retargets the picture's relationship id so position and size
are preserved. Slide removal drops the relationship and the <p:sldId>
entry; reorder moves the <p:sldId> element within <p:sldIdLst>
(python-pptx has no public API for either — the script does the XML-level
work). --duplicate-slide N appends an independent deep copy of slide N:
shape XML plus image/media/hyperlink relationships are cloned and rIds
remapped, so editing the copy never touches the original. Chart slides
are refused (see Pitfalls). --set-notes/--append-notes edit speaker
notes; --set-background, --hyperlink, --enable-slide-number, and
--set-footer handle deck polish.
Chart updates take a JSON spec via --chart-data. Full replace:
{"slide": 0, "chart": 0, "categories": [...], "series": {...}}. For
surgical edits, pass "ops" instead — a list of
{"op": "update_series", "name": ..., "values": [...]},
add_series, remove_series, rename_category (from/to or
index), and set_title. python-pptx can only swap a chart's entire
dataset (replace_data), so ops are implemented as read-existing →
modify → replace; the per-part UX is a wrapper, and any chart data not
expressible as categories + numeric series will be normalized by the
round-trip.
4. Build from a template
pptx_from_template.py opens a brand .pptx, replaces every
{{token}} from a values JSON across slides/tables/notes, and can append
new slides that use the template's own layouts (by layout name or index)
so they inherit the master's fonts and colors. Tip: to start from a
template with zero slides, delete existing ones afterward with
pptx_edit.py --remove-slide.
5. Visual verification
pptx_render.py deck.pptx --outdir ./render converts the deck to PDF
with soffice --headless and splits it into one PNG per slide with
pdftoppm (or pdftocairo). Output JSON lists the PNG paths — review
each with vision_analyze. When either tool is missing the script exits
0 with {"rendered": false, "missing": [...]} and guidance; fall back to
the JSON outline from pptx_read.py, which verifies content and
structure, just not visuals.
Converting to PDF
If LibreOffice is installed, export the finished deck to PDF directly:
soffice --headless --convert-to pdf --outdir ./out deck.pptx
The output lands at ./out/deck.pdf. Fonts not installed on the host are
substituted, so render-verify (Procedure step 5) before shipping the PDF.
There is no offline pure-Python .pptx→PDF path; if soffice is absent,
say so rather than approximating.
Pitfalls
- Run splitting: PowerPoint fragments paragraph text into runs at
spell-check and edit boundaries. --replace-text first merges adjacent
runs whose formatting is identical, so matches split across such runs
are replaced with formatting fully preserved. Only when a match spans
*genuinely differently-formatted* runs is the paragraph rewritten with
the first run's formatting — verify those slides after replacement.
- Chart slides cannot be duplicated: each chart relationship embeds a
separate XLSX workbook part; cloning that graph reliably is not
supported, so --duplicate-slide refuses chart slides cleanly instead
of corrupting the deck. Rebuild the chart on a new slide instead.
External-hyperlink and image/media rels are carried over; layout and
notes rels are recreated fresh.
- Chart ops are a wrapper: python-pptx replaces the whole dataset;
"ops" round-trips existing plot data through replace_data, and
changing chart *type* is not possible.
- Reordering is XML-level: python-pptx has no supported reorder API.
--move-slide manipulates <p:sldIdLst> directly; safe for ordinary
decks but re-read the deck afterward to confirm.
- Copying slides between decks is unsupported — duplication works
only within one deck, where layouts and masters are shared.
- Footer/slide-number enablement copies the placeholder from the slide's
layout; on layouts without those placeholders, --set-footer fails
with a clear message (add a textbox instead).
- Hyperlinks apply to whole runs;
--hyperlinklinks every run
containing the given text on that slide.
- The default python-pptx template is 4:3; the create script sets 16:9
unless the spec says otherwise. Custom templates keep their own size.
- Layout indexes vary by template. For brand templates, list layout names
first: pptx_read.py template.pptx --outline (layouts_available).
slide.shapes.titleis None on blank layouts — the create script
handles this, but remember it when writing ad-hoc python-pptx code.
- Always pass
encoding="utf-8"when writing spec files; tokens like
{{city}} may be filled with non-ASCII values.
Verification
1. After any create/edit, run pptx_read.py OUT.pptx --outline and check
slide count, texts, tables, notes, and chart values match intent.
2. --images DIR then file-size check confirms pictures embedded.
3. Render every slide with pptx_render.py deck.pptx --outdir ./render
and review each PNG with vision_analyze — this catches overlapping
shapes, truncated text, and color problems the outline cannot. If the
render tools are missing, the script says so; rely on the outline.
4. The bundled test suite is the full contract:
python -m pytest tests/ -q (requires python-pptx + pytest).
常見問題
powerpoint 技能有什麼用途?
使用 python-pptx 函式庫建立、讀取和編輯 PowerPoint (.pptx) 簡報,支援離線檔案操作。
如何安裝 powerpoint?
打開本頁的「安裝」區塊並選擇你的代理 — Claude Code、Codex、Cursor 或 Gemini CLI:那裡有把技能資料夾複製到正確位置的現成指令。也可以複製「透過助理」分頁中的提示,讓助理自行檢查並安裝技能。
powerpoint 適用哪些 AI 模型?
技能是純 Markdown 指示(Agent Skills 格式),因此 powerpoint 適用任何讀取 SKILL.md 的代理:Claude Code、Codex、Cursor、Gemini CLI、GitHub Copilot、OpenCode 等。只有在任務符合技能描述時,模型才會載入指示。
powerpoint 是免費的嗎?
此技能由 NousResearch 公開發布,採用 MIT 授權。技能本身免費 — 你只需向 AI 供應商支付實際使用的 token 費用。
安裝技能安全嗎?
技能是代理會遵循的指示,安裝前請閱讀 SKILL.md 及相關檔案。技能資料夾中的腳本只有在代理執行時才會運行 — 留意它的動作,不要授予多餘權限。
技能和 MCP 伺服器或外掛有何不同?
MCP 伺服器或外掛為模型提供新工具 — 會執行並回傳結果的程式碼。技能提供的是知識與流程:如何處理任務、要遵循哪些步驟、好的成果長什麼樣子。它不需要伺服器或 API 金鑰。