Skip to content

brycewang-stanford/Auto-Empirical-Research-Skills / skills/35-bahayonghang-academic-writing-skills/skills/latex-thesis-zh

latex-thesis-zh

Verified

Chinese LaTeX thesis assistant for existing .tex degree thesis projects (XeLaTeX/LuaLaTeX/latexmk). Use this skill whenever a user works on a Chinese master's or doctoral thesis needing compilation, GB/T 7714 bibliography checks, chapter structure mapping, template detection (thuthesis, pkuthss), terminology consistency, logic coherence review, heading lead-in checks, title optimization, de-AI editing, experiment chapter review, three-line table validation, or abstract structure diagnosis. Trigger even for single issues like "帮我编译论文", "检查国标格式", "看看绪论逻辑", "毕业论文", "学位论文", "硕士/博士论文", "三线表", "检查摘要", or "摘要结构".

FileKindSize
SKILL.mdskill md7.8 KB
agents/openai.yamlconfig348 B
evals/evals.jsonconfig7.1 KB
examples/bibliography-and-deai.mdmarkdown525 B
examples/compile-and-template.mdmarkdown463 B
examples/structure-and-consistency.mdmarkdown544 B
references/ABSTRACT_STRUCTURE.mdmarkdown4.9 KB
references/ACADEMIC_STYLE_ZH.mdmarkdown3.8 KB
references/CAPTION_GUIDE.mdmarkdown2.2 KB
references/COMPILATION.mdmarkdown2.0 KB
references/DEAI_GUIDE.mdmarkdown17.8 KB
references/FORBIDDEN_TERMS.mdmarkdown1.3 KB
references/GB_STANDARD.mdmarkdown3.8 KB
references/LOGIC_COHERENCE.mdmarkdown7.4 KB
references/STRUCTURE_GUIDE.mdmarkdown4.2 KB
references/TABLE_GUIDE.mdmarkdown2.6 KB
references/TITLE_OPTIMIZATION.mdmarkdown7.1 KB
references/UNIVERSITIES/generic.mdmarkdown2.1 KB
references/UNIVERSITIES/pku.mdmarkdown1.5 KB
references/UNIVERSITIES/tsinghua.mdmarkdown1.3 KB
references/UNIVERSITIES/yanshan.mdmarkdown1.2 KB
references/WRITING_PHILOSOPHY_ZH.mdmarkdown4.9 KB
references/modules/ABSTRACT.mdmarkdown1.2 KB
references/modules/BIBLIOGRAPHY.mdmarkdown1.3 KB
references/modules/COMPILE.mdmarkdown1.1 KB
references/modules/CONSISTENCY.mdmarkdown2.1 KB
references/modules/DEAI.mdmarkdown1.6 KB
references/modules/EXPERIMENT.mdmarkdown4.9 KB
references/modules/FORMAT.mdmarkdown988 B
references/modules/LOGIC.mdmarkdown2.3 KB
references/modules/TABLES.mdmarkdown1.3 KB
references/modules/TEMPLATE.mdmarkdown1.3 KB
references/modules/TITLE.mdmarkdown1.5 KB
scripts/analyze_abstract.pyscript17.3 KB
scripts/analyze_experiment.pyscript10.3 KB
scripts/analyze_logic.pyscript24.2 KB
scripts/check_consistency.pyscript12.1 KB
scripts/check_format.pyscript7.0 KB
scripts/check_references.pyscript17.6 KB
scripts/check_tables.pyscript16.3 KB
scripts/compile.pyscript15.8 KB
scripts/deai_batch.pyscript10.0 KB
scripts/deai_check.pyscript18.1 KB
scripts/detect_template.pyscript3.7 KB
scripts/generate_table.pyscript8.8 KB
scripts/map_structure.pyscript11.3 KB
scripts/online_bib_verify.pyscript11.9 KB
scripts/optimize_title.pyscript12.5 KB
scripts/parsers.pyscript10.7 KB
scripts/verify_bib.pyscript9.7 KB

references/ABSTRACT_STRUCTURE.md

View on GitHub
# Abstract Structure Guide

An effective academic abstract contains five structural elements that together tell a complete research story. This guide defines each element, how to detect it, and what makes it strong or weak.

## Five-Element Model

### 1. Background

**Purpose**: Establish the research context — the real-world problem, knowledge gap, or motivation.

**Detection markers (EN)**: "however", "remains unclear", "limited research", "growing interest", "challenge", "gap", "despite", "little is known", "increasingly important"

**Detection markers (ZH)**: "然而", "尚不清楚", "研究不足", "日益增长", "挑战", "空白", "尽管", "鲜有研究"

**Quality criteria**: Moves from broad context to specific gap in 1-2 sentences. A vague background restates the field name without identifying a gap.

### 2. Objective

**Purpose**: State what this specific study aims to answer or accomplish.

**Detection markers (EN)**: "this study aims", "we investigate", "the purpose of", "this paper presents", "we propose", "our goal", "in this work", "we address", "this research examines"

**Detection markers (ZH)**: "本文旨在", "本研究探讨", "本文提出", "研究目的", "为此我们", "本工作", "本文研究"

**Quality criteria**: Specific and falsifiable. A vague objective says "we study X" without specifying what aspect or what question about X.

### 3. Methods

**Purpose**: Describe the approach, data, tools, or analytical framework used.

**Detection markers (EN)**: "we propose", "using", "dataset", "participants", "method", "approach", "framework", "model", "algorithm", "collected", "trained", "evaluated", "sample", "experiment"

**Detection markers (ZH)**: "采用", "方法", "数据集", "样本", "模型", "算法", "框架", "实验", "训练", "评估"

**Quality criteria**: Names the specific technique, data source, or experimental setup. Missing methods make the abstract feel like an opinion piece.

### 4. Results

**Purpose**: Report the key findings with concrete data.

**Detection markers (EN)**: "results show", "achieved", "outperforms", "accuracy", "improved", "reduced", "found that", "demonstrates", "significant", numbers, percentages, p-values

**Detection markers (ZH)**: "结果表明", "达到", "优于", "准确率", "提高", "降低", "发现", "显著", numbers

**Quality criteria**: Must contain at least one quantitative finding (number, percentage, ratio, or comparative statement with magnitude). A results section without numbers is classified as VAGUE.

### 5. Conclusion / Significance

**Purpose**: State the contribution, implications, or practical value of the findings.

**Detection markers (EN)**: "our findings suggest", "contributes to", "implications", "demonstrates that", "can be used", "enables", "provides", "advances", "potential"

**Detection markers (ZH)**: "研究发现表明", "为...提供", "有助于", "具有...意义", "可用于", "推动", "贡献"

**Quality criteria**: Goes beyond restating results — connects findings to the broader field or practice. A hollow conclusion just repeats the results in different words.

## Common Defect Patterns

| Defect | Description | Typical fix |
|--------|-------------|-------------|
| Missing background | Jumps straight to "We propose..." | Add 1 sentence on the problem context |
| Vague objective | "We study deep learning for NLP" | Specify: "We investigate whether... improves..." |
| No methods | Describes results without explaining how | Add the core technique and data source |
| Data-free results | "Our method performs well" | Add a key metric: "achieves 94.2% F1" |
| Echo conclusion | Restates results verbatim | Add implication: "enabling real-time..." |

## Word Count Guidelines

| Context | Language | Range |
|---------|----------|-------|
| Default (no venue specified) | English | 150–250 words |
| Default (no venue specified) | Chinese | 200–300 characters |
| IEEE conference | English | 150–200 words |
| ACM conference | English | 150–250 words |
| NeurIPS/ICML | English | ≤ 200 words (strict) |
| Chinese thesis (GB/T) | Chinese | 300–500 characters |

Venue-specific limits override defaults. Check VENUES.md for exact requirements.

## Diagnostic Output Format

The analyzer outputs a per-element diagnosis:

```
Background:  ✅ PRESENT  — "Despite growing interest in X, the impact of Y remains unclear."
Objective:   ⚠️ VAGUE    — "This paper studies X." → Suggestion: specify the research question
Methods:     ✅ PRESENT  — "We propose a framework based on Z, evaluated on dataset W."
Results:     ❌ MISSING  — No quantitative findings detected → Add key metrics
Conclusion:  ⚠️ VAGUE    — Restates results without implications → Add practical significance
```

## Constraints

- Never alter the author's core claims or fabricate data
- Never add results or conclusions not present in the original text
- Preserve all citations, labels, and math environments
- Mark all modifications with brackets: [ADDED: ...] or [REVISED: ...]
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 323kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 323kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 323kUpdated Claude CodeCodexVerifiedInstall