paperjury

Reviews and edits CS-conference LaTeX papers through an adversarial multi-reviewer adjudication loop.

220|19|Updated Jun 4, 2026
One-click install
npx skills add https://github.com/Spark-To-Paper-Skills/paperjury-codex --skill paperjury-spark-to-paper-skills
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: paperjury
Source: https://github.com/Spark-To-Paper-Skills/paperjury-codex
Command: npx skills add https://github.com/Spark-To-Paper-Skills/paperjury-codex --skill paperjury-spark-to-paper-skills

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Authors submitting to CS conferences often discover reviewer-catchable weaknesses, overclaimed statements, and formatting risks only after submission. This Skill runs a pre-submission adversarial review that finds issues, adjudicates whether each one is valid, and applies only safe minimal LaTeX patches with author sign-off. ## Core Features & Use Cases - Courtroom review engine: N domain reviewers read the whole paper, contested issues go to a two-sided jury trial, and each verdict lands as fixable, author-required, or invalid, tracked in a durable JSON ledger. - Guarded LaTeX editing: Direct-edit mode drafts minimal patches (polish, de-AI, translate Chinese notes, compress, captions) with deterministic guards for anchors, cross-references, patching, and real LaTeX compilation. - Submission-readiness checks: Deterministic desk-reject screening plus compile-driven layout checks, degrading honestly when no LaTeX toolchain exists. - Use Case: Before submitting to CVPR or ACL, ask it to review your draft; it returns an issue ledger with evidence and verdicts, applies safe fixes you approve, and queues anything needing new experiments for your judgment. ## Quick Start Ask the assistant to review your paper before submission, for example by saying: review my LaTeX paper and flag weak claims, missing evidence, and formatting risks.

Frequently Asked Questions about paperjury

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I get an AI review of my LaTeX paper before submission?

Ask for a review or mock-review of your manuscript and the skill runs a multi-reviewer engine that reads the whole paper, quotes evidence for each weakness, and adjudicates every issue as fixable, author-required, or invalid. Results are tracked in a durable ledger you can inspect.

How does the adversarial review engine decide which issues to fix?

Substantive major issues go to a two-sided trial with isolated jurors and a deterministic majority verdict. Only valid-fixable issues with a concrete close criterion get minimal patches; missing experiments or evidence are routed back to the author.

Does it require a LaTeX toolchain installed locally?

No, a LaTeX toolchain is optional. When latexmk or pdflatex is available it runs a real compile and reports errors, undefined references, and page counts; otherwise it degrades to structural lint and explicitly reports what it could not verify.

Can it edit my paper automatically without my approval?

No, every edit requires explicit author sign-off. The unattended auto mode works only through up-front authorization of a frozen claim spine and a bounded policy, and anything outside that envelope is queued for human review.

What are the limitations of AI pre-submission paper review?

It cannot replace peer review or the author's scientific judgment, and it never invents experiments or unsupported claims. It is scoped to CS conference papers and does not write papers from scratch, generate figures, or handle official rebuttals.