brycewang-stanford/Auto-Empirical-Research-Skills / skills/35-bahayonghang-academic-writing-skills/skills/latex-paper-en
latex-paper-en
VerifiedEnglish 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.
references/modules/LOGIC.md
View on GitHub# Module: Logical Coherence & Methodological Depth
**Trigger**: logic, coherence, 逻辑, methodology, argument structure, 论证
**Purpose**: Ensure logical flow between paragraphs and strengthen methodological rigor in academic writing.
```bash
uv run python -B scripts/analyze_logic.py main.tex
uv run python -B scripts/analyze_logic.py main.tex --section methods
```
**Focus Areas**:
**1. Paragraph-Level Coherence (AXES Model)**:
| Component | Description | Example |
|-----------|-------------|---------|
| **A**ssertion | Clear topic sentence stating the main claim | "Attention mechanisms improve sequence modeling." |
| **X**ample | Concrete evidence or data supporting the claim | "In our experiments, attention achieved 95% accuracy." |
| **E**xplanation | Analysis of why the evidence supports the claim | "This improvement stems from the ability to capture long-range dependencies." |
| **S**ignificance | Connection to broader argument or next paragraph | "This finding motivates our proposed architecture." |
**2. Transition Signals**:
| Relationship | Signals |
|--------------|---------|
| Addition | furthermore, moreover, in addition, additionally |
| Contrast | however, nevertheless, in contrast, conversely |
| Cause-Effect | therefore, consequently, as a result, thus |
| Sequence | first, subsequently, finally, meanwhile |
| Example | for instance, specifically, in particular |
**3. Methodological Depth Checklist**:
- [ ] Each claim is supported by evidence (data, citation, or logical reasoning)
- [ ] Method choices are justified (why this approach over alternatives?)
- [ ] Limitations are acknowledged explicitly
- [ ] Assumptions are stated clearly
- [ ] Reproducibility details are sufficient (parameters, datasets, metrics)
**4. Common Issues**:
| Issue | Problem | Fix |
|-------|---------|-----|
| Logical gap | Missing connection between paragraphs | Add transition sentence explaining the relationship |
| Unsupported claim | Assertion without evidence | Add citation, data, or reasoning |
| Shallow methodology | "We use X" without justification | Explain why X is appropriate for this problem |
| Hidden assumptions | Implicit prerequisites | State assumptions explicitly |
**Output Format**:
```latex
% LOGIC (Line 45) [Severity: Major] [Priority: P1]: Logical gap between paragraphs
% Issue: Paragraph jumps from problem description to solution without transition
% Current: "The data is noisy. We propose a filtering method."
% Suggested: "The data is noisy, which motivates the need for preprocessing. Therefore, we propose a filtering method."
% Rationale: Add causal transition to connect problem and solution
% METHODOLOGY (Line 78) [Severity: Major] [Priority: P1]: Unsupported method choice
% Issue: Method selection lacks justification
% Current: "We use ResNet as the backbone."
% Suggested: "We use ResNet as the backbone due to its proven effectiveness in feature extraction and skip connections that mitigate gradient vanishing."
% Rationale: Justify architectural choice with technical reasoning
```
**Section-Specific Guidelines**:
| Section | Coherence Focus | Methodology Focus |
|---------|-----------------|-------------------|
| Introduction | Problem → Gap → Contribution flow | Justify research significance |
| Related Work | Group by theme, compare explicitly | Position against prior work |
| Methods | Step-by-step logical progression | Justify every design choice |
| Experiments | Setup → Results → Analysis flow | Explain evaluation metrics |
| Discussion | Findings → Implications → Limitations | Acknowledge boundaries |
**Best Practices** (Based on [Elsevier](https://elsevier.blog/logical-academic-writing/), [Proof-Reading-Service](https://www.proof-reading-service.com/blogs/academic-publishing/a-guide-to-creating-clear-and-well-structured-scholarly-arguments)):
1. **One idea per paragraph**: Each paragraph should have a single, clear focus
2. **Topic sentences first**: Start each paragraph with its main claim
3. **Evidence chain**: Every claim needs support (data, citation, or logic)
4. **Explicit transitions**: Use signal words to show relationships
5. **Justify, don't just describe**: Explain *why*, not just *what*
---
## Literature Review Quality Validation (A1-A4)
These rules ensure the Related Work section synthesizes literature rather than merely cataloguing it.
### A1: Thematic Clustering (Not Author/Year Enumeration)
**Rule**: Related Work should organize references by research theme, not by author or publication year. Detecting 3+ consecutive sentences following an "Author (Year) proposed/introduced..." pattern signals enumeration.
**Detection heuristic** (script-automated):
- Regex: `^(In \d{4}|.*\(\d{4}\).*(?:proposed|introduced|presented|developed|designed))`
- Threshold: 3+ consecutive matching lines → Major/P1
| Pattern | Verdict |
|---------|---------|
| "Smith (2019) proposed X. Jones (2020) introduced Y. Lee (2021) designed Z." | Enumeration (flag) |
| "Attention-based methods have evolved... Smith (2019) and Jones (2020) both explored... However, Lee (2021) showed that..." | Thematic synthesis (pass) |
**Fix**: Reorganize by theme clusters; within each cluster, compare and contrast methods critically.
### A2: Critical Analysis After Each Theme Cluster (LLM-judgment)
**Rule**: Each thematic group must end with a synthesis sentence that compares, contrasts, or evaluates the cited works — not just list them. Look for evaluative language: "however", "despite", "a common limitation", "compared to".
*This rule is too nuanced for regex and requires LLM judgment during review.*
### A3: Research Gap Derivation at End of Related Work
**Rule**: The final paragraph of Related Work must contain explicit research gap language that motivates the current study.
**Detection heuristic** (script-automated):
- Scan last 10 lines of the `related` section
- Keywords: `gap|limitation|however.*(?:no|not|few)|remains|lack|overlooked|under-explored|open problem|yet to be|inadequate|insufficient`
- If no match → Major/P1
| Pattern | Verdict |
|---------|---------|
| "Despite these advances, existing methods remain unable to handle X." | Gap present (pass) |
| "Lee (2021) achieved 95% accuracy on benchmark Y." (section ends) | No gap (flag) |
### A4: Funnel-Shaped Citation Density (LLM-judgment)
**Rule**: Citation density should follow a broad→focused→specific funnel: start with the general field, narrow to the sub-problem, end with the most relevant prior work. A flat or inverted funnel suggests poor narrative structure.
*This rule requires LLM judgment to assess the narrative arc.*
---
## Cross-Section Logic Chain Closure (C3)
**Rule**: Contribution claims made in the Introduction must be explicitly answered in the Conclusion. If the Introduction states "we propose X" or "our contributions include Y", the Conclusion must contain corresponding answer language ("we have shown", "results demonstrate", "experiments confirm").
**Detection heuristic** (script-automated, `--cross-section` flag):
- Extract contribution keywords from `introduction` section
- Extract answer keywords from `conclusion` section
- If intro has claims but conclusion has zero answer language → Major/P1 (flagged as `[Script]` observation)
| Intro Claim | Expected Conclusion Answer |
|-------------|---------------------------|
| "We propose a novel attention mechanism." | "We have shown that the proposed attention mechanism achieves..." |
| "Our main contributions are: (1)..." | "Experiments confirm that contribution (1)..." |
**Note**: This check is inherently heuristic. Findings are framed as observations, not definitive judgments. False positives are possible when the conclusion uses different phrasing to address the same claims.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| 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: 472k | Updated | Claude CodeCodex | Verified | Install |
| 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: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |