with one click
paperreview
// Use when the user explicitly wants to upload a final or near-final PDF to paperreview.ai for an external second opinion. Skip this for local paper critique, which should go through `paper-review-pipeline` first.
// Use when the user explicitly wants to upload a final or near-final PDF to paperreview.ai for an external second opinion. Skip this for local paper critique, which should go through `paper-review-pipeline` first.
Use when the user wants multi-agent division of labor for research-led work and the lead should stay on the critical path while 1-2 bounded sidecars handle low-coupling tasks. Do not use this for tiny tasks, fully sequential debugging, or overlapping refactors.
Use when the user asks to review a skill, analyze skill quality, update a skill version, or run a repeatable keep/disable/archive decision loop from real failures instead of abstract best practices.
学术论文写作助手,专门用于 LaTeX 论文编写、BibTeX 管理、格式化、学术写作规范检查。适用于 AI/ML 研究论文、会议投稿(NeurIPS、ICML、ICLR 等)
Use when a task is ambiguous and needs deep multi-role planning with designer, inspiration, and reviewer perspectives before execution. Skip this for ordinary task plans.
落实 CLAUDE.md / AGENTS.md 中的“主动探索”原则,在向用户提问前自动使用 Grep、Read、Bash、WebSearch 等工具获取信息
Use when you want Claude Code CLI as a second opinion for coding tasks such as design tradeoffs, debugging, or diff review, while keeping Codex as the primary implementer.
| name | paperreview |
| description | Use when the user explicitly wants to upload a final or near-final PDF to paperreview.ai for an external second opinion. Skip this for local paper critique, which should go through `paper-review-pipeline` first. |
| version | 0.1.0 |
Submit a paper PDF to paperreview.ai using the same HTTP flow as the website:
This skill uses a small Python script so it can run deterministically without a browser. The public version requires you to provide your own email when submitting.
--submit as an irreversible external side effect (creates a real submission and returns a token).--dry-run first to validate the file and show what would happen.The public version does not ship with a fixed email address.
--email you@example.com when doing a real submissionpython scripts/submit_http.py --pdf "/path/to/paper.pdf" --dry-run
python scripts/submit_http.py --pdf "/path/to/paper.pdf" --venue ICLR --email "you@example.com" --submit
By default, after a successful submit the token is also written next to the PDF as:
<pdf>.paperreview.token.txtTo disable token file writing:
python scripts/submit_http.py --pdf "/path/to/paper.pdf" --venue ICLR --email "you@example.com" --submit --no-token-file
When the review is ready, paperreview.ai can be queried with:
GET /api/review/<token>
202 means still processing200 means ready (JSON review payload)This skill provides a polling script that saves timestamped artifacts next to the PDF:
<pdf>.paperreview.<timestamp>.json (raw JSON, includes _retrieved_at and _token)<pdf>.paperreview.<timestamp>.md (human-readable Markdown)Run (default: 10 minutes, up to 48 hours):
python scripts/watch_review.py --pdf "/path/to/paper.pdf"
One-shot check (useful for debugging / cron):
python scripts/watch_review.py --pdf "/path/to/paper.pdf" --once
0 and prints basic validation info.0 and prints a token: line. Save the token immediately..json + .md next to the PDF and exits 0.