Individual skill
paper-write
Write, structure, or revise academic paper sections, keep notation consistent, refine figures and tables, and set up or fix the LaTeX build (TeX distribution, biber vs bibtex, venue templates, compilation). Use when the user says "write the abstract", "structure the methods", "improve this section", "notation consistency", "figure refinement", "paper structure", "setup latex", "biber vs bibtex", "latex compilation error", "install latex packages", "venue template", or "texlive setup".
plugin/skills/paper-write/SKILL.md
Source commit 04877622ff124d92d9ee8377109499c0afc6bf01
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 5, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 456
- Repository last updated
- Nov 1, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 5,087 bytesSKILL.mdcore · 5,087 bytesSKILL.mdcore · 5,087 bytesreferences/latex.mddoc · 3,947 bytes
Read excerpt
# Paper Write: academic paper writing and LaTeX setup
For LaTeX environment setup, biber vs bibtex, venue templates and compilation, follow [references/latex.md](references/latex.md).
## Core Principles
1. **Precision over elegance.** Every claim traces to code, data or a cited source.
2. **Conciseness.** Remove words that don't add information.
## Writing Process
1. **Read first.** Always read the existing section before writing.
2. **Identify the claim.** What is this paragraph trying to say?
3. **Find the evidence.** Where in code/results does this come from?