Kimi-PDF：智能PDF生成与处理工具，支持HTML/LaTeX转换、合并、提取及表单填写

kimi-pdf by thvroyal/kimi-skills

79 周安装量

93 GitHub Stars

GitHub

安装命令

npx skills add https://github.com/thvroyal/kimi-skills --skill kimi-pdf

自动化 LaTeX 文档生成

🇨🇳中文介绍

路由选择

路由	触发条件	路由文件
HTML (默认)	所有 PDF 创建请求	`routes/html.md`
LaTeX	用户明确请求 LaTeX、.tex 或 Tectonic	`routes/latex.md`
Process	处理现有 PDF（提取、合并、填写表单等）	`routes/process.md`

默认使用 HTML。 仅当用户明确请求时才使用 LaTeX 路由。

强制要求：实施前必须阅读路由文件

实施前，您必须：

确定路由（HTML / LaTeX / Process）

广告位招租

在这里展示您的产品或服务

触达数万 AI 开发者，精准高效

联系我们

用户表述	路由
"创建 PDF"、"制作报告"、"撰写论文"	HTML
"使用 LaTeX"、"编译 .tex"、"使用 Tectonic"	LaTeX
"从 PDF 提取文本"、"合并这些 PDF"、"填写此表单"	Process

上下文	样式
学术论文、学位论文、正式课程作业	极简（白色、居中、无装饰）
报告、提案、专业文档	设计版（从 html.md 中的样式参考中选择）
不确定	默认使用设计版 — 纯文本封面 = 平庸

文档语言	格式
中文	GB/T 7714（使用 [J][M][D] 标识符）
英文	APA
混合	中文参考文献 → GB/T 7714，英文参考文献 → APA

核心约束 (必须遵守)

输出语言必须与用户的查询语言匹配。

用户使用中文写作 → PDF 内容为中文
用户使用英文写作 → PDF 内容为英文
用户明确指定语言 → 遵循用户的指定

2. 字数和页数约束

严格遵守用户指定的字数/页数要求
不要随意增加内容长度

3. 引用和搜索标准

关键：写作前先搜索

请勿捏造信息。如有疑问，先搜索。

如果内容涉及以下任何一项，您必须在写作前先搜索：

统计数据、数字、百分比、排名
政策、法规、法律、标准
学术研究、理论、方法论
时事、近期发展
任何您不是 100% 确定的内容

场景	需要搜索？	备注
统计数据、数据	必需	例如："2024 年就业率"
政策、法规	必需	例如："创业补贴"
研究、论文	必需	例如："方法 X 的有效性"
时效性内容	必需	知识截止日期后的信息
不确定的事实	必需	如果不确定，总是搜索
常识	不需要	例如："水在 100°C 沸腾"

搜索工作流程：

识别需要验证的事实/数据
搜索权威来源
如果结果不足，迭代搜索直到获得可靠信息
在参考文献中包含真实来源
如果搜索反复失败，请告知用户，而不是捏造数据

禁止捏造参考文献。所有引用必须包含：

正确的作者/机构名称
准确的标题
可验证的年份、期刊/来源

交叉引用 (必须可点击)

如 <a href="#fig-1-1">图 1-1</a> 所示...
根据 <a href="#eq-2-1">公式 (2-1)</a>...
参见 <a href="#sec3">第 3 节</a>...

注意：id 必须放在容器顶部（参见 html.md 中的 CSS 计数器部分）。

1. 字数/页数约束

必须严格遵守用户指定的字数或页数要求：

用户请求	执行标准
特定字数（例如："3000 字"）	在 ±20% 范围内，即 2400-3600 字
特定页数（例如："5 页"）	完全相等，最后一页可以是部分页
字数范围（例如："2000-3000 字"）	必须落在范围内
无明确要求	根据文档类型合理推断；宁详勿略
指定最小值（例如："超过 5000 字"）	不超过 2 倍，即 5000-10000 字

随意缩短内容（"简洁"不是借口）
用过多的项目列表填充页面（保持高信息密度）
超过用户要求长度的两倍

特殊情况 - 简历/CV：

简历应为 1 页，除非用户另有指定
使用紧凑的页边距：margin: 1.5cm

2. 大纲遵循 (强制)

当用户提供大纲时：

严格遵守用户提供的大纲结构
章节标题必须与大纲匹配（允许微调措辞，不得更改级别/顺序）
不得随意添加或删除章节
如果大纲似乎有问题，先询问用户再进行修改

当用户未提供大纲时：

根据文档类型使用标准结构：
- 学术论文：IMRaD（引言-方法-结果-讨论）或引言-文献综述-方法-结果-讨论-结论
- 商业报告：结论先行（执行摘要 → 详细分析 → 建议）
- 技术文档：概述 → 原理 → 用法 → 示例 → 常见问题
- 课程作业：遵循作业结构要求
章节之间必须有逻辑递进，不得脱节

路由	工具	用途
HTML	Playwright + Paged.js	HTML → PDF 转换
HTML	KaTeX, Mermaid	数学公式、图表
Process	pikepdf	表单填写、页面操作、元数据
Process	pdfplumber	文本和表格提取
Process	LibreOffice	Office → PDF 转换
LaTeX	Tectonic	LaTeX → PDF 编译

2026 年 2 月 4 日

🇺🇸English

Route Selection

Route	Trigger	Route File
HTML (default)	All PDF creation requests	`routes/html.md`
LaTeX	User explicitly requests LaTeX, .tex, or Tectonic	`routes/latex.md`
Process	Work with existing PDFs (extract, merge, fill forms, etc.)	`routes/process.md`

Default to HTML. Only use LaTeX route when user explicitly requests it.

MANDATORY: Read Route File Before Implementation

Before implementation, you MUST:

Determine the route (HTML / LaTeX / Process)
Read the route file (routes/html.md, routes/latex.md, or routes/process.md)
Only then proceed with implementation

This file (SKILL.md) contains constraints and principles. Route files contain how-to details.

Decision Rules

Route Selection

User Says	Route
"Create a PDF", "Make a report", "Write a paper"	HTML
"Use LaTeX", "Compile .tex", "Use Tectonic"	LaTeX
"Extract text from PDF", "Merge these PDFs", "Fill this form"	Process

Cover Style Selection (HTML Route)

Context	Style
Academic paper, thesis, formal coursework	Minimal (white, centered, no decoration)
Reports, proposals, professional documents	Designed (choose from style reference in html.md)
Uncertain	Default to Designed — plain text cover = mediocre

Key principle : Cover background separates "acceptable" from "impressive". See html.md for 11 style options.

Citation Format Selection

Document Language	Format
Chinese	GB/T 7714 (use [J][M][D] identifiers)
English	APA
Mixed	Chinese refs → GB/T 7714, English refs → APA

Quick Start

Use the unified CLI for all operations:

# Check environment (JSON output, exit code 0=ok, 2=missing deps)
/app/.kimi/skills/kimi-pdf/scripts/pdf.sh check

# Auto-fix missing dependencies (idempotent, safe to run multiple times)
/app/.kimi/skills/kimi-pdf/scripts/pdf.sh fix

# Convert HTML to PDF
/app/.kimi/skills/kimi-pdf/scripts/pdf.sh html input.html

# Compile LaTeX to PDF
/app/.kimi/skills/kimi-pdf/scripts/pdf.sh latex input.tex

Exit codes:

0 = success
1 = usage error
2 = dependency missing (run pdf.sh fix)
3 = runtime error

Dependencies by route:

HTML route : Node.js, Playwright, Chromium
Process route : Python 3, pikepdf, pdfplumber
LaTeX route : Tectonic

Core Constraints (Must Follow)

1. Output Language

Output language must match user's query language.

User writes in Chinese → PDF content in Chinese
User writes in English → PDF content in English
User explicitly specifies language → Follow user's specification

2. Word Count and Page Constraints

Strictly follow user-specified word/page count requirements
Do not arbitrarily inflate content length

3. Citation and Search Standards

CRITICAL: Search Before Writing

DO NOT fabricate information. When in doubt, SEARCH.

If content involves ANY of these, you MUST search FIRST before writing:

Statistics, numbers, percentages, rankings
Policies, regulations, laws, standards
Academic research, theories, methodologies
Current events, recent developments
Anything you're not 100% certain about

When Search is Required

Scenario	Search?	Notes
Statistics, data	Required	e.g., "2024 employment rate"
Policies, regulations	Required	e.g., "startup subsidies"
Research, papers	Required	e.g., "effectiveness of method X"
Time-sensitive content	Required	Information after knowledge cutoff
Uncertain facts	Required	If unsure, always search
Common knowledge	Not needed	e.g., "water boils at 100°C"

Search workflow :

Identify facts/data requiring verification
Search for authentic sources
If results insufficient, iterate search until reliable info obtained
Include real sources in references
If search fails repeatedly, tell the user instead of making up data

Citations Must Be Real

Fabricating references is prohibited. All citations must have:

Correct author/institution names
Accurate titles
Verifiable year, journal/source

Cross-references (Must Be Clickable)

As shown in <a href="#fig-1-1">Figure 1-1</a>...
From <a href="#eq-2-1">Equation (2-1)</a>...
See <a href="#sec3">Section 3</a>...

Note : id must be placed at container top (see CSS Counters section in html.md).

Content Quality Constraints

1. Word/Page Count Constraints

Must strictly follow user-specified word or page count requirements :

User Request	Execution Standard
Specific word count (e.g., "3000 words")	Within ±20%, i.e., 2400-3600 words
Specific page count (e.g., "5 pages")	Exactly equal, last page may be partial
Word count range (e.g., "2000-3000 words")	Must fall within range
No explicit requirement	Infer reasonably by document type; prefer thorough over superficial
Minimum specified (e.g., "more than 5000 words")	No more than 2x, i.e., 5000-10000 words

Prohibited behaviors :

Arbitrarily shortening content ("concise" is not an excuse)
Padding pages with excessive bullet lists (maintain high information density)
Exceeding twice the user's requested length

Special case - Resume/CV :

Resume should be 1 page unless user specifies otherwise
Use compact margins: margin: 1.5cm

2. Outline Adherence (Mandatory)

When user provides outline :

Strictly follow the user-provided outline structure
Section titles must match outline (minor wording adjustments OK, no level/order changes)
Do not add or remove sections arbitrarily
If outline seems problematic, ask user first before modifying

When no user outline :

Use standard structures based on document type:
- Academic papers : IMRaD (Introduction-Methods-Results-Discussion) or Introduction-Literature Review-Methods-Results-Discussion-Conclusion
- Business reports : Conclusion-first (Executive Summary → Detailed Analysis → Recommendations)
- Technical docs : Overview → Principles → Usage → Examples → FAQ
- Course assignments : Follow assignment structure requirements
Sections must have logical progression, no disconnects

Tech Stack Overview

Route	Tools	Purpose
HTML	Playwright + Paged.js	HTML → PDF conversion
HTML	KaTeX, Mermaid	Math formulas, diagrams
Process	pikepdf	Form filling, page operations, metadata
Process	pdfplumber	Text and table extraction
Process	LibreOffice	Office → PDF conversion
LaTeX	Tectonic	LaTeX → PDF compilation

Weekly Installs

Repository

thvroyal/kimi-skills

GitHub Stars

First Seen

Feb 4, 2026

Security Audits

Gen Agent Trust HubFail SocketPass SnykWarn

Installed on

gemini-cli74

codex74

amp73

github-copilot73

kimi-cli73

opencode73

GitHub Actions 官方文档查询助手 - 精准解答 CI/CD 工作流问题

45,200 周安装

Kimi-PDF：智能PDF生成与处理工具，支持HTML/LaTeX转换、合并、提取及表单填写

🇨🇳中文介绍

路由选择

强制要求：实施前必须阅读路由文件

相关 Skills

决策规则

路由选择

封面样式选择 (HTML 路由)

引用格式选择

快速开始

核心约束 (必须遵守)

1. 输出语言

2. 字数和页数约束

3. 引用和搜索标准

关键：写作前先搜索

何时需要搜索

引用必须真实

交叉引用 (必须可点击)

内容质量约束

1. 字数/页数约束

2. 大纲遵循 (强制)

技术栈概览

🇺🇸English

Route Selection

MANDATORY: Read Route File Before Implementation

Decision Rules

Route Selection

Cover Style Selection (HTML Route)

Citation Format Selection

Quick Start

Core Constraints (Must Follow)

1. Output Language

2. Word Count and Page Constraints

3. Citation and Search Standards

CRITICAL: Search Before Writing

When Search is Required

Citations Must Be Real

Cross-references (Must Be Clickable)

Content Quality Constraints

1. Word/Page Count Constraints

2. Outline Adherence (Mandatory)

Tech Stack Overview

最新 Skills