Latex Thesis Zh
Compile, inspect, and systematically polish a Chinese LaTeX degree thesis when chapters, templates, or XeLaTeX builds are blocking graduation deliverables.
Overview
LaTeX Thesis ZH is an agent skill most often used in Build (also Ship review, Build pm) that compiles, inspects, and mainline-polishes Chinese LaTeX theses across template, structure, logic, literature, and experiments.
Install
npx skills add https://github.com/bahayonghang/academic-writing-skills --skill latex-thesis-zhWhat is this skill?
- Infers and sequences thesis modules—compile, template, structure, consistency, logic, literature, and experiments—from n
- Detects common Chinese thesis templates such as thuthesis, pkuthss, and ctexbook before compile troubleshooting
- Runs uv-backed scripts against the project entry file and returns thesis-focused findings or chapter mainline writing pl
- Checks chapter structure plus terminology and abbreviation consistency across the manuscript
- Asks only for missing main.tex or context instead of generic chat-only LaTeX guesses
- Multi-module routing across compile, template, structure, consistency, logic, literature, and experiments
- Template families referenced include thuthesis, pkuthss, and ctexbook
Adoption & trust: 2.3k installs on skills.sh; 318 GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You have a Chinese LaTeX thesis with failing XeLaTeX builds, unclear template setup, or inconsistent chapters and terms, and chat-only advice does not trace the real main.tex pipeline.
Who is it for?
Graduate students and indie researchers maintaining a Chinese LaTeX thesis repo who want module-routed review, compile triage, and terminology consistency across long chapters.
Skip if: English-only theses, Word-only workflows, or one-page marketing copy where LaTeX template and degree-thesis module routing add no value.
When should I use this skill?
Review a Chinese LaTeX thesis project, infer the right module from the request, sequence compatible modules, clarify missing entry-file or context, run uv-backed scripts, and return thesis-focused findings or chapter-mai
What do I get? / Deliverables
You get template-aware compile diagnosis, structured chapter and consistency findings, and chapter-mainline writing plans grounded in the modules your project actually needs.
- Template and compile troubleshooting report
- Structure overview with consistency findings on terms and abbreviations
- Chapter mainline writing plan keyed to routed modules
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
The skill’s center of gravity is producing and hardening the thesis manuscript and its LaTeX project—the canonical solo-builder shelf for long-form written deliverables is Build → docs, even when compile checks feel like shipping work. Subphase docs fits structured thesis chapters, bibliography, abbreviations, and main.tex-centric workflows rather than app UI or API integration.
Where it fits
Map chapter order and fix abbreviation tables before submitting a draft chapter to your advisor.
Diagnose recurring XeLaTeX compile errors after template or package changes near submission.
Sequence logic, literature, and experiment modules into a mainline plan for the next writing sprint.
Align experiment narrative and citations so results chapters match the declared thesis structure.
How it compares
Use this modular thesis skill instead of generic LaTeX snippets that skip template detection, uv-backed checks, and Chinese degree-thesis structure rules.
Common Questions / FAQ
Who is latex-thesis-zh for?
It is for people writing Chinese academic degree theses in LaTeX who need compile reliability, template clarity, and chapter-level polish—not casual note-taking or non-thesis docs.
When should I use latex-thesis-zh?
During Build when drafting or restructuring chapters and fixing main.tex; during Ship review when XeLaTeX fails or terminology and abbreviations drift; and during Build pm when you need a sequenced plan for the next chapter mainline pass.
Is latex-thesis-zh safe to install?
Treat it like any agent skill that can run local scripts: review the Security Audits panel on this Prism page and inspect uv-backed commands before running them on sensitive thesis sources.
SKILL.md
READMESKILL.md - Latex Thesis Zh
interface: display_name: "LaTeX Thesis ZH" short_description: "Compile, inspect, and mainline-polish Chinese LaTeX theses across template, structure, logic, literature, and experiments" default_prompt: "Review my Chinese LaTeX thesis project, infer the right module from the request, sequence compatible modules when needed, ask only for missing entry-file or context details, run the relevant uv-backed scripts, and return thesis-focused findings or chapter-mainline writing plans." { "skill_name": "latex-thesis-zh", "evals": [ { "id": 1, "prompt": "帮我定位这个中文学位论文 main.tex 为什么 XeLaTeX 一直编译失败，并判断是不是 thuthesis 模板。", "expected_output": "先识别模板，再走 compile 模块，返回模板结论和编译排障建议。", "files": [], "assertions": [ {"type": "regex", "pattern": "(template|compile|模板|编译)", "description": "correct modules routed"}, {"type": "regex", "pattern": "(thuthesis|pkuthss|ctexbook)", "description": "template detection attempted"}, {"type": "regex", "pattern": "[\\u4e00-\\u9fff]{5,}", "description": "Chinese output present"} ] }, { "id": 2, "prompt": "请梳理这篇硕士论文的章节结构，并检查术语和缩略语是否前后统一。", "expected_output": "路由到 structure 和 consistency 模块，并给出结构概览与一致性问题。", "files": [], "assertions": [ {"type": "regex", "pattern": "(structure|consistency|结构|一致)", "description": "correct modules routed"}, {"type": "regex", "pattern": "(术语|缩略|abbreviat)", "description": "terminology consistency checked"}, {"type": "regex", "pattern": "[\\u4e00-\\u9fff]{5,}", "description": "Chinese output present"} ] }, { "id": 3, "prompt": "按 GB/T 7714 帮我检查参考文献，再看看绪论是不是有明显 AI 腔。", "expected_output": "路由到 bibliography 和 deai 模块，分别输出格式问题和去 AI 化建议。", "files": [], "assertions": [ {"type": "regex", "pattern": "(bibliography|deai|参考文献|去AI)", "description": "correct modules routed"}, {"type": "regex", "pattern": "(GB.?T.?7714|国标)", "description": "GB/T standard referenced"}, {"type": "not_contains", "text": "\\cite{fabricated", "description": "no fabricated citations"} ] }, { "id": 4, "prompt": "请检查 related work 的逻辑链条，尤其是有没有只按作者年份罗列文献、以及有没有把研究空白推导出来。", "expected_output": "路由到 logic 模块，指出文献综述的罗列式写法、研究空白缺失或跨章节闭合问题，但不改引用和公式。", "files": [], "assertions": [ {"type": "contains", "text": "logic", "description": "logic module routed"}, {"type": "regex", "pattern": "(罗列|研究空白|gap|A1|A3)", "description": "literature review quality checked"}, {"type": "not_contains", "text": "\\cite{fabricated", "description": "no fabricated citations"} ] }, { "id": 5, "prompt": "帮我看看实验章节和论文标题：实验写法是否像学位论文而不是项目汇报，标题是否过于空泛。", "expected_output": "同时覆盖 title 和 experiment 两类问题，返回标题建议以及实验章节在论证深度、结果讨论和结论闭合上的审阅意见。", "files": [], "assertions": [ {"type": "regex", "pattern": "(title|experiment|标题|实验)", "description": "correct modules routed"}, {"type": "regex", "pattern": "(建议|修改|优化)", "description": "actionable suggestions present"}, {"type": "regex", "pattern": "[\\u4e00-\\u9fff]{5,}", "description": "Chinese output present"} ] }, { "id": 6, "prompt": "请检查这篇中文学位论文是不是每一章、每一节、甚至四级标题后都写了导语；我担心很多地方标题后直接开始列点和公式。", "expected_output": "路由到 logic 模块，检查标题后是否缺少导语段落，重点标出直接进入列表、图表、公式或下一级标题的地方。", "files": [], "assertions": [ {"type": "contains", "text": "logic", "description": "logic module routed"}, {"type": "regex", "pattern": "(导语|lead-in|S1)", "description": "heading lead-in check performed"}, {"type": "regex", "pattern": "[\\u4e00-\\u9fff]{5,}", "description": "Chinese output present"} ] }, { "id": 7, "prompt": "帮我看看章节衔接是不是太生硬，尤其是小节标题下面经常只有一句短话就马上开始表格和条目，这样像不像大论文规范问题？", "expected_output": "识别为 logic/structure 相关问题，指出导语缺失或导语过短的标题层级，并说明这是中文学位论文的结构与逻辑衔接问题。", "files": [], "assertions": [ {"type": "regex"