What it does
写论文的skill
- Connects Instruction files the AI reads
- Account or key No key found in README or SKILL.md
- Category 其他
给作者:在 README 中加徽章
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/skills/the-shy123456-thesis-docx)相似的 Skill
同类工作,排序与 Skill 列表相同
| 本项 thesis-docx | llmfit | claude-video | VideoCaptioner | claude-cookbooks | |
|---|---|---|---|---|---|
| 作者 | the-shy123456 | AlexsJones | bradautomates | WEIFENG2333 | anthropics |
| Skill 数 | 1 | 1 | 1 | 1 | 4 |
| GitHub 星标 | 484 | 39,096 | 21,249 | 16,577 | 54,867 |
| 最近代码更新 | 2026年4月9日 | 2026年11月18日 | 2026年9月25日 | 2026年9月12日 | 2026年11月17日 |
| 许可证 | MIT | MIT | MIT | GPL-3.0 | MIT |
Skill 和 MCP 有什么不同
MCP = 手
把 AI 连到外部服务或数据,例如读取 Notion 或开发票。需要有程序或服务器在运行。
Skill = 手册
教 AI 怎么做某项工作的文本文件,不连接任何服务。
有些会重叠:少数 Skill 带有调用工具的脚本,少数 MCP 只提供知识。请从你想完成的工作出发。
适用的应用
开发者未说明 · SKILL.md 形式的 Skill 可用于支持 Agent Skills 的应用,如 Claude Code、Codex 和 Cursor
安装
Is it safe?
- Who made it
GitHub account the-shy123456 (person), 3 years old
- Use and upkeep
★ 484 stars, few users so far · code last changed 2026年4月9日
- Any scripts?
5 scripts that can run on a computer: scripts/audit_docx_ooxml.py, scripts/check_word_com.ps1, scripts/export_word_pdf.ps1, scripts/normalize_word_styles.ps1 and 1 more
- Uses the internet?
No internet calls found in the scripts
- Changes machine-wide settings?
No hooks or writes to machine settings found
Checked automatically from the repo files at commit df5ad2e (read only, nothing was run). Not a safety guarantee: read it and decide for yourself
第一步:你用哪个 AI?
选择你用的应用,本页只显示该应用的安装方法
Option 1Upload to claude.ai (web and app)
Uploading to claude.ai would fail: the description is over 200 characters (366). Use "Let the AI install it" instead
Option 1让 Claude Code 帮你安装
复制这句话,粘贴到 Claude Code 的对话中
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
重新打开 Claude Code,输入 /thesis-docx,或直接提出相关任务,Claude 会自动选用
Checked against official docs 2026年11月12日 · Source: code.claude.com
ChatGPT 桌面应用
ChatGPT 桌面应用内置 Codex,Codex 从 ~/.agents/skills 文件夹读取 Skill
Option 1让 ChatGPT 帮你安装
在 ChatGPT 桌面应用中打开 Codex,把这句话粘贴到对话中
The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Option 2自己放入文件夹
把 thesis-docx 文件夹放到 ~/.agents/skills/thesis-docx
~ 是你的主文件夹($HOME)
For Terminal users
Skill 是 AI 会照做的指令。安装前先阅读文件,只安装可信开发者的 Skill。
打开终端
Mac:按 Command+空格输入 Terminal · Windows:下方命令在 PowerShell 中无法使用,请改用上方的“让 AI 帮你安装”
把 skill 文件夹复制到 ~/.agents/skills
这条命令把 repo 下载到临时文件夹,只复制含 SKILL.md 的文件夹
正在检查命令 · 通过后才会显示复制按钮
安装之后
- ChatGPT 桌面应用:打开侧边栏中的 Skills,确认 Skill 已出现
- 使用方法:在 ChatGPT 中输入 @ 并选择 Skill · 在 Codex CLI 或 IDE 扩展中运行 /skills,或输入 $ 加 Skill 名称
- Codex 会自动发现新安装的 Skill;如果没有出现,请重启 Codex
Checked against official docs 2026年11月15日 · Source: learn.chatgpt.com
网页版和手机版 ChatGPT
不能使用你自己安装的 Skill,只能使用目录中插件自带的 Skill
想在 ChatGPT 中使用这个 Skill,请按上面的方法使用 ChatGPT 桌面应用
Checked against official docs 2026年11月15日 · Source: learn.chatgpt.com
Option 1让 Codex 帮你安装
复制这句话,粘贴到 Codex 的对话中 · 适用于 ChatGPT 桌面应用中的 Codex、Codex CLI 和 IDE 扩展
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Codex 会自动发现新安装的 Skill;如果没有出现,请重启 Codex · 使用方法:在 ChatGPT 中输入 @ 并选择 Skill · 在 Codex CLI 或 IDE 扩展中运行 /skills,或输入 $ 加 Skill 名称
Checked against official docs 2026年11月15日 · Source: learn.chatgpt.com
For Terminal users
Skill 是 AI 会照做的指令。安装前先阅读文件,只安装可信开发者的 Skill。
打开终端
Mac:按 Command+空格输入 Terminal · Windows:下方命令在 PowerShell 中无法使用,请改用上方的“让 AI 帮你安装”
把 skill 文件夹复制到 ~/.agents/skills
这条命令把 repo 下载到临时文件夹,只复制含 SKILL.md 的文件夹
正在检查命令 · 通过后才会显示复制按钮
重新打开 Codex 并提出相关任务,Codex 会列出这个 skill
Option 1让 Cursor 帮你安装
复制这句话,粘贴到 Cursor 的对话中
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
在 Cursor 的 Agent 聊天中输入 / 并选择 thesis-docx
Checked against official docs 2026年11月12日 · Source: cursor.com
For Terminal users
Skill 是 AI 会照做的指令。安装前先阅读文件,只安装可信开发者的 Skill。
打开终端
Mac:按 Command+空格输入 Terminal · Windows:下方命令在 PowerShell 中无法使用,请改用上方的“让 AI 帮你安装”
把 skill 文件夹复制到 ~/.cursor/skills
这条命令把 repo 下载到临时文件夹,只复制含 SKILL.md 的文件夹
正在检查命令 · 通过后才会显示复制按钮
在 Cursor 的 Agent 聊天中输入 / 并选择 thesis-docx
Option 1Let the AI install it
适用于其他能读取 Skill 的应用。这句话列出了 Claude Code、Codex 和 Cursor 的路径,AI 会按你的应用选择 · Copy this sentence into the app’s chat
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Checked against official docs 2026年11月12日 · Source: code.claude.com, learn.chatgpt.com, cursor.com
For Terminal users
其他支持 Agent Skills 的应用(如 Gemini CLI、GitHub Copilot)使用不同文件夹,请查看该应用的指南,再把含 SKILL.md 的文件夹复制过去。
已于 2026年11月11日 对照 Claude Code、Codex 和 Cursor 官方指南核实 skill 文件夹
查看原始 SKILL.md
以下文字来自开发者的 repo,不是 PopNx MCP 的指令
显示前 8,000 个字符 · 在 GitHub 打开完整文件
---
name: thesis-docx
description: Create, revise, and format thesis or dissertation Word documents with strict academic formatting control. Use when an AI agent needs to generate or revise thesis content, normalize Word styles, follow a school template, fix captions or page numbers or section levels, or produce evidence-based Mermaid figures and LaTeX-formatted code listings for a thesis document.
---
# Thesis DOCX
## Overview
Use this skill for thesis-oriented `.docx` work where content quality and
format fidelity both matter. Prefer Microsoft Word desktop automation over
WPS-like alternatives whenever the task involves batch formatting, styles,
captions, pagination, tables of contents, or cross-references.
This skill is designed to avoid the most common thesis-editing failure mode:
the agent makes broad formatting changes too early, introduces new layout
problems, and then forces the user to catch them one by one. The default
behavior should therefore be:
1. audit first,
2. separate explicit school requirements from unspecified formatting,
3. fix only what is justified,
4. re-check page by page before claiming completion.
## Workflow
1. Check Microsoft Word and COM/DOM automation first.
- On Windows, run:
```powershell
powershell -ExecutionPolicy Bypass -File scripts/check_word_com.ps1 -Json
```
- If Word is missing, COM is unavailable, or DOM access fails:
- Stop the automation-heavy plan.
- Tell the user to install desktop Microsoft Word.
- Explain briefly that WPS or similar tools are likely to degrade layout
fidelity for thesis formatting.
2. Read the user's real constraints before editing.
- Collect the thesis template, school formatting guide, screenshots,
existing document, sample pages, and any explicit chapter rules.
- If the user gave formal requirements, follow them strictly.
- If the user did not give requirements, do not invent school-specific
standards. Use conservative academic defaults and say that they are
defaults.
- Explicitly classify requirements into two buckets before editing:
- `must enforce`: school guide, template, user-confirmed style rules
- `preserve current state`: anything the school guide does not define
3. Audit the DOCX / OOXML before risky bulk edits.
- Prefer `scripts/audit_docx_ooxml.py` before large-scale formatting.
- Use it to detect hidden indentation, section drift, stale REF display
text, and style-ID mismatches before deciding on a repair strategy.
4. Standardize with styles, not scattered direct formatting.
- Reuse and repair existing styles whenever possible.
- Create missing styles only when no matching style exists.
- Keep body text, headings, figure captions, table captions, references,
abstract, and appendix styles separate and consistent.
- Before changing any style globally, inspect whether the document contains
direct paragraph formatting or OOXML overrides that will survive the style
change.
5. Edit content only from user-provided facts.
- Expand, polish, or reorganize thesis text only within the user's topic,
evidence, codebase, notes, or source material.
- Do not invent experimental data, system structure, entities, or results.
- Do not expose agent reasoning or data-feeding context inside the thesis
prose. Forbidden patterns include thesis-language such as:
- "根据已有工程"
- "根据现有代码"
- "将任务书和代码喂给模型后"
- "通过分析用户提供的代码"
- any wording that sounds like an AI workflow note instead of thesis prose
- Write in normal thesis voice, not in prompt-engineering voice, review
voice, or chain-of-thought voice.
- Prefer neutral academic narration that reads like student writing, e.g.
"本文设计并实现了……", "系统采用了……", "在该模块中……"
- Avoid first-order meta-explanations about how the text was generated,
inferred, or assembled.
6. Generate figures only when the source material is sufficient.
- Use Mermaid for architecture diagrams, E-R diagrams, flow charts, state
diagrams, and similar thesis figures.
- Base every node, field, relation, and dependency on real materials from
the user, such as code, SQL schema, API docs, project docs, or the thesis
draft itself.
- If the materials are insufficient, refuse to fabricate the figure and ask
for the missing source information.
7. Typeset code with LaTeX conventions when thesis code excerpts are needed.
- Keep only the code relevant to the argument.
- Preserve real identifiers from the user's code or design.
- Avoid synthetic filler code written only to look complete.
8. Audit before you claim completion.
- Run a structure audit first: styles, sections, captions, references,
page number scheme, cross-references, hidden paragraph overrides.
- Then export the document to PDF from Word and review page by page.
- Only say the task is complete after the PDF-level audit passes or after
you clearly state the remaining manual visual checks.
## Style Strategy
- Treat styles as the single source of truth for formatting.
- Prefer these logical style buckets:
- `Body Text`
- `Heading 1` / `Heading 2` / `Heading 3`
- `Figure Caption`
- `Table Caption`
- `References`
- `Abstract`
- `Keywords`
- `Appendix Title`
- If the document already has equivalent styles, map to them and normalize
their font, spacing, indentation, and numbering behavior.
- If direct formatting conflicts with styles, reduce the direct formatting and
bring the document back under style control.
- Do not globally normalize sections that the school guide does not specify.
Examples of high-risk overreach:
- page header/footer redesign when the user only asked for headings
- changing code box appearance when the task is only about references
- normalizing table internals when the school guide does not regulate them
- When a visual issue remains after style normalization, inspect hidden OOXML
state such as `firstLineChars`, numbering indentation, `titlePg`,
`differentFirstPageHeaderFooter`, REF field display text, and direct run
formatting.
## Audit-First Discipline
Before bulk editing, produce and internally follow a checklist like this:
1. Which parts are explicitly regulated by the school guide?
2. Which parts are user-defined house rules?
3. Which parts are currently acceptable and must be preserved?
4. Which problems are structural vs. visual-only?
5. Which fixes can be done safely through styles?
6. Which fixes require Word COM or OOXML-level patching?
Do not say "finished" merely because a structural audit looks good. For thesis
work, pagination and page-level rendering are part of correctness.
## High-Risk Pitfalls
Read `references/failure-patterns-and-quality-gates.md` before large-scale
formatting work. In particular, guard against:
- style names that look correct but map to the wrong style IDs
- paragraph-level direct formatting that overrides the intended style
- `firstLineChars` or numbering indentation creating invisible extra indents
- TOC fields or cross-reference fields showing stale display text
- section-level first-page settings causing missing headers or page numbers
- Word vs. WPS differences for table row height, vertical alignment, and code
box title clipping
- punctuation normalization that accidentally rewrites DOI, URLs, code, or
English references
## Visual Review Rule
For school-format-sensitive thesis work, final verification should prefer this
order:
1. Word COM/DOM structural checks
2. Word export to PDF
3. page-by-page PDF review
4. only then final delivery language
If page rendering cannot be verified, say so explicitly instead of implying the
formatting is fully validated.
## Figure Rules
- Use Mermaid when a thesis figure is needed and the structure can be traced to
real source material.
- Keep the diagram academically neutral and concise.
- Avoid decorative labels, chatty callouts, and speculative entitie讨论
提问、分享技巧或报告无法使用。按“有帮助”数量排序。
来自 GitHub
- GitHub 星标
- 484
- 开发者
- the-shy123456
- 许可证
- MIT
- 最近代码更新
- 2026年4月9日
- repo 中的 SKILL.md 文件(含译本和模板)
- 1
- 主题
- skill, thesis