What it does
Pre-submission AI review stress-test for research papers. A Claude Code skill: review, verdict, revise, verify.
- Connects Instruction files the AI reads
- Account or key No key found in README or SKILL.md
- Category Coding
For makers: add a badge to your README
If you made this, paste this code into your README. The badge links back to this page.
[](https://mcp.popnx.com/en/skills/spark-to-paper-skills-paperjury)Use together with
MCP servers that connect the AI to services for the same work
Fallow
Codebase intelligence for TypeScript and JavaScript, exposed as structured MCP analysis tools.
Desktop Commander
MCP server for terminal commands, file operations, and process management
Similar Skills
Same kind of work, ordered like the Skills list
| This one paperjury | rea | andrej-karpathy-skills | graphify | MoneyPrinterTurbo | |
|---|---|---|---|---|---|
| Maker | Spark-To-Paper-Skills | morluto | multica-ai | Graphify-Labs | harry0703 |
| Skills | 1 | 1 | 1 | 1 | 1 |
| GitHub stars | 1,234 | 470,165 | 234,528 | 150,695 | 144,727 |
| Last code change | Aug 14, 2026 | Nov 20, 2026 | Apr 20, 2026 | Nov 20, 2026 | Nov 19, 2026 |
| License | MIT | MIT | – | Apache-2.0 | MIT |
1 skills (instruction sets) by Spark-To-Paper-Skills that an AI reads and follows · not an MCP server
How a Skill differs from MCP
MCP = the hands
Connects the AI to an outside service or data, such as reading Notion or creating an invoice. A program or server has to be running.
Skill = the manual
A text file that teaches the AI how to do a task. It connects to nothing.
Some overlap: a few Skills run scripts that call tools, and a few MCP servers only send knowledge. Start from the task you want done.
Works with
Claude CodeCodex
From the maker’s README and the folders in the repo
Install
Is it safe?
- Who made it
GitHub account Spark-To-Paper-Skills (organization) is only 3 months old: take extra care
- Use and upkeep
★ 1,234 stars · code last changed Aug 14, 2026
- Any scripts?
36 scripts that can run on a computer: scripts/anchor-diff.js, scripts/apply-patch.js, scripts/check-update.js, scripts/compile-guard.js and 32 more
- Uses the internet?
Could not check every script (some are too large); read them first
- Changes machine-wide settings?
No hooks or writes to machine settings found
Checked automatically from the repo files at commit 53c75e8 (read only, nothing was run). Not a safety guarantee: read it and decide for yourself
First: which AI do you use?
Pick your app and this page shows only how to install it there
Option 1Upload to claude.ai (web and app)
Uploading to claude.ai would fail: the description is over 200 characters (1021). Use "Let the AI install it" instead
Option 1Let Claude Code install it
Copy this sentence and paste it into a Claude Code chat
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Restart Claude Code, then type /paperjury or ask for a matching task and Claude picks it up
Checked against official docs Nov 12, 2026 · Source: code.claude.com
For Terminal users
A Skill is instructions the AI will follow. Read the files before installing, and install only from makers you trust.
The maker’s recommended way
/plugin marketplace add Spark-To-Paper-Skills/paperjury
/plugin install paperjury@Spark-To-Paper-SkillsCopied from the maker’s README; it downloads and runs the maker’s code
Open Terminal
Mac: press Command+Space and type Terminal · Windows: the command below does not work in PowerShell; use “Let AI install it” above instead
Copy the skill folder to ~/.claude/skills
This downloads the repo to a temporary folder and copies only the folders that contain a SKILL.md
git clone --depth 1 https://github.com/spark-to-paper-skills/paperjury.git /tmp/popnx-skill-spark-to-paper-skills-paperjury-53c75e8 && mkdir -p ~/.claude/skills && cp -R '/tmp/popnx-skill-spark-to-paper-skills-paperjury-53c75e8/.' ~/.claude/skills/paperjuryRestart Claude Code, then type /paperjury or ask for a matching task and Claude picks it up
ChatGPT desktop app
The ChatGPT desktop app has Codex built in, and Codex reads skills from ~/.agents/skills
Option 1Let ChatGPT install it
Open Codex in the ChatGPT desktop app and paste this sentence into the chat
The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Option 2Put the folder there yourself
Put the paperjury folder at ~/.agents/skills/paperjury
~ is your home folder ($HOME)
For Terminal users
A Skill is instructions the AI will follow. Read the files before installing, and install only from makers you trust.
Open Terminal
Mac: press Command+Space and type Terminal · Windows: the command below does not work in PowerShell; use “Let AI install it” above instead
Copy the skill folder to ~/.agents/skills
This downloads the repo to a temporary folder and copies only the folders that contain a SKILL.md
git clone --depth 1 https://github.com/spark-to-paper-skills/paperjury.git /tmp/popnx-skill-spark-to-paper-skills-paperjury-53c75e8 && mkdir -p ~/.agents/skills && cp -R '/tmp/popnx-skill-spark-to-paper-skills-paperjury-53c75e8/.' ~/.agents/skills/paperjury
After installing
- ChatGPT desktop app: open Skills in the sidebar to see that the skill is there
- To use it: in ChatGPT type @ and pick the skill · in Codex CLI or the IDE extension run /skills or type $ and the skill name
- Codex picks up newly installed skills by itself; if one does not show up, restart Codex
Checked against official docs Nov 15, 2026 · Source: learn.chatgpt.com
ChatGPT on the web and mobile
Skills you install yourself do not work here; only skills that come with a plugin from the directory
To use this skill with ChatGPT, use the ChatGPT desktop app as above
Checked against official docs Nov 15, 2026 · Source: learn.chatgpt.com
Option 1Let Codex install it
Copy this sentence and paste it into a Codex chat · Works in Codex inside the ChatGPT desktop app, Codex CLI and the IDE extension
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Codex picks up newly installed skills by itself; if one does not show up, restart Codex · To use it: in ChatGPT type @ and pick the skill · in Codex CLI or the IDE extension run /skills or type $ and the skill name
Checked against official docs Nov 15, 2026 · Source: learn.chatgpt.com
For Terminal users
A Skill is instructions the AI will follow. Read the files before installing, and install only from makers you trust.
Open Terminal
Mac: press Command+Space and type Terminal · Windows: the command below does not work in PowerShell; use “Let AI install it” above instead
Copy the skill folder to ~/.agents/skills
This downloads the repo to a temporary folder and copies only the folders that contain a SKILL.md
git clone --depth 1 https://github.com/spark-to-paper-skills/paperjury.git /tmp/popnx-skill-spark-to-paper-skills-paperjury-53c75e8 && mkdir -p ~/.agents/skills && cp -R '/tmp/popnx-skill-spark-to-paper-skills-paperjury-53c75e8/.' ~/.agents/skills/paperjuryRestart Codex, then ask for a matching task; Codex lists the skill
Option 1Let Cursor install it
Copy this sentence and paste it into a Cursor chat
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
In Cursor’s Agent chat, type / and pick paperjury
Checked against official docs Nov 12, 2026 · Source: cursor.com
For Terminal users
A Skill is instructions the AI will follow. Read the files before installing, and install only from makers you trust.
Open Terminal
Mac: press Command+Space and type Terminal · Windows: the command below does not work in PowerShell; use “Let AI install it” above instead
Copy the skill folder to ~/.cursor/skills
This downloads the repo to a temporary folder and copies only the folders that contain a SKILL.md
git clone --depth 1 https://github.com/spark-to-paper-skills/paperjury.git /tmp/popnx-skill-spark-to-paper-skills-paperjury-53c75e8 && mkdir -p ~/.cursor/skills && cp -R '/tmp/popnx-skill-spark-to-paper-skills-paperjury-53c75e8/.' ~/.cursor/skills/paperjuryIn Cursor’s Agent chat, type / and pick paperjury
Option 1Let the AI install it
For other apps that read skills. The sentence gives the paths for Claude Code, Codex and Cursor so the AI picks the one for your app · Copy this sentence into the app’s chat
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Checked against official docs Nov 12, 2026 · Source: code.claude.com, learn.chatgpt.com, cursor.com
For Terminal users
Other apps that support Agent Skills (such as Gemini CLI or GitHub Copilot) use different folders. Check that app’s guide, then copy the folder with the SKILL.md there.
Skill folders checked against the official Claude Code, Codex and Cursor guides on Nov 11, 2026
✓ Commands checked Nov 19, 2026
View the original SKILL.md
The text below comes from the maker’s repo, not from PopNx MCP
Showing the first 8,000 characters · Open the full file on GitHub
---
name: paperjury
description: Three modes for CS-conference papers (CVPR/ICCV/ECCV vision, ACL/EMNLP/NAACL NLP, ICLR/NeurIPS/ICML/AAAI ML). DIRECT-EDIT mode (common): the user describes a change in Chinese or English and the manuscript (LaTeX or Markdown) is edited directly through a CS-venue writing toolkit with author sign-off (use for 改这段 / 把中文想法写成 latex / polish / de-AI / translate / compress a passage). REVIEW mode (occasional, pre-submission): harden the paper through an adversarial courtroom review engine (N holistic domain reviewers / contestability routing / two-sided trial / three-way verdict / clerk-converged multi-round loop) with consensus-gated, author-signed revisions (use for review / critique / 审稿 / 评审 / mock-review). AUTO mode (unattended, opt-in via /goal): run the review-revise loop toward a verifiable goal, applying safe fixes under a drift-bounded policy and queueing risky ones. Resolves all inputs at runtime, no hardcoded paths. Not a from-scratch drafter (use ml-paper-writing) and not an official-venue rebuttal.
version: 1.2.1
author: Yiran Wang
license: MIT
tags: [Academic Writing, Peer Review, Adversarial Review, CVPR, ICCV, ECCV, ACL, EMNLP, NAACL, ICLR, NeurIPS, ICML, AAAI, Workflow, LaTeX]
---
# PaperJury (CS-conference paper review and editing)
PaperJury edits and hardens any CS-conference paper. It runs in
three modes. In **direct-edit mode** (the common case) the user describes a change
in Chinese or English and the LaTeX is edited directly through a CS-venue writing
toolkit, with author sign-off. In **review mode** (occasional, pre-submission) it
exposes the manuscript to a harsh, multi-perspective courtroom review engine that
adjudicates each issue (N holistic domain reviewers -> contestability routing ->
two-sided trial -> three-way verdict, with a polish track and a clerk-converged
multi-round loop), gates every change behind consensus, and tracks issues in a durable
ledger. In **auto mode** (unattended, opt-in via `/goal`) it runs that same engine
toward a verifiable goal, applying safe fixes under a drift-bounded policy and
queueing the risky ones for one human pass on return. All modes share the same
writing toolkit, hard rules, ledger, and author sign-off (auto via up-front policy
sign-off plus the queue, see hard rule 1).
This skill is **fully generic**. It ships no hardcoded paths, no project files,
and no embedded paper. Everything specific to a given paper (where the
manuscript is, the venue, who signs off, the house style) is resolved at runtime
or supplied by a config the *project* owns. The skill itself is the backbone;
any concrete paper is just an instantiation of it.
Scope: CS conferences only. Three venue families, each with its own style profile:
- **Vision**: CVPR, ICCV, ECCV, WACV
- **NLP**: ACL, EMNLP, NAACL, COLING
- **ML**: ICLR, NeurIPS, ICML, AAAI, COLM
## When to use / when not
Three modes, one skill. Pick by what the user is asking for:
- **Direct-edit mode (the common case).** The user describes a change in Chinese
(or English) and wants the LaTeX edited directly: "把这段改成...", "polish this
paragraph", "把我对 intro 的想法写成 LaTeX", "tighten this". No review panel; go
straight to drafting the patch through the writing toolkit, with author sign-off.
- **Review mode (occasional, pre-submission).** The user wants the paper critiqued
or hardened: review / critique / 审稿 / 评审 / mock-review, or iterating a draft
to clear reviewer-raised issues. This runs the courtroom review engine
(`references/review-engine-v3.md`).
- **Auto mode (unattended).** The user opts in via `/goal` (or config `mode: auto`)
to run the review-revise loop AFK toward a verifiable goal. Establish the spine
up front (the one human step), then the engine applies safe fixes under the
bounded-aggressive policy and queues the rest. The drafter input passes the
significance floor (`node scripts/ledger.js floor`: valid-fixable majors only) and
the ledger view is initialized collapsed (`--display collapse`: minors fold into a
Minor digest, majors stay itemized). See `references/auto-mode.md`.
Never self-detect auto; it is explicit only.
Do NOT use for: writing a paper from scratch (use `ml-paper-writing`), figure or
diagram generation (use `academic-plotting`), or an official-venue rebuttal (this
is a pre-submission self-hardening loop, no score gate).
Soft update reminder: at the start of each PaperJury invocation, before choosing
the mode or editing a manuscript, run `node scripts/check-update.js` from the
skill root unless `PAPERJURY_DISABLE_UPDATE_CHECK=1` is set. If it reports an
available update, show the notice once and continue. If the check is skipped,
silent, or cannot reach GitHub, continue without mentioning it; update checks are
never allowed to block review or editing.
## The three primitives
This paradigm is expressed as **Skill + Workflow + Memory**. Each carries one
concern; together they replace the heavy per-round file-and-flag machinery a
hand-rolled version accumulates.
1. **Skill (this folder) = entry point + methodology.** The protocol, the
reviewer panel, the contestability routing, the writing toolkit, the human gates.
Detail in `references/review-engine-v3.md`, `references/reviewer-personas.md`,
`references/writing-toolkit.md`.
2. **Workflow = fan-out engine.** The semantic, no-human-in-the-middle steps run as
Workflows (parallelism + schema-validated output by construction). The simple
panel is `workflows/review-panel.workflow.js`; the v3 courtroom engine is
`assign-reviewers` -> `reading-check` -> `coverage-auditor` -> `merge` ->
{`trial` (+ escalate) || `polish`} -> `recall-audit` -> `drafter` ->
{`edit-audit` | `meaning-audit`} -> `clerk`. The DETERMINISTIC guards run
orchestrator-side via Bash between workflow calls (the Workflow sandbox has no fs):
`scripts/` holds `decompose`, `extract-docx`, `ledger`, `journal`, `apply-patch`,
`anchor-diff`, `cross-ref`, `spine`, `rekey`, `compile-guard`, `compliance-check`
(plus `doctor`, the install/repo health check: `npm run doctor`). Build note: this harness
delivers a workflow's `args` as a JSON STRING, so every workflow parses it
defensively. Protocol + every orchestrator seam: `references/review-engine-v3.md`.
3. **Memory = durable state + learned conventions.** Two layers:
- **Ledger** (`LEDGER.json` resolved at runtime = the machine source of truth,
plus a rendered `LEDGER.md` view; managed by `scripts/ledger.js`): the live,
mutable issue state across rounds and sessions. Schema + status state machine:
`references/ledger-schema.md`.
- **Claude memory** (the active project's memory): stable conventions worth
recalling next session, e.g. this paper's house style, venue, persona tuning.
## Resolving inputs at runtime (no hardcoded paths)
The skill ships ZERO hardcoded paths or project files. On trigger it resolves
each input by **discovery first, then asking**:
- **manuscript**: detect the main source, then route it through the INTAKE FORMAT
GATE by extension. Four routes, none silent:
- `.tex`: the native LaTeX path. Detect the main source (the `.tex` with
`\documentclass` / `\begin{document}`, or the file the user names). If
several candidates, ask.
- `.md` / `.markdown` / `.txt`: the native text path. The full multi-round
engine runs; compile checks are not applicable (`compile-guard` returns
`compiled:null` plus a markdown sanity lint, an honest UNKNOWN, never a
fake pass); LaTeX-only compliance checks are skipped and reported as
`skipped_checks`.
- `.docx`: if a `.paper-review/` working copy AND a ledger already exist,
REUSE them, never re-extract. If the sha256 of the docx no longer matches
the ledger's `meta.original_sha256`, STOP and ask: continue on the working
copy, or `extract --force` knowingly discarding the applied edits (an
explicit new-intake event). Otherwise run
`node scripts/extract-docDiscussion
Ask, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.
From GitHub
- GitHub stars
- 1,234
- Maker
- Spark-To-Paper-Skills
- License
- MIT
- Last code change
- Aug 14, 2026
- SKILL.md files in the repo (including translated copies and templates)
- 1
- Topics
- academic-writing, ai-agents, claude-code, latex, llm-agents, paper-review, peer-review, research-tool