Traction scoreGitHub stars can be faked, so popularity alone can be misleading. Traction Score looks for broader signs of recent attention, adoption, and active maintenance.
PaperJury runs a CS-conference manuscript through an adversarial courtroom review engine that assigns domain reviewers, routes issues to a trial jury, and gates every edit behind author sign-off. It helps authors, lab teams, and graduate students harden papers for vision, NLP, and ML venues without leaving the agent workflow.
Compatible AgentsThe repository documents support for these agents. The skills may also work with other agents that can load SKILL.md files, but they may need some setup or small changes.
After installation, run this terminal command from the installed skill folder to verify repository integrity, required tools, and manuscript detection.
Installs: PaperJury skill scoped to one project · Claude Code
Before you start
node installed; it is required for deterministic checks
Run from: <project>
Replace <project> with the paper project’s root directory and place the PaperJury repository under <project>/.claude/skills/. This is a manual placement instruction; the source does not provide a project-scoped command.
From the installed skill folder, run this terminal command to verify repository integrity, required tools, and manuscript detection.
Paper project path to substitute for <paper-project>
A manuscript in the project
The target CS-conference venue or venue family if it is not otherwise available
Use the paperjury skill to review the manuscript in <paper-project>, especially its experiments and claims. Treat <paper-project> as the path to my paper project. Report the issues and proposed revisions, and require my confirmation before applying any patch.
A file location, line range, or pasted paragraph to substitute for <target-passage>
Any wording or length constraint that must be preserved
Use the paperjury skill in direct-edit mode to tighten the introduction paragraph at <target-passage> without changing its claim. Treat <target-passage> as a placeholder for the file and paragraph, line range, or pasted passage I provide. Draft the bounded change and wait for my sign-off before applying it.
Paper project path to substitute for <paper-project>
Main manuscript path to substitute for <main-manuscript>
node installed
Optional LaTeX toolchain for real compilation and layout checks
Use the paperjury skill’s submission-readiness checker on <main-manuscript> in <paper-project>. Treat both values as path placeholders. Give me the deterministic desk-reject screening and compile findings; if no LaTeX toolchain is available, clearly report the supported structural-lint fallback instead.
Claude
Codex