Typst Academic Paper Assistant

Use this skill for targeted work on an existing Typst paper project. Route requests to the smallest useful module and keep outputs compatible with Typst source review.

Capability Summary

• Compile Typst projects and diagnose Typst CLI issues.
• Audit format, bibliography, grammar, sentence length, argument logic, expression quality, and AI traces.
• Review IEEE-like pseudocode blocks for algorithmic, algorithm-figure, lovelace, caption handling, and comment length.
• Support both BibTeX and Hayagriva bibliography files.
• Improve titles, translation, and experiment-section clarity for Typst papers.

Triggering

Use this skill when the user has an existing .typ paper project and wants help with:

• Typst compilation or export issues
• format or venue compliance
• bibliography validation for BibTeX or Hayagriva
• grammar, sentence, logic, or expression review
• translation or bilingual polishing
• title optimization
• pseudocode and algorithm-block review
• de-AI editing
• experiment-section review

Do Not Use

Do not use this skill for:

• LaTeX-first conference or thesis projects
• DOCX/PDF-only editing without Typst source
• thesis template detection or GB/T 7714 thesis workflows
• from-scratch paper planning or literature research
• multi-perspective review, scoring, or submission gate decisions (use paper-audit)
• standalone pseudocode drafting without a paper context

Module Router

Required Inputs

• main.typ or the Typst entry file.
• Optional --section SECTION for targeted analysis.
• Optional bibliography path when the request targets references.
• Optional venue context when the user cares about IEEE, ACM, Springer, or similar expectations.

If arguments are missing, ask only for the Typst entry file and the target module.

Output Contract

• Return findings in Typst diff-comment style whenever possible: // MODULE (Line N) [Severity] [Priority]: Issue ...
• Report the exact command used and the exit code when a script fails.
• Preserve @cite, <label>, math blocks, and Typst macros unless the user explicitly asks for source edits.

Workflow

1. Parse $ARGUMENTS and select the active module.
2. Read only the reference file needed for that module.
3. Run the module script with uv run python ....
4. Return Typst-ready comments and next actions.
5. For bibliography requests, decide BibTeX vs Hayagriva first, then run bibliography.

Safety Boundaries

• Never invent citations, labels, or experimental claims.
• Never rewrite Typst references, labels, or math content by default.
• Keep compile diagnostics separate from prose rewrites so the user can validate each step.

Reference Map

• references/TYPST_SYNTAX.md: Typst syntax reminders and pitfalls.
• references/STYLE_GUIDE.md: paper-writing style baseline.
• references/CITATION_VERIFICATION.md: citation verification workflow.
• references/modules/: module-specific Typst commands and choices.
• references/modules/PSEUDOCODE.md: IEEE-like defaults for Typst pseudocode.

Read only the file that matches the active module.

Example Requests

• “Compile this Typst paper and tell me why the export works locally but fails in CI.”
• “Check bibliography, title, and abstract wording in my main.typ submission.”
• “Review this algorithm-figure block for IEEE-like caption, line-number, and comment issues.”
• “Review the methods section for sentence length and logic, but keep Typst labels intact.”

See examples/ for full request-to-command walkthroughs.