brycewang-stanford/Auto-Empirical-Research-Skills / skills/35-bahayonghang-academic-writing-skills/skills/typst-paper
typst-paper
VerifiedTypst 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.
references/CITATION_VERIFICATION.md
View on GitHub# Citation Verification Guide
## Table of Contents
- [AI Citation Error Rate Warning](#ai-citation-error-rate-warning)
- [6-Step Verification Workflow](#6-step-verification-workflow)
- [API-Based Verification](#api-based-verification)
- [Exa MCP Integration](#exa-mcp-integration)
- [Citation Rules Quick Reference](#citation-rules-quick-reference)
- [Typst-Specific: Hayagriva Format](#typst-specific-hayagriva-format)
## AI Citation Error Rate Warning
**WARNING: AI-generated citations have a ~40% error rate.** Hallucinated references — papers that don't exist, wrong authors, incorrect years, fabricated DOIs — are a serious form of academic misconduct.
**The Golden Rule**: NEVER generate BibTeX entries from memory. ALWAYS fetch programmatically.
| Action | Correct | Wrong |
|--------|---------|-------|
| Adding a citation | Search API → verify → fetch BibTeX | Write BibTeX from memory |
| Uncertain about a paper | Mark as `[CITATION NEEDED]` | Guess the reference |
| Can't find exact paper | Note: "placeholder — verify" | Invent similar-sounding paper |
## 6-Step Verification Workflow
- [ ] **Step 1**: Search using Exa MCP or Semantic Scholar API
- [ ] **Step 2**: Verify paper exists in 2+ sources (Semantic Scholar + arXiv/CrossRef)
- [ ] **Step 3**: Retrieve BibTeX via DOI (programmatically, not from memory)
- [ ] **Step 4**: Verify the claim you're citing actually appears in the paper
- [ ] **Step 5**: Add verified BibTeX to bibliography
- [ ] **Step 6**: If ANY step fails → mark as placeholder, inform user
## API-Based Verification
### Search with Semantic Scholar
```python
from semanticscholar import SemanticScholar
sch = SemanticScholar()
results = sch.search_paper("attention mechanism transformers", limit=5)
for paper in results:
print(f"{paper.title} - {paper.paperId}")
print(f" DOI: {paper.externalIds.get('DOI', 'N/A')}")
```
### Retrieve BibTeX via DOI
```python
import requests
def doi_to_bibtex(doi: str) -> str:
"""Get verified BibTeX from DOI via CrossRef."""
response = requests.get(
f"https://doi.org/{doi}",
headers={"Accept": "application/x-bibtex"}
)
response.raise_for_status()
return response.text
# Example
bibtex = doi_to_bibtex("10.48550/arXiv.1706.03762")
print(bibtex)
```
### Verify via arXiv
```python
import requests
import xml.etree.ElementTree as ET
def search_arxiv(query: str, max_results: int = 5):
"""Search arXiv for papers."""
url = f"http://export.arxiv.org/api/query?search_query=all:{query}&max_results={max_results}"
response = requests.get(url)
root = ET.fromstring(response.text)
ns = {"atom": "http://www.w3.org/2005/Atom"}
for entry in root.findall("atom:entry", ns):
title = entry.find("atom:title", ns).text.strip()
arxiv_id = entry.find("atom:id", ns).text.strip().split("/")[-1]
print(f"{title} [arXiv:{arxiv_id}]")
```
## Exa MCP Integration
For the best paper search experience, install Exa MCP:
```bash
# Claude Code
claude mcp add exa -- npx -y mcp-remote "https://mcp.exa.ai/mcp"
```
Exa enables searches like:
- "Find papers on RLHF for language models published after 2023"
- "Search for transformer architecture papers by Vaswani"
Then verify results with Semantic Scholar API and fetch BibTeX via DOI.
## Citation Rules Quick Reference
| Situation | Action |
|-----------|--------|
| Found paper, got DOI, fetched BibTeX | Use the citation |
| Found paper, no DOI | Use arXiv BibTeX or manual entry from paper |
| Paper exists but can't fetch BibTeX | Mark placeholder, inform user |
| Uncertain if paper exists | Mark `[CITATION NEEDED]`, inform user |
| "I think there's a paper about X" | **NEVER cite** — search first or mark placeholder |
## Placeholder Format
When you cannot verify a citation:
```typst
// EXPLICIT PLACEHOLDER - requires human verification
@PLACEHOLDER_author2024_verify_this // TODO: Verify this citation exists
```
**Always tell the user**: "I've marked [X] citations as placeholders that need verification."
## Typst-Specific: Hayagriva Format
Typst natively supports Hayagriva YAML format alongside BibTeX:
```yaml
# references.yml (Hayagriva format)
vaswani2017:
type: article
title: "Attention Is All You Need"
author:
- Vaswani, Ashish
- Shazeer, Noam
date: 2017
parent:
type: proceedings
title: "Advances in Neural Information Processing Systems"
serial-number:
doi: "10.48550/arXiv.1706.03762"
```
```typst
// Use in Typst
#bibliography("references.yml", style: "ieee")
```
When verifying citations for Typst, the same 6-step workflow applies. The only difference is the bibliography format (`.yml` vs `.bib`).
## API References
- [Semantic Scholar API](https://api.semanticscholar.org/api-docs/)
- [CrossRef API](https://www.crossref.org/documentation/retrieve-metadata/rest-api/)
- [arXiv API](https://info.arxiv.org/help/api/basics.html)
- [Hayagriva Format](https://github.com/typst/hayagriva/blob/main/docs/file-format.md)
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| 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: 472k | Updated | Claude CodeCodex | Verified | Install |
| 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: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |