Use this skill to handle targeted issues in an existing Chinese LaTeX thesis project. Keep friction low: first determine the smallest matching module, then run the corresponding script, and finally return issues and suggestions in a thesis-review-friendly format.
Capability Summary
- Compile and diagnose XeLaTeX / LuaLaTeX / latexmk build issues.
- Check thesis formatting, GB/T 7714-related requirements, chapter structure, template type, and terminology consistency.
- Review logical coherence, literature review quality, experiment chapter writing, title expression, and AI traces.
- Provide actionable Chinese thesis revision suggestions without breaking citations, labels, and math environments.
Triggering
Use this skill when the user has an existing Chinese .tex thesis project and wants you to help with the following tasks:
- Compilation failure or uncertain toolchain
- Thesis formatting, national standard, or school template checks
- Chapter structure organization or template identification
- Terminology, abbreviation, and naming consistency checks
- Logical coherence, literature review quality, and cross-chapter closure checks
- Title optimization, academic expression, or de-AI-ification checks
- Language and structure review of experiment chapters
This skill should also be triggered even if the user mentions only a single issue, for example "help me determine whether this is thuthesis," "check the logic of the introduction," or "check the references according to GB/T 7714."
Do Not Use
Do not use this skill for:
- English conference or journal papers
- Typst projects
- Scenarios with only DOCX/PDF and no LaTeX source files
- Tasks involving pure literature research with no thesis project
- Writing a thesis from scratch
Module Router
| Module | Use when | Primary command | Read next |
|---|---|---|---|
compile |
Thesis build fails or toolchain is unclear | uv run python $SKILL_DIR/scripts/compile.py main.tex |
references/COMPILATION.md |
format |
User asks about thesis formatting or GB/T 7714 layout | uv run python $SKILL_DIR/scripts/check_format.py main.tex |
references/GB_STANDARD.md |
structure |
Need chapter/section map or thesis skeleton overview | uv run python $SKILL_DIR/scripts/map_structure.py main.tex |
references/STRUCTURE_GUIDE.md |
consistency |
Terms, abbreviations, or naming drift across chapters | uv run python $SKILL_DIR/scripts/check_consistency.py main.tex --terms |
references/LOGIC_COHERENCE.md |
template |
Need to identify or validate thesis class/template | uv run python $SKILL_DIR/scripts/detect_template.py main.tex |
references/UNIVERSITIES/generic.md |
bibliography |
GB/T 7714 or BibTeX validation | uv run python $SKILL_DIR/scripts/verify_bib.py references.bib --standard gb7714 |
references/GB_STANDARD.md |
title |
Optimize Chinese thesis titles and chapter titles | uv run python $SKILL_DIR/scripts/optimize_title.py main.tex --check |
references/TITLE_OPTIMIZATION.md |
deai |
Reduce AI-writing traces in visible Chinese prose | uv run python $SKILL_DIR/scripts/deai_check.py main.tex --section introduction |
references/DEAI_GUIDE.md |
logic |
Check logical coherence, lit review quality, cross-section closure | uv run python $SKILL_DIR/scripts/analyze_logic.py main.tex --section related |
references/LOGIC_COHERENCE.md |
experiment |
Review experiment chapter language and structure | uv run python $SKILL_DIR/scripts/analyze_experiment.py main.tex --section experiments |
references/modules/EXPERIMENT.md |
Required Inputs
- Thesis entry file, for example
main.tex。 - Optional
--section SECTION, when the user is focused on only one chapter or one section. - Optional bibliography path, when the task focuses on references.
- Optional school/template context, when the user cares about
thuthesis、pkuthssor specific university requirements.
If the parameters are incomplete, ask only for the entry .tex file and target module, and do not expand the questions further.
Output Contract
- Return issues in a LaTeX-friendly review format as much as possible:
% MODULE (L##) [Severity] [Priority]: ... - Clearly state the commands executed; if a script fails, you must report the exit code and key stderr.
- State "check results" and "suggested revisions" separately, to avoid mixing script diagnostics with body text polishing.
- By default preserve
\cite{}、\ref{}、\label{}, math environments, bibliography keys, and template macros.
Workflow
- Parse
$ARGUMENTSfor entry file and module. If missing, ask for the thesis.texentry file and target module. - Read the one reference file tied to that module (see "Read next" column).
- Run the corresponding script with
uv run python .... - Return findings as
% Module (L##) [Severity] [Priority]: .... Report exact command and exit code on failure. - If template and structure are both unclear, run
templatefirst, thenstructure.
Safety Boundaries
- Never fabricate citations, funding statements, acknowledgements, or academic claims.
- Never rewrite
\cite{},\ref{},\label{}, math blocks, or bibliography keys unless explicitly asked. - Treat title suggestions, de-AI revisions, and logic comments as proposals; keep source-preserving checks separate from edits.
Reference Map
references/COMPILATION.md: compilation strategy and toolchain diagnosis.references/GB_STANDARD.md: GB/T 7714 and bibliography-related checks.references/STRUCTURE_GUIDE.md: thesis structure expectations and chapter mapping.references/LOGIC_COHERENCE.md: logic, coherence, consistency, and literature-review expectations.references/TITLE_OPTIMIZATION.md: Chinese academic title heuristics.references/DEAI_GUIDE.md: de-AI review heuristics.references/modules/EXPERIMENT.md: experiment-chapter review criteria.references/UNIVERSITIES/: school/template-specific constraints after template detection.
Read only the reference files needed by the current module, and avoid loading the entire guide at once.
Example Requests
- "Help me locate why this Chinese thesis
main.texkeeps failing to compile with XeLaTeX, and determine whether it is a thuthesis template." - "Please organize the chapter structure of this master's thesis, and check whether the terminology and abbreviations are consistent throughout."
- "Help me check the references according to GB/T 7714, and also see whether the introduction has an obvious AI tone."
- "Check the logical chain and research gap derivation in related work, but do not touch any citations or formulas."