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

evals/evals.json

View on GitHub
{
  "skill_name": "typst-paper",
  "evals": [
    {
      "id": 1,
      "prompt": "Compile my Typst paper and tell me whether the layout looks obviously wrong for an IEEE-style submission.",
      "expected_output": "Route to compile and format modules, run uv-backed Typst checks, and return Typst-oriented comments.",
      "files": [],
      "assertions": [
        {"type": "regex", "pattern": "(compile|format)", "description": "correct modules routed"},
        {"type": "regex", "pattern": "(typst|Typst)", "description": "Typst-specific handling"},
        {"type": "regex", "pattern": "// .+\\[Severity:", "description": "Typst comment format used"}
      ]
    },
    {
      "id": 2,
      "prompt": "Validate the bibliography in main.typ, whether it uses BibTeX or Hayagriva, and point out any missing citations.",
      "expected_output": "Choose the bibliography module correctly and surface Typst citation/bibliography mismatches.",
      "files": [],
      "assertions": [
        {"type": "contains", "text": "bibliography", "description": "bibliography module routed"},
        {"type": "regex", "pattern": "(BibTeX|Hayagriva|@cite|#bibliography)", "description": "Typst bib format detected"},
        {"type": "regex", "pattern": "(missing|unused|unresolved)", "description": "citation issues reported"}
      ]
    },
    {
      "id": 3,
      "prompt": "Polish the abstract wording in my Typst paper and help me translate one Chinese paragraph into academic English without breaking labels.",
      "expected_output": "Route to expression and translation modules while preserving Typst syntax.",
      "files": [],
      "assertions": [
        {"type": "regex", "pattern": "(expression|translation)", "description": "correct modules routed"},
        {"type": "not_contains", "text": "<label-rewritten>", "description": "Typst labels preserved"}
      ]
    },
    {
      "id": 4,
      "prompt": "My Typst project uses a Hayagriva YAML bibliography. Validate it, then tell me whether any citations used in the paper are missing or unused.",
      "expected_output": "Choose the bibliography path correctly for Hayagriva input, preserve Typst citation syntax, and surface missing, unused, or mismatched references.",
      "files": [],
      "assertions": [
        {"type": "contains", "text": "bibliography", "description": "bibliography module routed"},
        {"type": "regex", "pattern": "(Hayagriva|YAML|\\.yml)", "description": "Hayagriva format recognized"},
        {"type": "regex", "pattern": "(missing|unused|mismatch)", "description": "reference issues reported"}
      ]
    },
    {
      "id": 5,
      "prompt": "Review the related work section in main.typ for weak literature organization, missing gap derivation, and cross-section logic problems, but do not rewrite labels or math.",
      "expected_output": "Route to the logic module, flag enumeration-heavy related work or missing gap statements, and keep Typst labels, cites, and math untouched.",
      "files": [],
      "assertions": [
        {"type": "contains", "text": "logic", "description": "logic module routed"},
        {"type": "regex", "pattern": "(gap|enumerat|organization)", "description": "literature quality assessed"},
        {"type": "not_contains", "text": "@cite-rewritten", "description": "@cite references preserved"}
      ]
    },
    {
      "id": 6,
      "prompt": "Check whether the introduction in my Typst paper jumps from broad background straight to our method without establishing the bottleneck and prior-work limitations.",
      "expected_output": "Route to the logic module and flag introduction funnel breaks such as background-to-contribution jumps or missing literature-derived insufficiencies.",
      "files": [],
      "assertions": [
        {"type": "contains", "text": "logic", "description": "logic module routed"},
        {"type": "regex", "pattern": "(funnel|gap|bottleneck|jump)", "description": "funnel analysis present"}
      ]
    },
    {
      "id": 7,
      "prompt": "Tell me whether the abstract, contribution claims, and conclusion in this Typst paper are aligned, or if they are saying different things.",
      "expected_output": "Route to the logic module and report cross-section alignment issues involving problem, method, result, and contribution coverage.",
      "files": [],
      "assertions": [
        {"type": "contains", "text": "logic", "description": "logic module routed"},
        {"type": "regex", "pattern": "(alignment|consistency|cross-section|drift)", "description": "cross-section analysis present"}
      ]
    },
    {
      "id": 8,
      "prompt": "My Typst paper is in Chinese. Check the introduction for AI-sounding filler, repeated openings, and low-information paragraphs without breaking labels.",
      "expected_output": "Route to the deai module with Chinese-aware heuristics and preserve Typst syntax while surfacing filler, parallel openings, and low-information density issues.",
      "files": [],
      "assertions": [
        {"type": "contains", "text": "deai", "description": "deai module routed"},
        {"type": "regex", "pattern": "(AI.?痕迹|AI.?trace|filler|填充)", "description": "AI pattern detection present"},
        {"type": "regex", "pattern": "[\\u4e00-\\u9fff]{5,}", "description": "Chinese-aware analysis present"}
      ]
    },
    {
      "id": 9,
      "prompt": "Review the discussion section in main.typ and tell me if it is just a data dump without mechanism, comparison, limitations, or implications.",
      "expected_output": "Route to the experiment module and flag shallow or unlayered discussion structure for a Typst paper.",
      "files": [],
      "assertions": [
        {"type": "contains", "text": "experiment", "description": "experiment module routed"},
        {"type": "regex", "pattern": "(layer|mechanism|limitation|implication|depth)", "description": "discussion depth assessed"}
      ]
    },
    {
      "id": 10,
      "prompt": "Review the algorithm-figure block in my IEEE-style Typst paper and tell me whether the caption, line numbers, and style-algorithm hook are in good shape.",
      "expected_output": "Route to the pseudocode module, inspect algorithmic usage, and distinguish missing caption or wrapper issues from line-number recommendations.",
      "files": [],
      "assertions": [
        {"type": "contains", "text": "pseudocode", "description": "pseudocode module routed"},
        {"type": "regex", "pattern": "(algorithm-figure|style-algorithm|caption)", "description": "Typst pseudocode details checked"},
        {"type": "regex", "pattern": "(recommended|not required|IEEE-like)", "description": "advisory distinction present"}
      ]
    },
    {
      "id": 11,
      "prompt": "I used lovelace for a custom pseudocode block in main.typ. Tell me whether I still need a figure wrapper and caption for an IEEE-like submission.",
      "expected_output": "Route to the pseudocode module, identify lovelace usage, and explain when figure wrapping and captions become mandatory for IEEE-like output.",
      "files": [],
      "assertions": [
        {"type": "contains", "text": "pseudocode", "description": "pseudocode module routed"},
        {"type": "regex", "pattern": "(lovelace|figure|caption)", "description": "lovelace wrapper guidance present"},
        {"type": "regex", "pattern": "\\[Severity: (Critical|Major|Minor)\\]", "description": "severity format correct"}
      ]
    }
  ]
}
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