Paper Polish

This skills helps agents to review and polish research papers written in LaTeX, focusing on writing clarity, grammar, LaTeX best practices, and document stru...

Security Scan

The skill's requirements and instructions are consistent with its stated purpose of reviewing and polishing LaTeX research papers; it makes no unexpected requests for credentials, installs, or system-level access.

Purpose & Capability

Name, description, and the SKILL.md all focus on LaTeX and writing/structure guidance. The skill does not request unrelated binaries, environment variables, or credentials — nothing appears extraneous to a paper-polishing task.

Instruction Scope

SKILL.md is a prose guide for reviewing LaTeX papers and references typical project files/paths (main.tex, src/, tables/, figures/). The instructions themselves do not instruct the agent to access environment variables or external endpoints. Note: because it mentions project file layout, an agent using this skill may read the user's LaTeX files to apply the guidance — that is expected for this purpose but you should be aware the agent will need access to those files to operate.

Install Mechanism

No install specification or code files are present (instruction-only), so nothing will be downloaded or written to disk by the skill itself.

Credentials

The skill declares no required environment variables, credentials, or config paths. There is no disproportionate credential request relative to the described functionality.

Persistence & Privilege

The skill does not request always-on presence and uses default invocation settings. It does not attempt to modify other skills or system settings.

Assessment

This skill is instruction-only and coherent for polishing LaTeX papers. Before using it, confirm that any agent invoking the skill is permitted to read the LaTeX project files (main.tex, src/, etc.), and avoid sending sensitive or unreleased content if you don't want it processed. Because the skill has no install or credential requirements, the main risk is that the agent (not the skill itself) will access your documents — review agent/file permissions and external network access policies before proceeding.

Polishing and reviewing research papers in LaTeX

On writing

Contents

• Your paper should be easily comprehensible by its reviewers. They are far less familiar with your work than you. They may not be an expert on the topic and may not be able to afford much time on your paper.
• The introduction should convey curiosity or excitement (new problem, new solution, improved solution, impressive results, or high impact), the design novelty, substantiality, and correctness, and the evaluation relevancy and comprehensiveness.
• Conciseness: Remove every word that contributes no meaning, such as kind of.
• Use proper tenses:
  • 1
  • 2
  • 3

Grammar

• Section titles should have consistent capitalization.

  • Title Case: Capitalize the first and last words and all major words in between.
    • Good: Introduction to Fuzzing with LLMs
  • Sentence case: Capitalize only the first word and proper nouns.
    • Good: Introduction to fuzzing with LLMs
  • Choose one style and be consistent throughout the paper.

• Avoid passive voice unless strongly justifiable. Passive voice is ambiguous because it has no subject unless followed by "by...".

  • Bad: LLM was applied to fuzzing. (Who applied it? The authors or someone else?)
  • Good: We applied LLM to fuzzing.

• Avoid nominalization.

  • Bad: He made a proposal to use Rust.
  • Good: He proposed to use Rust.

• Avoid "There is/are".

  • Bad: There are many developers of Rust.
  • Good: Many developers use Rust.
  • Good: Rust has many developers.

• "Which" vs "that": Use "which" in a nonrestrictive clause and "that" in a restrictive clause. More...

  • Wrong: Rust that is safe is popular. (This is wrong because there is only one Rust.)
  • Right: Rust, which is safe, is popular.

• Distinguish coordinating conjunction vs conjunctive adverbs.

  • Wrong: C is dangerous, Rust is safe. (Cannot join two sentences by a comma)
  • Right: C is dangerous, but Rust is safe.
  • Wrong: C is dangerous, however Rust is safe.
  • Right: C is dangerous; however, Rust is safe.

• "Fewer" modifies countable nouns whereas "less" uncountable nouns.

  • Wrong: ten items or less
  • Right: ten items or fewer
  • Wrong: fewer feedback
  • Right: less feedback

• Use articles (a, an, the) properly.

  • A singular countable noun must be preceded by an article.

    • Wrong: I wrote Rust program.
    • Right: I wrote a Rust program.
    • Right: I wrote Rust programs.

  • The must have a reference that is unique either by fact or in the context.

    • Right: the first Rust programmer (unique by fact)
    • Right: Our team has a Rust and a C++ programmer. The Rust programmer produces the fastest, most robust code. (unique in the context)
    • Wrong: Our team has two Rust and two C++ programmers. The Rust programmer is more productive than the C++ programmer.

• Distinguish between compare with and compare to

  • Right: Rust is safer compared with C.
  • Right: Some people compare Rust to a panacea for memory safety problems.

On LaTeX

• Use modern implementations of LaTeX to take advantage of Unicode and other useful features.

  • Use LuaLaTeX instead of LaTeX or pdfLaTeX
  • Use BibLaTeX for acmart and ieeetrans templates instead of BibTex

• Use correct typefaces. Particularly, italics should be used for variables but not for descriptive terms. More...

  • Wrong: $t_{max}$
  • Right: $t_\text{max}$

• Do not manually add separators in large numbers. \usepackage{siunitx}. Then, wrap large numbers in \num{}.

  • Bad: 12,345
  • Good: \num{12345}

• Do not manually type reference names, such as Table, Figure, Theorem. Instead, \usepackage{hyperref}, and then \autoref{fig:xxx}, \autoref{sec:xxx}, \autoref{table:xxx}.

  • Not recommended: In Figure~\ref{fig:overview}
  • Good: In \autoref{fig:overview}

Structure

• main.tex is the entry root of the LaTeX project, containing the usepackage commands and the document structure.
• src/ contains all the sections.
• tables/ contains all the tables.
• figures/ or fig/ contains the figures. Figures are PDF files or .tex files. .tex in figures are algorithms.
• code/ contains code listings used in the text.