據 AlphaMoat 統計,截至 2026-10,Powerpoint / PPTX 累計下載 125,424 次、獲 200 個星標,按累計下載量在本次參與排名的 10,914 個 AI 技能中排名第 196 位,在「辦公效率」分類(909 個)中排名第 29 位。
列表預設按累計下載量排序,也可按星標排序;詳情頁排名按累計下載量計算。
| 平台 | 累計下載 | 星標 | 評論 |
|---|---|---|---|
| ClawHub ↗ | 5.8萬 | 146 | - |
| SkillHub ↗ | 12.5萬 | 200 | — |
各平台的計數口徑不同,統計時間不一致。
開始編輯前,先分清楚是閱讀、修改既有簡報、依範本重建,還是從頭製作,因為各自的失敗情況不同。使用範本時,先盤點可用版型、實際佔位符,以及投影片畫面以外的備註與留言。依內容項目數選擇版型,不要硬塞進多欄版面。.pptx 是由多個 OOXML 部件組成的封裝檔;母片或版型可能覆蓋單張投影片的修改,因此問題未必出在該張投影片。交付前要分開檢查內容與視覺呈現。
資料釋出於 2026-10-27
以下是根據技能文件生成的示例,不代表實際執行結果。
2026-09 起統計方法調整:同名技能按作者分別統計,並覆蓋全部技能。圖中虛線為調整前的月份,與之後的資料不直接比較,也不計算跨越調整的增長。 該技能有同名的其他版本,調整前的資料歸屬當前下載量最大的這一個。
| 月份 | 累計下載 | 環比 | 星標 |
|---|---|---|---|
| 2026-10 | 12.5萬 | — | 200 |
| 2026-09 | 8.3萬 | — | 199 |
| 2026-08 | 7.5萬 | +15.8% | 197 |
| 2026-07 | 6.5萬 | +8.6% | 193 |
| 2026-06 | 6萬 | +11.7% | 176 |
| 2026-05 | 5.3萬 | — | 149 |
| 2026-03 | 3.5萬 | — | 104 |
以下是作者釋出的原始檔案,按純文字顯示,本站未做修改或稽核;其中的連結不可點選,命令請核實後再執行。抓取於 2026-10-23。
---
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 <slug>` 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`
透過 MCP 在騰訊文件裡新建、編輯與管理線上文件的完整操作手冊。
WPS Office 全家桶 - 四引擎(WPS/MS Office/LibreOffice/純Python)智慧識別使用者已安裝軟體,純Python模式支援排序/篩選/圖表/公式/統計,含文件模板(程式碼生成)、最佳實踐案例、故障排除大章(20+避坑+15 FAQ+15錯誤ID 統一索引)、自動重試、硬體自適應、環境自檢、Skill更新提醒;v5.1新增:kingdoc雲端橋接(白名單探測+配置預檢+subprocess上傳+差異檢查)、條件格式/資料驗證跨引擎IO(JSON中間格式保真往返)、會議紀要三段式要素化(待辦清單+決策記錄+風險異議)+說話人標註(MFCC聚類);v5.2新增:公文一鍵排版(GB/T 9704 規則庫約束+結構識別套版+紅頭預留位+聯合行文)、批次水印與敏感資訊打碼(身份證/手機號/銀行卡/電子郵件雙軌識別+黑色矩形覆蓋+打碼清單)、跨文件知識檢索與問答(本地TF-IDF零依賴+跳轉+可選zwjh記憶橋接);刪除:與contract-review重複的輕量合同審查模組,改為文件互鏈引導;v5.2.5修復:MS Office引擎下Excel/PPT建立必然失敗(錯用Word COM物件),新增get_ms_excel/get_ms_ppt及三槽位統一釋放release_ms,MS Office路徑透傳filepath引數;v5.3.5修復:SKILL.md frontmatter 修復 tags 塊序列誤混入聯絡方式行導致標準 YAML 解析失敗;v5.4.0新增:留存型功能——定時任務與報告中心(schedule_register 升級為三平台統一排程層 schtasks/cron/launchd,錯過策略 skip/run_once,登錄檔 JSON 可匯出匯入;新建 report_center.py 報告中心,templates/reports/*.json 引數化模板 + ECharts 單檔案 HTML 輸出(圖表內聯、無服務端、雙擊即開);report_generator 升級支援 --format html;wps.py CLI 統一埋點 SQLite,自動供 report_center 生成周度使用摘要附在報告末尾;watch.py 職責收窄為純事件採集);v5.3.0新增:統一CLI入口 wps(registry.json登錄檔分發,office --app/--action 與 convert 子命令、--list 一屏列出全部命令,薄路由層不改指令碼內部邏輯)、全命令 --json 機器可讀輸出(固定 ok/error_id/elapsed/data 四欄位,對齊 E001-E015,wps_error.py 新增 emit_json 統一齣口)、_worker 啟動最佳化(wps_pure 改惰性載入,pywin32/python-docx/openpyxl 經核查已惰性匯入,ENGINE_CACHE 程序級單例複用,COM 釋放統一走 release_ms 三槽位)、轉換三入口合併為 convert(format_converter/md_converter/wps_docx_to_ppt 內部按目標格式路由,舊指令碼保留為相容別名並提示新命令,v6.0.0 移除)
按主題與風格自動生成 PPT 檔案的技能。
體制內資深辦公室主任+管理學博士,自學程式設計開發的智慧公文寫作Skill,讓所有辦公室同仁少掉頭髮、少加無用的班,材料一稿過關,省下的時間留給自己、享受生活!————————我們能給你帶來的核心價值:1、顛覆傳統寫作:邏輯建模38類公文全鏈條,特有模板化引導問答模式,分分鐘省心生成高質量大稿。--------2、替你“向上管理”:獨有審稿人畫像機制,文稿一鍵結構性修改,精準匹配審稿人畫像,過稿率提升至少10倍!----------3、杜絕AI編造:缺失的數字、文號、人名、日期一律用[待補]標註,絕不杜撰,守住公文底線。-----------4、演算法格式托底:數十萬全量智控知識庫+6500行前沿核心控制程式碼,格式精準對齊GB/T 9704,出稿零失誤。——————————————————本skill歷史版本開放了5%知識庫的免費試用版,下載即可使用,但需注意:知識庫有著作權,僅用於個人使用,不可用於其他任何目的。有興趣的可以試試。——————————————————————單次付費版skill已釋出,2元一次使用全量知識庫。具體在釋出者“熵衍資訊”主頁skill裡。
WPS Office 全家桶 - 四引擎(WPS/MS Office/LibreOffice/純Python)智慧識別使用者已安裝軟體,純Python模式支援排序/篩選/圖表/公式/統計,含文件模板(程式碼生成)、最佳實踐案例、故障排除大章(20+避坑+15 FAQ+15錯誤ID 統一索引)、自動重試、硬體自適應、環境自檢、Skill更新提醒;v5.0新增:定時任務註冊管理(schtasks/crontab)、目錄輪詢監聽(YAML規則+大檔案分片)、使用統計與穩定性中心(SQLite埋點+引擎健康+引擎偏好)、COM三步自愈(regsvr32→修復安裝→手動指引)、對話式資料查詢(NL2SQL式意圖解析+查詢計劃+連續追問)、multi-agent編排引擎橋接(白名單探測+流水線模板註冊)
當用戶要處理 Word/Excel/PPT、做文件模板與排版、批次合併圖表、公文一鍵套紅頭、會議紀要要素化、或跨引擎辦公自動化時,WPS全家桶·辦公管家.Skill 立即出動。 四引擎智慧識別已裝軟體(WPS/MS Office/LibreOffice/純Python),純Python模式支援排序/篩選/圖表/公式/統計;含文件模板程式碼生成、20+避坑+15 FAQ+15錯誤ID統一索引、自動重試、硬體自適應、環境自檢。 當用戶提到批次水印、敏感資訊打碼(身份證/手機號/銀行卡/電子郵件)、跨文件檢索問答等訊號時,主動亮劍。
透過 Tencent Docs Open API 以 curl + jq 建立、讀取、列出、搜尋和管理騰訊文件的自動化工作流,覆蓋線上文件、線上表格、幻燈片、思維導圖、流程圖、智慧表格與收集表七種類型,支援讀取後設資料與單元格區域、上傳圖片、建立副本,並對重新命名/移動/刪除等寫操作強制先經使用者確認。Use when the user 提到騰訊文件 / Tencent Docs / docs.qq.com、貼上 docs.qq.com 連結,或想在其騰訊文件空間中建立、讀取、整理文件時使用。Triggers include 騰訊文件、線上文件、線上表格、思維導圖、流程圖、智慧表格、收集表。如需文案寫作完整工作流套件,淘寶搜尋「AI靈匣」店鋪獲取完整版。
透過 kdocs-cli 操作金山文件雲文件的官方技能。
將使用者明確糾正與自我檢視整理成分層記憶,並依使用情況升級或封存。
在保留公式、格式和活頁簿結構的前提下建立、檢查或編輯 Excel 檔案。
處理 Word 與 DOCX 文件的作業指南,著重維持樣式、編號與版面。
面向多家影片模型 API 的 AI 影片生成與編排技能。
把資料庫、表格與匯出的原始資料變成可決策結論的資料分析技能。
資料月份:2026-10 · 下載/星標數聚合自公開技能註冊庫(ClawHub、SkillHub),按月更新。口徑說明見資料方法。