Figma Context MCP
Give your coding agent access to your Figma data. Implement designs in any framework in one-shot.
Speaker is a Codex skill project for academic presentations: read real.pptx, combine text extraction, PPTX structure parsing, page-by-page rendering, OCR, and visual review to generate page-by-page speaker notes, and write a clean version of the lecture into the PowerPoint comment area.
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/skills/ai272-speaker)在同一工作中把 AI 连到服务的 MCP
Give your coding agent access to your Figma data. Implement designs in any framework in one-shot.
draw.io diagrams your AI agent draws on a live browser canvas that you can also edit by hand
Create, inspect, validate, and save editable 3D building scenes with Pascal's MCP server.
同类工作,排序与 Skill 列表相同
| 本项 speaker | impeccable | diagram-design | frontend-slides | guizang-ppt-skill | |
|---|---|---|---|---|---|
| 作者 | AI272 | pbakaus | cathrynlavery | zarazhangrui | op7418 |
| Skill 数 | 1 | 1 | 1 | 1 | – |
| GitHub 星标 | 479 | 110,690 | 67,371 | 32,358 | 29,835 |
| 最近代码更新 | 2026年6月23日 | 2026年11月16日 | 2026年11月13日 | 2026年6月24日 | 2026年10月30日 |
| 许可证 | – | Apache-2.0 | MIT | MIT | AGPL-3.0 |
AI272 提供的 1 个 Skill(指令集),AI 读取后照做 · 不是 MCP server
MCP = 手
把 AI 连到外部服务或数据,例如读取 Notion 或开发票。需要有程序或服务器在运行。
Skill = 手册
教 AI 怎么做某项工作的文本文件,不连接任何服务。
有些会重叠:少数 Skill 带有调用工具的脚本,少数 MCP 只提供知识。请从你想完成的工作出发。
Claude CodeCodex
依据开发者 README 和 repo 中的文件夹
GitHub account AI272 (person), 2 years old
★ 479 stars, few users so far · code last changed 2026年6月23日
6 scripts that can run on a computer: scripts/inject_notes.py, scripts/read_slides.py, scripts/render_slides.py, scripts/vision_review.py and 2 more
No internet calls found in the scripts
No hooks or writes to machine settings found
Checked automatically from the repo files at commit a7b5b9d (read only, nothing was run). Not a safety guarantee: read it and decide for yourself
第一步:你用哪个 AI?
选择你用的应用,本页只显示该应用的安装方法
This skill has no license, so we do not hand out a ZIP from our site. Download it from GitHub and arrange the folder yourself, or use "Let the AI install it" above, which is easier
Download from GitHub (whole repo) ↗
Unzip it, then zip only the ppt-speech-writer folder again. The ZIP must have a ppt-speech-writer folder with SKILL.md at the top level, no loose files
+Create skillUpload a skillpick ppt-speech-writer.zip
SettingsCapabilitiesCode execution and file creation
Turn on Code execution and file creation first (newer menus: Create and edit files) · personal plans: Settings → Capabilities · Team/Enterprise: an admin turns it on under Organization settings → Plugins & skills · every plan, including Free
Upload once; it works in claude.ai and Claude Desktop, and in recent Claude Code signed in with a Claude account (not with an API key)
Cowork and cloud sessions use the skills turned on in your claude.ai account, not ~/.claude/skills on your computer (Claude Desktop scheduled tasks run locally and still load it)
Checked against official docs 2026年11月12日 · Source: support.claude.com, support.claude.com, code.claude.com
复制这句话,粘贴到 Claude Code 的对话中
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
重新打开 Claude Code,输入 /ppt-speech-writer,或直接提出相关任务,Claude 会自动选用
Checked against official docs 2026年11月12日 · Source: code.claude.com
Skill 是 AI 会照做的指令。安装前先阅读文件,只安装可信开发者的 Skill。
Mac:按 Command+空格输入 Terminal · Windows:下方命令在 PowerShell 中无法使用,请改用上方的“让 AI 帮你安装”
这条命令把 repo 下载到临时文件夹,只复制含 SKILL.md 的文件夹
正在检查命令 · 通过后才会显示复制按钮
ChatGPT 桌面应用内置 Codex,Codex 从 ~/.agents/skills 文件夹读取 Skill
在 ChatGPT 桌面应用中打开 Codex,把这句话粘贴到对话中
The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
把 ppt-speech-writer 文件夹放到 ~/.agents/skills/ppt-speech-writer
~ 是你的主文件夹($HOME)
Skill 是 AI 会照做的指令。安装前先阅读文件,只安装可信开发者的 Skill。
Mac:按 Command+空格输入 Terminal · Windows:下方命令在 PowerShell 中无法使用,请改用上方的“让 AI 帮你安装”
这条命令把 repo 下载到临时文件夹,只复制含 SKILL.md 的文件夹
正在检查命令 · 通过后才会显示复制按钮
Checked against official docs 2026年11月15日 · Source: learn.chatgpt.com
不能使用你自己安装的 Skill,只能使用目录中插件自带的 Skill
想在 ChatGPT 中使用这个 Skill,请按上面的方法使用 ChatGPT 桌面应用
Checked against official docs 2026年11月15日 · Source: learn.chatgpt.com
复制这句话,粘贴到 Codex 的对话中 · 适用于 ChatGPT 桌面应用中的 Codex、Codex CLI 和 IDE 扩展
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Codex 会自动发现新安装的 Skill;如果没有出现,请重启 Codex · 使用方法:在 ChatGPT 中输入 @ 并选择 Skill · 在 Codex CLI 或 IDE 扩展中运行 /skills,或输入 $ 加 Skill 名称
Checked against official docs 2026年11月15日 · Source: learn.chatgpt.com
Skill 是 AI 会照做的指令。安装前先阅读文件,只安装可信开发者的 Skill。
Mac:按 Command+空格输入 Terminal · Windows:下方命令在 PowerShell 中无法使用,请改用上方的“让 AI 帮你安装”
这条命令把 repo 下载到临时文件夹,只复制含 SKILL.md 的文件夹
正在检查命令 · 通过后才会显示复制按钮
复制这句话,粘贴到 Cursor 的对话中
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
在 Cursor 的 Agent 聊天中输入 / 并选择 ppt-speech-writer
Checked against official docs 2026年11月12日 · Source: cursor.com
Skill 是 AI 会照做的指令。安装前先阅读文件,只安装可信开发者的 Skill。
Mac:按 Command+空格输入 Terminal · Windows:下方命令在 PowerShell 中无法使用,请改用上方的“让 AI 帮你安装”
这条命令把 repo 下载到临时文件夹,只复制含 SKILL.md 的文件夹
正在检查命令 · 通过后才会显示复制按钮
适用于其他能读取 Skill 的应用。这句话列出了 Claude Code、Codex 和 Cursor 的路径,AI 会按你的应用选择 · Copy this sentence into the app’s chat
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Checked against official docs 2026年11月12日 · Source: code.claude.com, learn.chatgpt.com, cursor.com
其他支持 Agent Skills 的应用(如 Gemini CLI、GitHub Copilot)使用不同文件夹,请查看该应用的指南,再把含 SKILL.md 的文件夹复制过去。
已于 2026年11月11日 对照 Claude Code、Codex 和 Cursor 官方指南核实 skill 文件夹
以下文字来自开发者的 repo,不是 PopNx MCP 的指令
显示前 8,000 个字符 · 在 GitHub 打开完整文件
---
name: ppt-speech-writer
description: Read a real .pptx using text extraction, OOXML inspection, slide rendering, OCR, visual inventory, and vision-capable screenshot review; then write academic speaker notes grounded in every visible slide element, generate a complete display-version document, and inject clean notes into the PowerPoint notes pane. Use when the user wants speaker notes, presenter notes, a speech script, narration, or annotated notes for an existing PowerPoint deck, especially when slides contain images, charts, tables, SmartArt, axes, legends, or screenshot text.
---
# PPT Speech Writer
You are a senior academic presentation coach. This skill writes slide-by-slide speaker notes for an existing `.pptx`, grounded in the actual visible deck. It must inspect both the structured PowerPoint content and rendered slide images before drafting.
## Grounding Contract
Do not rely on text boxes alone. A slide is considered read only after these evidence sources have been checked:
1. Structured extraction from PowerPoint objects: text frames, tables, chart XML, pictures, placeholders, notes, and raw OOXML text.
2. Rendered slide screenshots, one image per slide.
3. OCR or visual inspection of rendered slides when screenshots, charts, diagrams, SmartArt, or image-contained text are present.
4. A visible-element inventory for every slide.
5. Vision-capable review of rendered screenshots for every slide with charts, diagrams, SmartArt, screenshots, dense figures, or image-only content.
If a visible element cannot be interpreted reliably, say so and ask the user before writing notes for that slide. Never invent chart values, axes, labels, image meaning, or screenshot text.
## Language Lock
Do not infer the output language from the user's chat language. Before writing any notes, explicitly confirm exactly one output language:
- English
- Chinese
- same as the deck language
- another user-specified language
Never draft speaker notes, display notes, glossary entries, timing-table labels, transitions, coverage notes, or injected clean notes until the output language is confirmed.
Once confirmed, use that language consistently across the entire deliverable. Technical terms may remain in their canonical form, such as `PPO`, `AUROC`, `PowerPoint`, `SmartArt`, or dataset names, but sentence grammar, explanations, labels, table headers, and transitions must follow the selected language.
If the selected language is English:
- Write all prose, transitions, labels, glossary definitions, timing-table headers, and coverage notes in English.
- If a slide contains Chinese or Japanese text, quote only the necessary original term and immediately explain it in English.
- Do not write mixed sentences such as "This model 说明了 robustness."
If the selected language is Chinese:
- Write all prose, transitions, labels, glossary definitions, timing-table headers, and coverage notes in Chinese.
- Keep standard technical names in English only when they are the canonical term.
- Do not write mixed sentences such as "这个 model shows strong robustness."
- Embed English technical terms naturally in Chinese syntax, for example: "`AUROC` 用来衡量模型区分正负样本的能力。"
## Slide Prose Style
Do not begin slide notes by describing the slide object. Begin with the claim, implication, finding, method role, or argument step.
Banned English openings:
- "This slide shows..."
- "This slide presents..."
- "This slide explains..."
- "On this slide..."
- "Here we can see..."
- "The slide is about..."
Banned Chinese openings:
- "这一页展示了..."
- "这一页说明了..."
- "这一页主要讲..."
- "在这一页中..."
- "我们可以看到..."
- "这页是关于..."
Preferred pattern:
- Weak: "This slide shows the optimization setup."
- Strong: "The experiments use a fixed optimization protocol so later comparisons stay controlled."
- Weak: "这一页展示了实验设置。"
- Strong: "实验设置被固定下来,是为了保证后续结果比较具有可解释性。"
Write speaker notes as a coherent oral argument, not as captions for slides. Each page should open with a content-level thesis sentence, then explain the visible evidence that supports it.
## Timing And Pacing Model
Speaker notes must fit the spoken duration when read aloud at a realistic pace, with pauses. Do not treat raw word count as speaking time. Plan against pause-adjusted rates, then verify the total against the clock.
### Planning rates (pauses already absorbed)
These rates already account for natural pauses, breaths, and emphasis. Use them as the default budget:
| Output language | Planning rate | Notes |
|-----------------|---------------|-------|
| English | 110 words/min | Academic delivery. Range 100–130. Use 100 for dense or non-native delivery. |
| Chinese | 165 字/min | Academic delivery. Range 150–180. Count Chinese characters, not words. |
Calibration rule: if the speaker says a previous talk ran long, trust the measured pace over the default. Example: a 15-minute talk that actually took 30 minutes ran at `1800 ÷ 30 = 60` effective words per minute. When the speaker reports such a history, recompute with their real rate instead of the table default.
### Reserve time before budgeting words
Do not spend the whole clock on words. From the target duration, subtract:
- Slide transitions: about 3 seconds per slide.
- Deliberate `[PAUSE]` markers: about 1.5 seconds each.
- A global safety buffer of 10–15% for audience reactions, demos, and overruns.
Budget formula for a talk of `T` minutes across `N` slides:
```text
gross_seconds = T * 60
reserved = 3 * N + 1.5 * pause_count + 0.12 * gross_seconds
usable_seconds = gross_seconds - reserved
english_word_budget = usable_seconds / 60 * 110
chinese_char_budget = usable_seconds / 60 * 165
```
Worked example — 15-minute English talk, 12 slides, ~24 planned pauses:
```text
gross_seconds = 900
reserved = 36 (transitions) + 36 (pauses) + 108 (12% buffer) = 180
usable_seconds = 720
word_budget = 720 / 60 * 110 ≈ 1,320 words
```
So a 15-minute English talk targets roughly 1,300–1,400 spoken words, not 1,800. The earlier 1,800-word draft was about a third over budget, which is exactly why it overran. Apply the same arithmetic with the Chinese rate for a Chinese talk.
### Per-slide budget
Distribute the total budget by content weight, not evenly. A title or section divider may take 30–50 words; a dense results slide may take 150–180. Record each slide's target in the timing table `budget` field and the actual count in `word_count`, and the number of `[PAUSE]` markers in `pauses`. If a slide's `word_count` exceeds its `budget`, compress the prose or recommend splitting the slide. Never let total `word_count` exceed the computed budget.
### Writing to the budget in both languages
- Keep spoken sentences short, under 20 words. 中文每句也尽量短,便于换气。
- Place `[PAUSE]` after a thesis sentence or before a key number, not at random.
- Do not pad to hit a budget. A slightly short talk is safer than an overrun.
- Compute the Chinese and English drafts against their own language rate. Do not reuse the English word count as the Chinese character count; the same idea is usually fewer characters in Chinese than words in English.
## Required Workflow
### 1. Create Output Layout
Keep user-facing deliverables separate from intermediate evidence files.
Use this layout:
```text
<deck-stem>-speaker-output/
├── <deck-stem>-with-notes.pptx
├── <deck-stem>-display.docx
├── <deck-stem>-display.md # only if python-docx is unavailable
├── <deck-stem>-vision-review.md # optional, only if the Markdown review is requested
└── work/
├── slide_extract.json
├── visual_inventory.json
├── vision_review_packet.json
├── vision_review.json
├── display_document.json
├── notes.json
└── rendered_slides/
```
In the final response, surface only the user-facing deliverables as a short summary plus their file paths:
- PowerPoint with speaker notes
- complete display rehearsal document
- vision-review packet, and the Markdown version only if it was generated
All 提问、分享技巧或报告无法使用。按“有帮助”数量排序。