Skip to content

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

typst-paper

Verified

Typst academic paper assistant for existing `.typ` paper projects in English or Chinese. Use this skill whenever the user wants to compile, audit, or improve a Typst paper, including format checks, bibliography validation for BibTeX or Hayagriva, grammar/sentence/logic review, expression polishing, translation, title optimization, pseudocode review, algorithm block cleanup, de-AI editing, experiment-section review, table structure validation, three-line table generation, abstract structure diagnosis, or journal adaptation. Trigger even when the user only mentions one Typst file, one bibliography issue, one pseudocode block, one section rewrite, "three-line table", "check abstract", or "reformat for another journal". Also trigger when the user mentions ".typ files", "typst compile error", "typst export", "typst bibliography", `algorithm-figure`, `lovelace`, or `algorithmic` even without saying the word "Typst" explicitly.

FileKindSize
SKILL.mdskill md7.5 KB
agents/openai.yamlconfig330 B
evals/evals.jsonconfig7.3 KB
examples/bibliography-and-title.mdmarkdown509 B
examples/compile-and-format.mdmarkdown495 B
examples/expression-and-translation.mdmarkdown554 B
references/ABSTRACT_STRUCTURE.mdmarkdown4.9 KB
references/BEST_PRACTICES.mdmarkdown391 B
references/CITATION_STYLES.mdmarkdown4.2 KB
references/CITATION_VERIFICATION.mdmarkdown4.9 KB
references/COMMON_ERRORS.mdmarkdown5.3 KB
references/DEAI_GUIDE.mdmarkdown14.9 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.mdmarkdown7.9 KB
references/TABLE_GUIDE.mdmarkdown2.6 KB
references/TEMPLATES.mdmarkdown2.5 KB
references/TERMINOLOGY.mdmarkdown9.9 KB
references/TRANSLATION_GUIDE.mdmarkdown11.4 KB
references/TYPST_SYNTAX.mdmarkdown9.8 KB
references/VENUES.mdmarkdown13.0 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.1 KB
references/modules/COMPILE.mdmarkdown1.2 KB
references/modules/DEAI.mdmarkdown2.8 KB
references/modules/EXPERIMENT.mdmarkdown3.8 KB
references/modules/EXPRESSION.mdmarkdown1.6 KB
references/modules/FORMAT.mdmarkdown1.1 KB
references/modules/GRAMMAR.mdmarkdown1.1 KB
references/modules/LOGIC.mdmarkdown5.4 KB
references/modules/PSEUDOCODE.mdmarkdown1.4 KB
references/modules/SENTENCES.mdmarkdown726 B
references/modules/TABLES.mdmarkdown1.3 KB
references/modules/TITLE.mdmarkdown7.3 KB
references/modules/TRANSLATION.mdmarkdown1.5 KB
references/modules/WORKFLOW.mdmarkdown706 B
scripts/analyze_abstract.pyscript17.3 KB
scripts/analyze_experiment.pyscript11.1 KB
scripts/analyze_grammar.pyscript3.6 KB
scripts/analyze_logic.pyscript18.8 KB
scripts/analyze_sentences.pyscript3.6 KB
scripts/check_format.pyscript11.3 KB
scripts/check_pseudocode.pyscript8.6 KB
scripts/check_references.pyscript14.1 KB
scripts/check_tables.pyscript9.8 KB
scripts/compile.pyscript8.1 KB
scripts/deai_batch.pyscript10.2 KB
scripts/deai_check.pyscript19.2 KB
scripts/generate_table.pyscript6.7 KB
scripts/improve_expression.pyscript3.2 KB
scripts/online_bib_verify.pyscript11.9 KB
scripts/optimize_title.pyscript16.9 KB
scripts/parsers.pyscript8.0 KB
scripts/translate_academic.pyscript4.2 KB
scripts/verify_bib.pyscript15.1 KB

references/WRITING_PHILOSOPHY.md

View on GitHub
# Writing Philosophy for Academic Papers

> "A paper is a short, rigorous, evidence-based technical story with a takeaway readers care about." — Neel Nanda

## Table of Contents
- [The Narrative Principle](#the-narrative-principle)
- [5-Sentence Abstract Formula](#5-sentence-abstract-formula)
- [Gopen-Swan 7 Principles](#gopen-swan-7-principles)
- [Word Choice](#word-choice)
- [Precision Over Brevity](#precision-over-brevity)
- [Micro-Level Tips](#micro-level-tips)
- [Section-by-Section Guide](#section-by-section-guide)
- [Time Allocation](#time-allocation)

## The Narrative Principle

(Neel Nanda, Google DeepMind)

Your paper is NOT a collection of experiments — it's a story with ONE clear contribution.

**Three Pillars** (must be crystal clear by end of introduction):

| Pillar | Description | Example |
|--------|-------------|---------|
| **The What** | 1-3 specific novel claims within cohesive theme | "We prove that X achieves Y under condition Z" |
| **The Why** | Rigorous empirical evidence supporting claims | Strong baselines, experiments distinguishing hypotheses |
| **The So What** | Why readers should care | Connection to recognized community problems |

**If you cannot state your contribution in one sentence, you don't yet have a paper.**

## 5-Sentence Abstract Formula

(Sebastian Farquhar, DeepMind)

1. What you achieved: "We introduce...", "We prove...", "We demonstrate..."
2. Why this is hard and important
3. How you do it (with specialist keywords for discoverability)
4. What evidence you have
5. Your most remarkable number/result

**Delete** generic openings like "Large language models have achieved remarkable success..."

## Gopen-Swan 7 Principles

(Based on "The Science of Scientific Writing")

| # | Principle | Rule | Example |
|---|-----------|------|---------|
| 1 | **Subject-verb proximity** | Keep subject and verb close | ❌ "The model, which was trained on..., achieves" → ✅ "The model achieves... after training on..." |
| 2 | **Stress position** | Place emphasis at sentence ends | ❌ "Accuracy improves by 15% when using attention" → ✅ "When using attention, accuracy improves by **15%**" |
| 3 | **Topic position** | Put context first, new info after | ✅ "Given these constraints, we propose..." |
| 4 | **Old before new** | Familiar info → unfamiliar info | Link backward, then introduce new |
| 5 | **One unit, one function** | Each paragraph makes one point | Split multi-point paragraphs |
| 6 | **Action in verb** | Use verbs, not nominalizations | ❌ "We performed an analysis" → ✅ "We analyzed" |
| 7 | **Context before new** | Set stage before presenting | Explain before showing equation |

## Word Choice

(Zachary Lipton)

### Be Specific
- ❌ "performance" → ✅ "accuracy" or "latency" (say what you mean)
- ❌ "significant" → ✅ "statistically significant (p < 0.05)" or remove

### Eliminate Hedging
Drop "may" and "can" unless genuinely uncertain.
- ❌ "This may improve performance" → ✅ "This improves accuracy by 3.2%"

### Avoid Incremental Vocabulary
- ❌ "combine," "modify," "expand" → ✅ "develop," "propose," "introduce"

### Delete Intensifiers
- ❌ "provides *very* tight approximation" → ✅ "provides tight approximation"

## Precision Over Brevity

(Jacob Steinhardt, UC Berkeley)

- **Consistent terminology**: Different terms for same concept creates confusion. Pick one and stick with it.
- **State assumptions formally**: Before theorems, list all assumptions explicitly
- **Intuition + rigor**: Provide intuitive explanations alongside formal proofs
- **Define before use**: Every symbol and term defined before first use

## Micro-Level Tips

(Ethan Perez, Anthropic)

- [ ] **Minimize pronouns**: ❌ "This shows..." → ✅ "This result shows..."
- [ ] **Verbs early**: Position verbs near sentence start
- [ ] **Unfold apostrophes**: ❌ "X's Y" → ✅ "The Y of X" (when awkward)
- [ ] **Delete filler words**: "actually," "a bit," "very," "really," "basically," "quite," "essentially"
- [ ] **Avoid vague "this"**: Always attach a noun after "this"
- [ ] **Active voice**: ❌ "The method was applied" → ✅ "We applied the method"

## Section-by-Section Guide

| Section | Length | Key Requirements |
|---------|--------|-----------------|
| **Abstract** | 150-250 words | 5-sentence formula; delete generic openings |
| **Introduction** | 1-1.5 pages max | 2-4 bullet contribution list; methods should start by page 2-3 |
| **Methods** | As needed | Enable reimplementation; all hyperparameters listed |
| **Experiments** | Main body | State claim before each experiment; error bars mandatory |
| **Related Work** | 1-1.5 pages | Organize methodologically; each cited work needs individual discussion; max 2 clustered citations |
| **Limitations** | 0.5-1 page | Required by all major venues; pre-empt reviewer criticisms |

### Introduction Must Include:
- Clear problem statement
- 2-4 bullet contribution list (max 1-2 lines each)
- Brief approach overview
- **Citation integration**: Each cited work must be accompanied by a brief description of its contribution, method, or limitation — max 2 clustered citations without discussion (see STYLE_GUIDE.md Anti-Citation-Stacking Rules)

### Experiments Must Include:
- What claim each experiment supports
- Error bars with methodology (std dev vs std error)
- Hyperparameter search ranges
- Compute infrastructure (GPU type, total hours)

## Time Allocation

(Neel Nanda)

Spend approximately **equal time** on each of:
1. The abstract
2. The introduction
3. The figures
4. Everything else combined

**Why?** Most reviewers form judgments before reaching your methods.

**Reader encounter order**: title → abstract → introduction → figures → maybe the rest.

## Sources

| Source | Key Contribution | Link |
|--------|-----------------|------|
| Neel Nanda (Google DeepMind) | The Narrative Principle | [How to Write ML Papers](https://www.alignmentforum.org/posts/eJGptPbbFPZGLpjsp/) |
| Sebastian Farquhar (DeepMind) | 5-sentence abstract formula | [How to Write ML Papers](https://sebastianfarquhar.com/on-research/2024/11/04/how_to_write_ml_papers/) |
| Gopen & Swan | 7 principles of reader expectations | [Science of Scientific Writing](https://cseweb.ucsd.edu/~swanson/papers/science-of-writing.pdf) |
| Zachary Lipton | Word choice, eliminating hedging | [Heuristics for Scientific Writing](https://www.approximatelycorrect.com/2018/01/29/heuristics-technical-scientific-writing-machine-learning-perspective/) |
| Jacob Steinhardt (UC Berkeley) | Precision, consistent terminology | [Writing Tips](https://bounded-regret.ghost.io/) |
| Ethan Perez (Anthropic) | Micro-level clarity tips | [Easy Paper Writing Tips](https://ethanperez.net/easy-paper-writing-tips/) |
| Andrej Karpathy | Single contribution focus | Various lectures |
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: 194kUpdated Claude CodeCodexVerifiedInstall