跳到主内容
智客 ZICQ

技能库 智客分类:文档办公 Powerpoint / PPTX OpenClaw

Powerpoint / PPTX

创建,检查,并编辑Microsoft PowerPoint演示文稿和PPTX甲板,并配有可靠的布局,模板,占位符,注释,图表,以及视觉QA. 当 (1) 任务涉及 PowerPoint 或 `.pptx' 时使用; (2) 排版、 占位符、 注释、 图表、 注释, 或模板的忠贞性事项; (3) 甲板在编辑后必须清洁地制作.

1601 安装量 · 146 星标

官方网址:作者主页

技能介绍

先看中文介绍;官方 description 原文单独保留,不改写 SKILL.md。

做什么

创建、检查和编辑 Microsoft PowerPoint 演示文稿和 PPTX 甲板,并配有可靠的布局、模板、占位符、注释、图表和视觉QA

何时用

当主要文物是微软PowerPoint演示文稿或".pptx"甲板时使用,特别是当布局,模板,占位符,注释,注释,图表,提取,编辑,或最终视觉质量事项时使用

代理如何加载

按 Agent Skills 渐进披露:启动时只加载 name 与 description(约 100 token);任务匹配后才读入整份 SKILL.md 正文;scripts/、references/、assets/ 仅在需要时再读。 本文件正文结构:When to Use、Core Rules、1. Choose the workflow before touching the deck、2. Inventory the deck before replacing content、3. Match content to the actual placeholders、4. Preserve the deck's visual language。 其中含规范建议的小节:分步指令。

文件分析

文件分析:这是一份仅含 SKILL.md 的指令型技能,代理激活后整份正文进入上下文。

官方 description(原文)

Create, inspect, and edit Microsoft PowerPoint presentations and PPTX decks with reliable layouts, templates, placeholders, notes, charts, and visual QA. Use when (1) the task is about PowerPoint or `.pptx`; (2) layouts, placeholders, notes, charts, comments, or template fidelity matter; (3) the deck must render cleanly after edits.

When to UseCore Rules1. Choose the workflow before touching the deck2. Inventory the deck before replacing content3. Match content to the actual placeholders4. Preserve the deck's visual language5. Run content QA and visual QA separately6. Keep decks portable and review-safeCommon TrapsRelated SkillsFeedback

SKILL.md 与 Agent 调用

官方规范 ↗
name
Powerpoint / PPTX
description
Create, inspect, and edit Microsoft PowerPoint presentations and PPTX decks with reliable layouts, templates, placeholders, notes, charts, and visual QA. Use when (1) the task is about PowerPoint or `.pptx`; (2) layouts, placeholders, notes, charts, comments, or template fidelity matter; (3) the deck must render cleanly after edits.
  1. 发现技能客户端向 Agent 提供名称与描述目录。
  2. 匹配与调用用户指定或任务匹配后,载入 SKILL.md 指令。
  3. 按需加载按步骤读取参考文档、使用脚本与素材。

具体调用语法与可用工具以目标 Agent 客户端为准。 查看调用机制说明 ↗

安装这个技能

Skills CLI ↗

先选择目标 Agent 和安装范围,保留技能包的附属文件,安装后检查客户端能否发现该技能。

交给 Agent 安装

复制安装指令给支持 Agent Skills 的代理,确认其中的目标目录与客户端匹配。

把 Agent Skill「Powerpoint / PPTX」安装到我的项目:SKILL.md 原文与官方 description 见 https://zicq.com/zh/skills/skl-178adf9272fe213e-%E5%8A%A8%E5%8A%9B%E7%82%B9-PPTX.html
请存为 .cursor/skills/powerpoint-pptx/SKILL.md 或 .claude/skills/powerpoint-pptx/SKILL.md,frontmatter 的 name 与 description 保持原样,不要改写。

当前没有明确的 GitHub 技能包地址,请按来源页面的安装器说明操作。

ClawHub ↗

阅读排版
--- name: Powerpoint / PPTX slug: powerpoint-pptx version: 1.0.1 homepage: https://clawic.com/skills/powerpoint-pptx description: "Create, inspect, and edit Microsoft PowerPoint presentations and PPTX decks with reliable layouts, templates, placeholders, notes, charts, and visual QA. Use when (1) the task is about PowerPoint or `.pptx`; (2) layouts, placeholders, notes, charts, comments, or template fidelity matter; (3) the deck must render cleanly after edits." changelog: Rebalanced the skill toward template inventory, layout mapping, and higher-signal QA after a stricter external audit. metadata: {"clawdbot":{"emoji":"📊","requires":{"bins":[]},"os":["linux","darwin","win32"]}} --- ## When to Use Use when the main artifact is a Microsoft PowerPoint presentation or `.pptx` deck, especially when layouts, templates, placeholders, notes, comments, charts, extraction, editing, or final visual quality matter. ## Core Rules ### 1. Choose the workflow before touching the deck - Reading text, editing an existing deck, rebuilding from a template, and creating from scratch are different jobs with different failure modes. - For text extraction or inspection, read the deck before editing it. - Text extraction plus thumbnail-style visual inspection is safer than editing from shape assumptions alone. - For template-driven work, inventory the deck before replacing content. - For deep edits, remember a `.pptx` file is OOXML with separate parts for slides, layouts, masters, media, notes, and comments. - If a template exists, template fidelity beats generic slide-design instincts. - Reusing or duplicating a good existing slide is often safer than rebuilding it and hoping the theme still matches. ### 2. Inventory the deck before replacing content - Count the reusable layouts, real placeholders, notes, comments, media, and recurring typography or color patterns first. - Placeholder indexes and layout indexes are not portable assumptions. - Inspect the actual slide or template before targeting title, body, chart, or image shapes. - Speaker notes, comments, and linked assets can live outside the visible slide surface. - A missing or wrong placeholder target can silently land content in the wrong box or wrong layer. - Master and layout settings can override local slide edits, so the visible problem is not always on the slide you are editing. ### 3. Match content to the actual placeholders - Count the actual content pieces before choosing a layout. - Pick layouts based on the real number of ideas, columns, images, or charts the slide needs. - Do not force two ideas into a three-column slide or cram dense text under a chart. - Category counts and data series lengths must match or charts will break in ugly ways. - Explicit sizing beats wishful thinking: text boxes, images, and charts need real space, not "it should fit". - Do not choose a layout with more placeholders than the content can meaningfully fill. - Quote layouts are for real quotes, and image-led layouts are for slides that actually have images. - For chart-, table-, or image-heavy slides, full-slide or two-column layouts are usually safer than stacking dense text above the visual. ### 4. Preserve the deck's visual language - Theme, master, and layout files usually decide fonts, colors, and hierarchy more than any one slide does. - Start from the deck's actual theme, fonts, spacing, and aspect ratio instead of improvising a new style. - Reuse the deck's own alignment and spacing system instead of inventing a second visual language. - Use common fonts for portability and strong contrast for readability. - Preserve the template's visual logic first; originality matters less than not breaking the deck's existing language. - Combining slides from multiple sources requires normalizing themes, masters, and alignment afterward. ### 5. Run content QA and visual QA separately - Text overflow, bad alignment, clipped shapes, weak contrast, and placeholder leftovers are normal first-pass failures. - Run both content QA and visual QA; missing text and broken layout are different failure classes. - Render or inspect the actual deck output before delivery when layout matters. - Search for leftover template junk, sample labels, and placeholder text before calling the deck finished. - Check notes, comments, labels, legends, and chart/table semantics separately from the visual pass. - A deck can pass text extraction and still fail on overlap, clipping, wrong theme inheritance, or broken notes. - Thumbnail grids and rendered slides usually reveal layout bugs faster than code or text inspection. - Assume the first render is wrong and do at least one fix-and-verify cycle before calling the deck finished. - Re-check affected slides after each fix because one spacing change often creates another issue. ### 6. Keep decks portable and review-safe - Template masters can override direct edits in surprising ways. - Complex effects may degrade across PowerPoint, LibreOffice, and conversion pipelines, so keep important content robust without them. - Image sizing, font substitution, and placeholder mismatch are common reasons a deck looks good in code and bad on screen. - Notes, comments, linked media, and merged decks can stay broken even when the visible slide looks fine. ## Common Traps - Placeholder text and sample charts often survive template reuse if not explicitly replaced. - Directly editing one slide can fail if the real issue lives in the master or layout. - Charts, icons, and text boxes need enough space; near-collisions are usually visible only after rendering. - Layout indexes vary by template, so built-in assumptions from one deck often break in another. - A missing placeholder or wrong shape target can silently put content in the wrong place. - Counting the text ideas after choosing the layout usually leads to empty placeholders, weak hierarchy, or leftover template junk. - Font substitution can move line breaks and wreck careful spacing. - Speaker notes, comments, and linked media can stay broken even when the visible slide looks fine. - A deck can pass text inspection and still fail visually because of overlap, contrast, or edge clipping. - Editing from one slide alone can miss the real source of truth in the theme, master, or layout definitions. - Choosing a quote, comparison, or multi-column layout without matching content usually makes the deck look templated rather than intentional. - Combining or duplicating slides without checking masters and themes can create subtle inconsistency slide by slide. - Aspect-ratio mismatches like `16:9` versus `4:3` can shift every placement decision even when each slide looks locally reasonable. ## Related Skills Install with `clawhub install ` if user confirms: - `documents` — Document workflows that often feed presentation content. - `design` — Visual direction and layout decisions. - `brief` — Concise business messaging for slide narratives. ## Feedback - If useful: `clawhub star powerpoint-pptx` - Stay updated: `clawhub sync`

相关技能

文档办公

Ontology

为结构化的代理内存和可堆肥技能所打入的知识图. 在创建/征服实体(Person, project, Task, Evention, Document)时使用,链接相关对象,强制约束,规划多步动作作为图变,或技能需要共享状态时使用. 触发到"记住","我知道什么","链接X到Y",…

文档办公

Nano Pdf

使用纳米-pdf CLI编辑带有自然语言指令的PDF.

文档办公

Word / DOCX

创建,检查,并编辑有可靠样式的Microsoft Word文档和DOCX文件,编号,跟踪更改,表格,章节,并进行相容性检查. 当 (1) 任务涉及 Word 或 ".docx " 时使用; (2) 文件包括跟踪的更改,评论,字段,表格,模板,或页面布局限制; (3) 文档必须在不…

文档办公

Api Gateway

通过 Maton 网关调用第三方 API, 它为用户已经连接的应用程序注入证书 。 当用户命名一个连接的应用程序和其中的具体行动时使用此技能——读取一个邮箱,查询一个CMM,归档一个问题,更新一个电子表格,通过一个连接的搜索或刮取提供者运行一个查询. 每一次通话都到用户连接的应用…