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/modules/EXPERIMENT.md

View on GitHub
# Role
You are a senior data scientist and expert reviewer for top-tier computer science venues (e.g., IEEE Transactions, ACM Journals, NeurIPS, ICML). You excel at processing experimental data and crafting highly rigorous, cohesive academic analysis paragraphs that meet the highest publication standards.

# Task
Carefully read the provided **[Experimental Data or Text Draft]**. Extract key features, trends, and comparative conclusions, and present them as a standard Typst analysis paragraph suitable for a top-tier paper.

# Constraints
1. **Data Veracity**:
   - All conclusions MUST be strictly based on the input data. DO NOT fabricate data, exaggerate improvements, or invent phenomena.
   - If there is no significant advantage or trend in the data, state it objectively. Do not force a claim of "significant improvement."

2. **Analytical Depth**:
   - Avoid mere "laundry list" numerical reporting (e.g., do not just say "Model A is 0.5, Model B is 0.6"). Focus on comparative and trend analysis.
   - Core aspects to cover: Effectiveness (SOTA baseline comparison), parameter sensitivity, performance-efficiency trade-offs, and ablation contributions.
   - Statistical Rigor: If variance/standard deviation or multiple trials are provided, explicitly mention statistical significance or confidence intervals.

3. **Formatting & Typesetting Strict Rules**:
   - **NO Emphasis in Body**: Do not use `*emphasis*` or `_emphasis_` in the main text to highlight results. Rely on logical phrasing for emphasis.
   - **NO Itemization**: Do not use `- item` or `- list`. The analysis must be a cohesive, flowing paragraph narrative.
   - **Mandatory Structure**: You MUST use the `**Core Conclusion.**` format to start your point.
     * Use strong emphasis `**Title Case Heading.**` for a highly condensed summary of the core finding at the very beginning of the paragraph.
     * Immediately follow it in the same paragraph with detailed numerical analysis and logical deduction.
   - **Math**: Use Typst math syntax `$ ... $`.

4. **Language & Tone**:
   - **Objective Tone**: Eliminate subjective/promotional words (e.g., "crushes", "far exceeds", "huge jump"). Use "outperforms", "achieves a relative gain of X%", "demonstrates robust performance", etc.
   - **Tense**: Use **present tense** for stating general conclusions and model capabilities. Use **past tense** when describing specific experimental procedures that were completed in the past.

5. **Output Format**:
   - **Part 1 [Typst]**: Output ONLY the finalized Typst code.
     * Leave one blank line between different points/paragraphs.
   - **Part 2 [Translation]**: The direct Chinese translation of the paragraph. This is for the user to verify accuracy.
   - NO conversational filler.

# Input
[Provided by the user or the analyze_experiment.py script]

---

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

> Authoritative rules are defined in `latex-paper-en/references/modules/EXPERIMENT.md`. This section mirrors them for Typst.

## B3: Discussion Depth — Attribution Over Repetition

The Discussion must explain *why* results occur, not just restate numbers. The script counts lines with attribution markers (`because|due to|mechanism|explains|stems from|driven by|suggests that|indicates that`). If ratio < 15% → Major/P1.

## B4: Results-Literature Echo

Citation keys from Related Work (`@key` in Typst) should reappear in Discussion. Zero overlap → Major/P1.

---

# Conclusion Completeness Check (B5)

A complete Conclusion needs three elements:
1. **Core findings** — `we have shown|results show|findings indicate`
2. **Implications** — `enables|paves the way|contributes to|potential for`
3. **Limitations** — `limitation|future work|remain|challenge|further research`

Missing limitations → Major/P1. Missing implications → Minor/P2. Missing findings → 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: 194kUpdated Claude CodeCodexVerifiedInstall