Skip to content

brycewang-stanford/Auto-Empirical-Research-Skills / skills/35-bahayonghang-academic-writing-skills/skills/latex-paper-en

latex-paper-en

Verified

English LaTeX academic paper assistant for existing `.tex` projects. Use this skill whenever the user wants to compile, lint, audit, or improve an English LaTeX conference or journal paper such as IEEE, ACM, Springer, NeurIPS, or ICML submissions. Trigger even when the user only mentions one paper issue, such as bibliography errors, grammar cleanup, sentence splitting, logic review, expression polishing, translation, title optimization, figure checks, pseudocode review, algorithm block cleanup, de-AI editing, experiment-section review, table structure validation, three-line table generation, abstract structure diagnosis, or journal adaptation. Also trigger for "proofread my paper", "fix my LaTeX", "prepare for submission", "check my manuscript", "improve my writing", "three-line table", "booktabs", "check abstract", "reformat for another journal", "换投", `algorithm2e`, `algorithmicx`, `algpseudocodex`, `Require/Ensure`, or "Algorithm 1" when the user has a .tex file.

FileKindSize
SKILL.mdskill md8.5 KB
agents/openai.yamlconfig390 B
evals/evals.jsonconfig7.8 KB
examples/compile-and-bibliography.mdmarkdown551 B
examples/experiment-review.mdmarkdown527 B
examples/figures-and-title.mdmarkdown513 B
examples/grammar-and-logic.mdmarkdown687 B
examples/translation-and-deai.mdmarkdown630 B
references/ABSTRACT_STRUCTURE.mdmarkdown4.9 KB
references/BEST_PRACTICES.mdmarkdown456 B
references/CITATION_STYLES.mdmarkdown4.2 KB
references/CITATION_VERIFICATION.mdmarkdown4.1 KB
references/COMMON_ERRORS.mdmarkdown2.8 KB
references/COMPILATION.mdmarkdown2.0 KB
references/DEAI_GUIDE.mdmarkdown16.8 KB
references/FORBIDDEN_TERMS.mdmarkdown1.6 KB
references/JOURNAL_ABBREVIATIONS.mdmarkdown3.5 KB
references/JOURNAL_ADAPTATION_WORKFLOW.mdmarkdown3.6 KB
references/NUMBER_UNIT_GUIDE.mdmarkdown2.3 KB
references/REVIEWER_PERSPECTIVE.mdmarkdown4.9 KB
references/STYLE_GUIDE.mdmarkdown6.5 KB
references/TABLE_GUIDE.mdmarkdown3.7 KB
references/TERMINOLOGY.mdmarkdown9.9 KB
references/TRANSLATION_GUIDE.mdmarkdown11.4 KB
references/VENUES.mdmarkdown6.4 KB
references/WRITING_PHILOSOPHY.mdmarkdown6.7 KB
references/modules/ABSTRACT.mdmarkdown1.2 KB
references/modules/ADAPT.mdmarkdown1.3 KB
references/modules/BIBLIOGRAPHY.mdmarkdown1.3 KB
references/modules/CAPTION.mdmarkdown2.0 KB
references/modules/COMPILE.mdmarkdown2.8 KB
references/modules/DEAI.mdmarkdown1.0 KB
references/modules/EXPERIMENT.mdmarkdown3.8 KB
references/modules/EXPRESSION.mdmarkdown789 B
references/modules/FORMAT.mdmarkdown440 B
references/modules/GRAMMAR.mdmarkdown980 B
references/modules/LOGIC.mdmarkdown7.6 KB
references/modules/PSEUDOCODE.mdmarkdown1.7 KB
references/modules/SENTENCES.mdmarkdown575 B
references/modules/TABLES.mdmarkdown1.3 KB
references/modules/TITLE.mdmarkdown7.7 KB
references/modules/TRANSLATION.mdmarkdown1.1 KB
references/modules/WORKFLOW.mdmarkdown910 B
scripts/analyze_abstract.pyscript17.3 KB
scripts/analyze_experiment.pyscript18.1 KB
scripts/analyze_grammar.pyscript3.6 KB
scripts/analyze_logic.pyscript18.4 KB
scripts/analyze_sentences.pyscript3.6 KB
scripts/check_figures.pyscript6.4 KB
scripts/check_format.pyscript6.4 KB
scripts/check_pseudocode.pyscript11.2 KB
scripts/check_references.pyscript14.2 KB
scripts/check_tables.pyscript16.3 KB
scripts/compile.pyscript17.4 KB
scripts/deai_batch.pyscript9.9 KB
scripts/deai_check.pyscript16.4 KB
scripts/extract_prose.pyscript2.7 KB
scripts/generate_table.pyscript8.8 KB
scripts/improve_expression.pyscript3.2 KB
scripts/online_bib_verify.pyscript11.9 KB
scripts/optimize_title.pyscript15.4 KB
scripts/parsers.pyscript14.9 KB
scripts/translate_academic.pyscript5.1 KB
scripts/verify_bib.pyscript18.9 KB

references/modules/EXPERIMENT.md

View on GitHub
# Module: Experiment Review

**Trigger**: experiment, evaluation, baseline, ablation, significance, efficiency comparison

**Purpose**: Review an existing experiment or evaluation section and emit reviewer-style findings without drafting a replacement paragraph.

## Commands

```bash
uv run python -B scripts/analyze_experiment.py main.tex --section experiments
uv run python -B scripts/analyze_experiment.py main.tex --section results
```

## Review Focus

- baseline/comparator specificity
- metric and numeric evidence
- overclaiming or promotional wording
- missing ablation evidence
- missing statistical significance or variance reporting
- missing efficiency comparison
- conclusions that go beyond the evidence shown

## Raw Script Output

```latex
% EXPERIMENT (Line 42) [Severity: Major] [Priority: P1]: Comparison claim names only generic baselines; cite or name the exact comparator.
% EXPERIMENT (Line 42) [Severity: Major] [Priority: P1]: Performance claim is not tied to a concrete metric or numeric result.
```

## Skill-Layer Response

- Keep the final response in LaTeX-friendly review comment style.
- Do not rewrite the experiment section unless the user explicitly asks for revised prose.
- Never invent baselines, metrics, significance claims, or efficiency numbers.

---

## Discussion & Results-Literature Integration (B3-B4)

### B3: Discussion Depth — Attribution Over Repetition

**Rule**: The Discussion section must go beyond restating numbers. It should explain *why* results occur using causal/attribution language. A discussion that merely echoes tables without interpretation is shallow.

**Detection heuristic** (script-automated):
- Scan all visible lines in the `discussion` section
- Count lines containing attribution markers: `because|due to|owing to|as a result of|attributed to|caused by|mechanism|explains|explanation|reason|hypothesis|interpret|stems from|arises from|driven by|suggests that|indicates that`
- If ratio < 15% of total visible lines (minimum 5 lines) → Major/P1

| Pattern | Verdict |
|---------|---------|
| "Model A achieves 95%. Model B achieves 90%." | Shallow repetition (flag) |
| "Model A outperforms Model B, likely due to its ability to capture long-range dependencies." | Attribution present (pass) |

### B4: Results-Literature Echo

**Rule**: The Discussion should reference prior work cited in Related Work to compare findings. Citation keys from Related Work should reappear in Discussion to show the authors have contextualized their results.

**Detection heuristic** (script-automated):
- Extract citation keys (`\cite{...}`) from `related` section range
- Extract citation keys from `discussion` section range
- If zero overlap → Major/P1

**Fix**: Add sentences like "Consistent with findings by Smith et al. \cite{smith2020}, our results confirm..." or "Unlike the approach of Jones \cite{jones2019}, our method demonstrates..."

---

## Conclusion Completeness Check (B5)

**Rule**: A complete Conclusion must contain three elements:
1. **Core findings summary** — explicit restatement of what was demonstrated
2. **Implications** — broader impact or practical significance
3. **Limitations / Future work** — acknowledged boundaries and next steps

**Detection heuristic** (script-automated):
- Scan `conclusion` section for three keyword categories:
  - Findings: `we have shown|we demonstrated|results show|this paper has presented|our experiments confirm|we proposed|findings indicate|key finding|main result`
  - Implications: `implication|suggests that.*practical|enables|opens|paves the way|facilitates|contributes to|advance|potential for|applicable to`
  - Limitations: `limitation|future work|future direction|remain|challenge|could be extended|further research|further investigation|not addressed|beyond the scope|caveat`
- Missing limitations → Major/P1
- Missing implications → Minor/P2
- Missing findings summary → Minor/P2
rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 196kUpdated Claude CodeCodexVerifiedInstall