kimi-docx

Name: kimi-docx
Author: thvroyal

435installs51forks

How to install kimi-docx?

thvroyal/kimi-skills/kimi-docx

$npx -y skills add thvroyal/kimi-skills --skill kimi-docx

Installs into the current project.

Summary

Generate and edit Word documents (.docx). Supports professional documents including covers, charts, track-changes editing, and more. Suitable for any .docx creation or modification task.

Files · 1

View on GitHub

SKILL.md

1	# Part 1: Goals
2
3	## ⚠️ When to Unzip vs Read
4
5	To preserve ANY formatting from the source document, MUST unzip and parse XML.
6
7	Read tool returns plain text only — fonts, colors, alignment, borders, styles are lost.
8
9	\| Need \| Method \|
10	\|------\|--------\|
11	\| Text content only (summarize, analyze, translate) \| Read tool is fine \|
12	\| Formatting info (copy styles, preserve layout, template filling) \| Unzip and parse XML \|
13	\| Structure + comments/track changes \| `pandoc input.docx -t markdown` \|
14
15	## Core Principles
16
17	1. Preserve formatting — When editing existing documents, retain original formatting. Clone and modify, never recreate.
18
19	2. Correct feature implementation — Comments need multi-file sync. Track Changes need revision marks. Use the right structure.
20
21	Never use python-docx/docx-js as fallback. These libraries produce lower quality output than direct XML manipulation.
22
23	## Source Principle
24
25	Template provided = Act as form-filler, not designer.
26	- Format is the user's decision
27	- Task: replace placeholders, not redesign
28	- Like filling a PDF form—do not redesign
29
30	No template = Act as designer. Design freely based on scenario.
31
32	For .doc (legacy format), first convert with `libreoffice --headless --convert-to docx`.
33
34	---
35
36	# Part 2: Execution
37
38	## File Structure
39
40	```
41	docx/
42	├── SKILL.md ← This file (entry point + reference)
43	├── references/
44	│ └── EditingGuide.md → Complete Python editing tutorial (comments, track changes, 5-file sync)
45	├── scripts/
46	│ ├── docx → Unified entry (the only script to call)
47	│ ├── fix_element_order.py → Auto-fix XML element ordering
48	│ ├── validate_docx.py → Business rule validation
49	│ ├── generate_backgrounds.py → Morandi style backgrounds
50	│ ├── generate_inkwash_backgrounds.py → Ink-wash style backgrounds
51	│ └── generate_chart.py → matplotlib (only for heatmaps/3D/radar; simple charts must use native)
52	├── assets/
53	│ └── templates/
54	│ ├── KimiDocx.csproj → Project file template (for creating new docs)
55	│ ├── Program.cs → Program entry template
56	│ ├── Example.cs → Complete example (cover+TOC+charts+back cover)
57	│ ├── CJKExample.cs → CJK content patterns (quote escaping, fonts)
58	│ └── xml/ → XML templates for comments infrastructure
59	└── validator/ → OpenXML validator (pre-compiled binary, AI does not modify)
60	```
61
62	Creating new documents: Use C# SDK with `./scripts/docx build` → See `Example.cs` for patterns, `CJKExample.cs` for CJK content
63	Editing existing documents: Use Python + lxml → See `references/EditingGuide.md` for complete tutorial
64
65	⚠️ Do NOT mix these approaches. C# SDK for creation, Python for editing. Never use python-docx/docx-js.
66
67	## Environment Setup
68
69	First time, execute in the SKILL directory:
70
71	```bash
72	cd /app/.kimi/skills/kimi-docx/
73	./scripts/docx init
74	```
75
76	Fixed Path Conventions (cannot be changed):
77
78	\| Path \| Purpose \|
79	\|------\|---------\|
80	\| `/app/.kimi/skills/kimi-docx/` \| SKILL directory, where commands are executed \|
81	\| `/tmp/docx-work/` \| Working directory, edit `Program.cs` here \|
82	\| `/mnt/okcomputer/output/` \| Output directory, final deliverables \|
83	\| `/mnt/okcomputer/upload/` \| User upload location (input files) \|
84
85	Script Commands (`./scripts/docx <cmd>`):
86
87	\| Command \| Purpose \|
88	\|---------\|---------\|
89	\| `env` \| Show environment status (no changes) \|
90	\| `init` \| Setup dependencies + workspace \|
91	\| `build [out]` \| Compile, run, validate (default: output/output.docx) \|
92	\| `validate FILE` \| Validate existing docx \|
93
94	The script automatically handles:
95	- Detects dotnet/python3 (required), pandoc/playwright/matplotlib (optional)
96	- Installed → use directly; Not installed → auto-install; Broken → repair
97	- Initializes working directory, copies template files
98
99	## Build Process
100
101	Must use `./scripts/docx build`, do not execute `dotnet build && dotnet run` separately (skips validation).
102
103	### Program.cs Output Path Convention (Critical)
104
105	Program.cs must get output path from command line arguments, otherwise build script cannot find the generated file:
106
107	```csharp
108	// Correct - get output path from command line arguments
109	string outputFile = args.Length > 0 ? args[0] : "/mnt/okcomputer/output/output.docx";
110
111	// Wrong - hardcoded path causes build failure
112	string outputFile = "my_document.docx"; // Script can't find file!
113	```
114
115	\| Step \| Action \| Notes \|
116	\|------\|--------\|-------\|
117	\| 1. Compile \| `dotnet build` \| Provides fix suggestions on failure \|
118	\| 2. Generate \| `dotnet run -- <output path>` \| Path passed via command line args \|
119	\| 3. Auto-fix \| `fix_element_order.py` \| Fixes XML element ordering issues \|
120	\| 4. OpenXML validation \| `validator/` \| Mand

People who liked this also viewed

6 picks

Type

grill-with-docsA relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.SkillsJul 2026537k182k
lark-minutes飞书妙记：搜索妙记、查看妙记基础信息、下载/上传音视频、读取或编辑妙记的产物内容、改标题、替换说话人/关键词、申请妙记查看/编辑权限。当给出minute_token、本地音视频文件，要查/改/转妙记产物，或用户明确要主动申请妙记权限时使用；本地音视频转纪要/逐字稿优先走本 skill，不要用 ffmpeg/whisper 本地转写。不负责：获取会议关联妙记，或仅按自然语言标题定位纪要SkillsJul 2026379k16k
lark-markdown飞书 Markdown：查看、创建、上传、编辑和比较 Markdown 文件。当用户需要创建或编辑 Markdown 文件、读取、修改、局部 patch 或比较差异时使用。不负责将 Markdown 导入为飞书在线文档，也不负责文件搜索、权限、评论、移动、删除等云空间管理操作。SkillsJul 2026295k16k
docxUse this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files) or Word templates (.dotx files). Triggers include: any mention of 'Word doc', 'word document', SkillsJul 2026157k163k
edit-articleSkills for Real Engineers. Straight from my .agents directory.SkillsJul 2026154k181k
lark-note飞书会议纪要（Note）直查：已知 note_id 时查询纪要详情、展示类型、关联文档 token，并读取 unified 原始逐字记录。当用户已持有 note_id，或从文档显式 vc-node-id 获得 note_id 时使用。不负责会议/日程/妙记定位、文档标题搜索或 Docx 正文读取。SkillsJul 2026154k16k

kimi-docx

435installs51forks

View on GitHub

How to install kimi-docx?

thvroyal/kimi-skills/kimi-docx

$npx -y skills add thvroyal/kimi-skills --skill kimi-docx

Installs into the current project.

Summary

Generate and edit Word documents (.docx). Supports professional documents including covers, charts, track-changes editing, and more. Suitable for any .docx creation or modification task.

Files · 1

View on GitHub

SKILL.md

1	# Part 1: Goals
2
3	## ⚠️ When to Unzip vs Read
4
5	To preserve ANY formatting from the source document, MUST unzip and parse XML.
6
7	Read tool returns plain text only — fonts, colors, alignment, borders, styles are lost.
8
9	\| Need \| Method \|
10	\|------\|--------\|
11	\| Text content only (summarize, analyze, translate) \| Read tool is fine \|
12	\| Formatting info (copy styles, preserve layout, template filling) \| Unzip and parse XML \|
13	\| Structure + comments/track changes \| `pandoc input.docx -t markdown` \|
14
15	## Core Principles
16
17	1. Preserve formatting — When editing existing documents, retain original formatting. Clone and modify, never recreate.
18
19	2. Correct feature implementation — Comments need multi-file sync. Track Changes need revision marks. Use the right structure.
20
21	Never use python-docx/docx-js as fallback. These libraries produce lower quality output than direct XML manipulation.
22
23	## Source Principle
24
25	Template provided = Act as form-filler, not designer.
26	- Format is the user's decision
27	- Task: replace placeholders, not redesign
28	- Like filling a PDF form—do not redesign
29
30	No template = Act as designer. Design freely based on scenario.
31
32	For .doc (legacy format), first convert with `libreoffice --headless --convert-to docx`.
33
34	---
35
36	# Part 2: Execution
37
38	## File Structure
39
40	```
41	docx/
42	├── SKILL.md ← This file (entry point + reference)
43	├── references/
44	│ └── EditingGuide.md → Complete Python editing tutorial (comments, track changes, 5-file sync)
45	├── scripts/
46	│ ├── docx → Unified entry (the only script to call)
47	│ ├── fix_element_order.py → Auto-fix XML element ordering
48	│ ├── validate_docx.py → Business rule validation
49	│ ├── generate_backgrounds.py → Morandi style backgrounds
50	│ ├── generate_inkwash_backgrounds.py → Ink-wash style backgrounds
51	│ └── generate_chart.py → matplotlib (only for heatmaps/3D/radar; simple charts must use native)
52	├── assets/
53	│ └── templates/
54	│ ├── KimiDocx.csproj → Project file template (for creating new docs)
55	│ ├── Program.cs → Program entry template
56	│ ├── Example.cs → Complete example (cover+TOC+charts+back cover)
57	│ ├── CJKExample.cs → CJK content patterns (quote escaping, fonts)
58	│ └── xml/ → XML templates for comments infrastructure
59	└── validator/ → OpenXML validator (pre-compiled binary, AI does not modify)
60	```
61
62	Creating new documents: Use C# SDK with `./scripts/docx build` → See `Example.cs` for patterns, `CJKExample.cs` for CJK content
63	Editing existing documents: Use Python + lxml → See `references/EditingGuide.md` for complete tutorial
64
65	⚠️ Do NOT mix these approaches. C# SDK for creation, Python for editing. Never use python-docx/docx-js.
66
67	## Environment Setup
68
69	First time, execute in the SKILL directory:
70
71	```bash
72	cd /app/.kimi/skills/kimi-docx/
73	./scripts/docx init
74	```
75
76	Fixed Path Conventions (cannot be changed):
77
78	\| Path \| Purpose \|
79	\|------\|---------\|
80	\| `/app/.kimi/skills/kimi-docx/` \| SKILL directory, where commands are executed \|
81	\| `/tmp/docx-work/` \| Working directory, edit `Program.cs` here \|
82	\| `/mnt/okcomputer/output/` \| Output directory, final deliverables \|
83	\| `/mnt/okcomputer/upload/` \| User upload location (input files) \|
84
85	Script Commands (`./scripts/docx <cmd>`):
86
87	\| Command \| Purpose \|
88	\|---------\|---------\|
89	\| `env` \| Show environment status (no changes) \|
90	\| `init` \| Setup dependencies + workspace \|
91	\| `build [out]` \| Compile, run, validate (default: output/output.docx) \|
92	\| `validate FILE` \| Validate existing docx \|
93
94	The script automatically handles:
95	- Detects dotnet/python3 (required), pandoc/playwright/matplotlib (optional)
96	- Installed → use directly; Not installed → auto-install; Broken → repair
97	- Initializes working directory, copies template files
98
99	## Build Process
100
101	Must use `./scripts/docx build`, do not execute `dotnet build && dotnet run` separately (skips validation).
102
103	### Program.cs Output Path Convention (Critical)
104
105	Program.cs must get output path from command line arguments, otherwise build script cannot find the generated file:
106
107	```csharp
108	// Correct - get output path from command line arguments
109	string outputFile = args.Length > 0 ? args[0] : "/mnt/okcomputer/output/output.docx";
110
111	// Wrong - hardcoded path causes build failure
112	string outputFile = "my_document.docx"; // Script can't find file!
113	```
114
115	\| Step \| Action \| Notes \|
116	\|------\|--------\|-------\|
117	\| 1. Compile \| `dotnet build` \| Provides fix suggestions on failure \|
118	\| 2. Generate \| `dotnet run -- <output path>` \| Path passed via command line args \|
119	\| 3. Auto-fix \| `fix_element_order.py` \| Fixes XML element ordering issues \|
120	\| 4. OpenXML validation \| `validator/` \| Mand

People who liked this also viewed

6 picks

Type