According to AlphaMoat, as of 2026-10, Word Docx 1 has 8,966 downloads and 0 stars — ranked by downloads #3,092 among 10,914 AI skills in this ranking, and #335 of 909 in Office.
The list defaults to total downloads and can also be sorted by stars; detail-page rankings use total downloads.
| Platform | Downloads | Stars | Comments |
|---|---|---|---|
| ClawHub ↗ | 4.9K | - | - |
| SkillHub ↗ | 9.0K | - | — |
Platforms count differently and update at different times.
Use when the main artifact is a Microsoft Word document or .docx file, especially when tracked changes, comments, headers, numbering, fields, tables, templates, or compatibility matter. Core rules: - A .docx file is a ZIP of XML parts, so structure matters as much as visible text. Text may be split across runs; prefer named styles over direct formatting; list numbering lives in numbering definitions (abstractNum/num), so restarting lists “by eye” usually fails; page layout is section-level behavior with differing first-page/odd-even headers; in review workflows - In tracked-change workflows, only the changed span should look changed; broad rewrites create noisy reviews and can destroy the original formatting context. Deleted text can persist in the XML; verify round-trip compatibility across Word/LibreOffice/Google Docs before delivery; treat .docm as macro-bearing higher risk; explicit table widths are safer than auto-fit. Card caution: documents may contain comments, tracked changes, deleted text, or metadata the user did not intend to expose — review before sharing outputs; use minimal structure-preserving edits and verify fidelity in the target editor. Version conflict recorded: card 1.0.0 vs frontmatter 1.0.2.
Profile published 2026-10-29
Generated from the skill’s documentation as examples; not results of actual runs.
The counting method changed in 2026-09: skills with the same name are now counted separately by author, and the full catalog is covered. Dashed lines show months before the change; they are not compared with later months, and no growth is computed across the change. Other skills share this name; figures from before the change are attributed to this one, which currently has the most downloads.
| Month | Downloads | MoM | Stars |
|---|---|---|---|
| 2026-10 | 9.0K | — | - |
| 2026-09 | 5.6K | — | - |
| 2026-08 | 4.7K | +18.7% | - |
| 2026-07 | 4.0K | +111.6% | - |
| 2026-06 | 1.9K | +15.6% | - |
| 2026-05 | 1.6K | — | - |
| 2026-03 | 775 | — | - |
The author’s original file, shown as plain text without edits or review by AlphaMoat. Links are not clickable; check commands before running them. Fetched 2026-10-23.
---
name: Word / DOCX
slug: word-docx
version: 1.0.2
homepage: https://clawic.com/skills/word-docx
description: "Create, inspect, and edit Microsoft Word documents and DOCX files with reliable styles, numbering, tracked changes, tables, sections, and compatibility checks. Use when (1) the task is about Word or `.docx`; (2) the file includes tracked changes, comments, fields, tables, templates, or page layout constraints; (3) the document must survive round-trip editing without formatting drift."
changelog: Tightened the skill around fragile review workflows, reference stability, and layout drift after a stricter external audit.
metadata: {"clawdbot":{"emoji":"📘","os":["linux","darwin","win32"]}}
---
## When to Use Use when the main artifact is a Microsoft Word document or `.docx` file, especially when tracked changes, comments, headers, numbering, fields, tables, templates, or compatibility matter. ## Core Rules ### 1. Treat DOCX as OOXML, not plain text - A `.docx` file is a ZIP of XML parts, so structure matters as much as visible text. - The critical parts are usually `word/document.xml`, `styles.xml`, `numbering.xml`, headers, footers, and relationship files. - Text may be split across multiple runs; never assume one word or sentence lives in one XML node. - Use different workflows on purpose: structured extraction for quick reading, style-driven generation for new files, and OOXML-aware editing for fragile existing documents. - If the job is mainly reading, extracting, or reviewing, prefer a structure-preserving read path before touching OOXML. - For deep edits, inspect the package layout instead of relying only on rendered output. - Reading, generating, and preserving an existing reviewed document are different jobs even when the format is the same. - Legacy `.doc` inputs usually need conversion before you can trust modern `.docx` assumptions. ### 2. Preserve styles and direct formatting deliberately - Prefer named styles over direct formatting so the document stays editable. - Styles layer: paragraph styles, character styles, and direct formatting do not behave the same. - Removing direct formatting is often safer than stacking more inline formatting on top. - When editing an existing file, extend the current style system instead of inventing a parallel one. - Copying content between documents can silently import foreign styles, theme settings, and numbering definitions. ### 3. Lists and numbering are their own system - Bullets and numbering belong to Word's numbering definitions, not pasted Unicode characters. - `abstractNum`, `num`, and paragraph numbering properties all matter, so restart behavior is rarely "visual only". - Indentation and numbering are related but not identical; a list can have broken numbering even if the indent looks right. - A list that looks correct in one editor can restart, flatten, or renumber itself later if the underlying numbering state is wrong. ### 4. Page layout lives in sections - Margins, orientation, headers, footers, and page numbering are section-level behavior. - First-page and odd/even headers can differ inside the same document, so one header fix may not fix the document. - Set page size explicitly because A4 and US Letter defaults change pagination and table widths. - Use section breaks for layout changes; manual spacing and stray page breaks usually create drift. - Header and footer media use part-specific relationships, so copied IDs often break images or links. - Tables, page breaks, and headers often drift together, so treat layout fixes as document-wide, not local cosmetic edits. - Table geometry depends on page width, margins, and fixed widths, so "close enough" table edits often break later in Google Docs or LibreOffice. ### 5. Track changes, comments, and fields need precise edits - Visible text is not the full document when tracked changes are enabled. - Insertions, deletions, and comments carry metadata that can survive careless edits. - Deleted text may still exist in the XML even when it no longer appears on screen. - Comment anchors and review ranges can break if edits move text without preserving the surrounding structure. - Comment markers and review wrappers do not behave like inline formatting, so moving text carelessly can orphan or misplace them. - Comments, footnotes, bookmarks, and linked media may live in separate parts, not only in the main document body. - Tables of contents, page numbers, dates, cross-references, and mail merge placeholders are fields. - Edit the field source carefully and expect cached display values to lag until refresh. - Hyperlinks, bookmarks, and references can break if IDs or relationships stop matching. - Bookmarks, footnotes, comment ranges, and cross-references depend on stable anchors even when the visible text seems untouched. - A document can look correct while still containing stale field output that refreshes later into something different. - For review workflows, make minimal replacements instead of rewriting whole paragraphs. - In tracked-change workflows, only the changed span should look changed; broad rewrites create noisy reviews and can destroy the original formatting context. - For legal, academic, or business review documents, default to review-style edits over wholesale paragraph rewrites unless the user explicitly wants a rewrite. ### 6. Verify round-trip compatibility before delivery - Complex documents can shift between Word, LibreOffice, Google Docs, and conversion tools. - Tables, headers, embedded fonts, and copied styles are common sources of layout drift. - Treat `.docm` as macro-bearing and higher risk; treat `.doc` as legacy input that may need conversion first. - When layout matters, explicit table widths are safer than auto-fit or percentage-style behavior that different editors reinterpret. - A document that passes a text check can still fail on pagination, table widths, or reference refresh after the recipient opens it. ## Common Traps - Copy-paste can import unwanted styles and numbering definitions. - Header or footer images use part-specific relationships, so reusing IDs blindly breaks them. - Empty paragraphs used as spacing make templates fragile; spacing belongs in paragraph settings. - A clean-looking export can still hide unresolved revisions, comments, or stale field values. - Restarting lists "by eye" usually fails because numbering state lives outside the paragraph text. - One visible phrase can be split across several runs, bookmarks, revision tags, or field boundaries. - Replacing a whole paragraph to change one clause often breaks review quality, bookmarks, comments, or nearby inline formatting. - Deleting all visible text from a paragraph or list item can still leave behind an empty paragraph mark, empty bullet, or unstable numbering. - Table auto-fit and percentage-like width behavior can look acceptable in Word and still drift in Google Docs or LibreOffice. - LibreOffice and Google Docs can shift complex tables, section behavior, and embedded fonts even when Word looks perfect. - Compatibility mode can silently cap newer features or change pagination behavior. - A single change in page size or margin defaults can ripple through tables, headers, TOC, and cross-references. - A revision workflow can look accepted on screen while leftover metadata, comments, or field caches still make the file unstable later. - TOC entries, footnotes, and cross-references can look correct until the recipient updates fields and exposes broken anchors. ## Related Skills Install with `clawhub install <slug>` if user confirms: - `documents` — General document handling and format conversion. - `brief` — Concise business writing and structured summaries. - `article` — Long-form drafting and editorial structure. ## Feedback - If useful: `clawhub star word-docx` - Stay updated: `clawhub sync`
A full manual for creating, editing, and managing Tencent Docs through 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 移除)
A skill that generates PPT decks from a topic and style.
体制内资深办公室主任+管理学博士,自学编程开发的智能公文写作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编排引擎桥接(白名单探测+流水线模板注册)
WPS/MS Office/LibreOffice/纯Python 四引擎智能办公全家桶:文档/表格/PPT/公文/会议纪要一体化。
通过 Tencent Docs Open API 以 curl + jq 创建、读取、列出、搜索和管理腾讯文档的自动化工作流,覆盖在线文档、在线表格、幻灯片、思维导图、流程图、智能表格与收集表七种类型,支持读取元数据与单元格区域、上传图片、创建副本,并对重命名/移动/删除等写操作强制先经用户确认。Use when the user 提到腾讯文档 / Tencent Docs / docs.qq.com、粘贴 docs.qq.com 链接,或想在其腾讯文档空间中创建、读取、整理文档时使用。Triggers include 腾讯文档、在线文档、在线表格、思维导图、流程图、智能表格、收集表。如需文案写作完整工作流套件,淘宝搜索「AI灵匣」店铺获取完整版。
The official skill for working with Kdocs cloud documents through kdocs-cli.
Data as of 2026-10. Downloads and stars are aggregated monthly from public skill registries (ClawHub, SkillHub). See data methodology.