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/REVIEWER_PERSPECTIVE.md

View on GitHub
# Reviewer Perspective Guide

## Table of Contents
- [Four-Dimensional Review Criteria](#four-dimensional-review-criteria)
- [Six-Point Scoring Scale](#six-point-scoring-scale)
- [Reviewer Reading Behavior](#reviewer-reading-behavior)
- [Pre-Submission Checklist](#pre-submission-checklist)
- [Rebuttal Best Practices](#rebuttal-best-practices)

## Four-Dimensional Review Criteria

| Criterion | What Reviewers Look For | Common Deduction Reasons |
|-----------|------------------------|--------------------------|
| **Quality** | Technical soundness, well-supported claims | Flawed proofs, missing baselines, unfair comparisons |
| **Clarity** | Clear writing, reproducible by experts | Ambiguous notation, missing details, poor organization |
| **Significance** | Community impact, advances understanding | Incremental improvement, narrow applicability |
| **Originality** | New insights (doesn't require new method) | Known results, obvious extensions |

## Six-Point Scoring Scale

(NeurIPS scale, widely adopted)

| Score | Rating | Typical Characteristics |
|-------|--------|------------------------|
| 6 | **Strong Accept** | Groundbreaking contribution, technically flawless, very high impact |
| 5 | **Accept** | Technically solid, high impact, well-written |
| 4 | **Borderline Accept** | Solid contribution, limited evaluation or novelty concerns |
| 3 | **Borderline Reject** | Technical merits but weaknesses outweigh strengths |
| 2 | **Reject** | Technical flaws, insufficient evaluation, unclear contribution |
| 1 | **Strong Reject** | Known results, ethical issues, or fundamental errors |

### What Moves Papers from 3→4 (Borderline → Accept):
- [ ] Address obvious weakness proactively (limitations section)
- [ ] Add one more strong baseline or ablation
- [ ] Improve clarity of main contribution statement
- [ ] Add reproducibility details (code, hyperparameters)

## Reviewer Reading Behavior

Understanding how reviewers read helps prioritize your effort:

| Paper Section | % Reviewers Who Read | Time Spent | Implication |
|---------------|---------------------|------------|-------------|
| Abstract | 100% | 2-3 min | Must be perfect |
| Introduction | 90%+ (skimmed) | 3-5 min | Front-load contribution |
| Figures/Tables | Before methods | 2-3 min | Figure 1 is critical |
| Methods | Only if interested | 5-10 min | Don't bury the lede |
| Experiments | If methods seem sound | 5-10 min | Clear claims + evidence |
| Appendix | Rarely (<30%) | As needed | Supplementary only |

**Key Insight**: If your abstract and intro don't hook reviewers, they may never read your methods.

## Pre-Submission Checklist

### Universal Checklist (All Venues)
- [ ] Paper compiles without errors
- [ ] All figures are referenced in text
- [ ] All tables are referenced in text
- [ ] No orphaned citations (every \cite has a bib entry)
- [ ] No placeholder text (TODO, FIXME, XXX)
- [ ] Anonymous submission (no author names in blind review)
- [ ] Page limit respected (excluding references)
- [ ] Consistent notation throughout
- [ ] All acronyms defined on first use
- [ ] Limitations section included

### NeurIPS Specific (16 items)
- [ ] Paper checklist completed (Appendix)
- [ ] Broader Impact Statement included
- [ ] Code submission prepared (if applicable)
- [ ] Lay summary prepared (for accepted papers)
- [ ] Ethics review flagged if applicable
- [ ] Supplementary material ≤ 50MB
- [ ] Main paper ≤ 9 pages (+ unlimited references/appendix)
- [ ] Uses official NeurIPS style file
- [ ] Reproducibility details: random seeds, compute, datasets
- [ ] Error bars included with methodology specified
- [ ] Statistical significance tests where appropriate
- [ ] Dataset licensing and consent documented
- [ ] Potential negative societal impacts discussed
- [ ] Limitations clearly stated
- [ ] Comparison with appropriate baselines
- [ ] Ablation studies for key design choices

## Rebuttal Best Practices

### Dennett's Criticism Method (Adapted for Academic Rebuttals)
1. **Acknowledge**: Re-state the reviewer's concern fairly
2. **Agree**: Find points of agreement
3. **Learn**: Show what you learned from the criticism
4. **Respond**: Then (and only then) address disagreements with evidence

### Rebuttal Structure Template

```
We thank Reviewer [X] for their thoughtful feedback.

**[Concern 1: Brief summary]**

We agree that [acknowledgment]. To address this:
- [Action taken / experiment added / clarification provided]
- [Evidence: "Table X shows..." / "We added Section Y..."]

**[Concern 2: Brief summary]**

[Same structure...]

**Summary of Changes:**
- [Bullet list of all modifications]
```

### Common Rebuttal Mistakes
- ❌ Arguing that the reviewer is wrong
- ❌ Ignoring a concern (address ALL points)
- ❌ Promising future work instead of showing results
- ❌ Being defensive or dismissive
- ✅ Providing concrete evidence (new experiments, tables)
- ✅ Acknowledging valid criticisms
- ✅ Showing actual revisions made
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