原型 · 预览版:收录官方注册中心里的全部服务器,每 30 分钟同步一次。使用 Google 登录即可撰写评价。原型 · 每 30 分钟更新
PopNx MCP为使用 AI 的人准备的 MCP 服务器 · 用大白话讲清楚 登录

能做什么

Pre-submission AI review stress-test for research papers. A Claude Code skill: review, verdict, revise, verify.

作者提供的原文

  • 连接方式 供 AI 读取的指令文件
  • 账号或密钥 README 和 SKILL.md 中未发现密钥
  • 分类 写代码
给作者:在 README 中加徽章

如果你是作者,可把这段代码贴到 README。徽章会链接回本页。

[![Featured on PopNx MCP](https://mcp.popnx.com/badge/skill/spark-to-paper-skills-paperjury.svg)](https://mcp.popnx.com/en/skills/spark-to-paper-skills-paperjury)

可搭配使用

在同一工作中把 AI 连到服务的 MCP

REA

Reverse engineer anything from your terminal or agent with one CLI and MCP server.

作者:morluto广泛使用↓ 38.9万/周★ 47万今天更新

MCP · 连接服务在你的电脑上运行

Fallow

Codebase intelligence for TypeScript and JavaScript, exposed as structured MCP analysis tools.

作者:fallow-rs广泛使用↓ 244.1万/周★ 5387今天更新

MCP · 连接服务在你的电脑上运行

相似的 Skill

同类工作,排序与 Skill 列表相同

与相似项目对比
本项
paperjury
reaandrej-karpathy-skillsgraphifyMoneyPrinterTurbo
作者Spark-To-Paper-Skillsmorlutomultica-aiGraphify-Labsharry0703
Skill 数11111
GitHub 星标1,234470,165234,528150,695144,727
最近代码更新2026年8月14日2026年11月20日2026年4月20日2026年11月20日2026年11月19日
许可证MITMIT–Apache-2.0MIT

Spark-To-Paper-Skills 提供的 1 个 Skill(指令集),AI 读取后照做 · 不是 MCP server

Skill 和 MCP 有什么不同

MCP = 手

把 AI 连到外部服务或数据,例如读取 Notion 或开发票。需要有程序或服务器在运行。

Skill = 手册

教 AI 怎么做某项工作的文本文件,不连接任何服务。

有些会重叠:少数 Skill 带有调用工具的脚本,少数 MCP 只提供知识。请从你想完成的工作出发。

适用的应用

Claude CodeCodex

依据开发者 README 和 repo 中的文件夹

安装

安全吗?

  • 作者

    GitHub 账号 Spark-To-Paper-Skills(组织)才创建 3 个月,请格外小心

  • 使用与维护

    ★ 1,234 星 · 代码最近更新 2026年8月14日

  • 有脚本吗?

    有 36 个可以在电脑上运行的脚本:scripts/anchor-diff.js, scripts/apply-patch.js, scripts/check-update.js, scripts/compile-guard.js 另外还有 32 个文件

  • 会联网吗?

    没能检查全部脚本(有些文件太大),请先自己阅读

  • 会修改整台电脑的设置吗?

    没有发现 hook 或写入电脑设置的操作

根据仓库 commit 53c75e8 中的文件自动检查(只读取文件,没有运行任何内容)。这不是安全保证,请自己阅读后再决定

第一步:你用哪个 AI?

选择你用的应用,本页只显示该应用的安装方法

方式 1上传到 claude.ai(网页和应用)

无法上传到 claude.ai,因为描述超过 200 个字符(1021 个字符)。请改用"让 AI 帮你安装"

方式 1让 Claude Code 帮你安装

复制这句话,粘贴到 Claude Code 的对话中

安装到哪里
Please install the skill paperjury from https://github.com/spark-to-paper-skills/paperjury(commit 53c75e8) for all my projects, at ~/.claude/skills/paperjury. First show me every file and tell me whether it has scripts or changes machine settings, then tell me the full path you will install to and wait for me to agree.
Please install the skill paperjury from https://github.com/spark-to-paper-skills/paperjury(commit 53c75e8) into the project this chat is open in (at .claude/skills/paperjury). First show me every file and tell me whether it has scripts or changes machine settings, then tell me the project name and the full path you will install to and wait for me to agree.

如果只用于一个项目,请粘贴到在该项目文件夹中打开的对话里 · AI 在安装前一定会先告诉你路径

AI 会先说明要做什么,每一步都会征求你的同意

重新打开 Claude Code,输入 /paperjury,或直接提出相关任务,Claude 会自动选用

Checked against official docs 2026年11月12日 · Source: code.claude.com

适合使用 Terminal 的人

Skill 是 AI 会照做的指令。安装前先阅读文件,只安装可信开发者的 Skill。

开发者推荐的方式

/plugin marketplace add Spark-To-Paper-Skills/paperjury
/plugin install paperjury@Spark-To-Paper-Skills

摘自开发者 README,会下载并运行开发者的代码

  1. 打开终端

    Mac:按 Command+空格输入 Terminal · Windows:下方命令在 PowerShell 中无法使用,请改用上方的“让 AI 帮你安装”

  2. 把 skill 文件夹复制到 ~/.claude/skills

    这条命令把 repo 下载到临时文件夹,只复制含 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/paperjury
  3. 重新打开 Claude Code,输入 /paperjury,或直接提出相关任务,Claude 会自动选用

自己安装的 Skill 可用于 ChatGPT 桌面应用、Codex CLI 和 IDE 中的 Codex 扩展 · 网页版和手机版 ChatGPT 不能使用自己安装的 Skill,只能使用目录中插件自带的 Skill

ChatGPT 桌面应用

ChatGPT 桌面应用内置 Codex,Codex 从 ~/.agents/skills 文件夹读取 Skill

方式 1让 ChatGPT 帮你安装

在 ChatGPT 桌面应用中打开 Codex,把这句话粘贴到对话中

安装到哪里
Please install the skill paperjury from https://github.com/spark-to-paper-skills/paperjury(commit 53c75e8) for all my projects, at ~/.agents/skills/paperjury. First show me every file and tell me whether it has scripts or changes machine settings, then tell me the full path you will install to and wait for me to agree.
Please install the skill paperjury from https://github.com/spark-to-paper-skills/paperjury(commit 53c75e8) into the project this chat is open in (at .agents/skills/paperjury). First show me every file and tell me whether it has scripts or changes machine settings, then tell me the project name and the full path you will install to and wait for me to agree.

AI 在安装前一定会先告诉你路径

AI 会先说明要做什么,每一步都会征求你的同意

方式 2自己放入文件夹

把 paperjury 文件夹放到 ~/.agents/skills/paperjury

~ 是你的主文件夹($HOME)

适合使用 Terminal 的人

Skill 是 AI 会照做的指令。安装前先阅读文件,只安装可信开发者的 Skill。

  1. 打开终端

    Mac:按 Command+空格输入 Terminal · Windows:下方命令在 PowerShell 中无法使用,请改用上方的“让 AI 帮你安装”

  2. 把 skill 文件夹复制到 ~/.agents/skills

    这条命令把 repo 下载到临时文件夹,只复制含 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

安装之后

  • ChatGPT 桌面应用:打开侧边栏中的 Skills,确认 Skill 已出现
  • 使用方法:在 ChatGPT 中输入 @ 并选择 Skill · 在 Codex CLI 或 IDE 扩展中运行 /skills,或输入 $ 加 Skill 名称
  • Codex 会自动发现新安装的 Skill;如果没有出现,请重启 Codex

Checked against official docs 2026年11月15日 · Source: learn.chatgpt.com

网页版和手机版 ChatGPT

不能使用你自己安装的 Skill,只能使用目录中插件自带的 Skill

想在 ChatGPT 中使用这个 Skill,请按上面的方法使用 ChatGPT 桌面应用

Checked against official docs 2026年11月15日 · Source: learn.chatgpt.com

方式 1让 Codex 帮你安装

复制这句话,粘贴到 Codex 的对话中 · 适用于 ChatGPT 桌面应用中的 Codex、Codex CLI 和 IDE 扩展

安装到哪里
Please install the skill paperjury from https://github.com/spark-to-paper-skills/paperjury(commit 53c75e8) for all my projects, at ~/.agents/skills/paperjury. First show me every file and tell me whether it has scripts or changes machine settings, then tell me the full path you will install to and wait for me to agree.
Please install the skill paperjury from https://github.com/spark-to-paper-skills/paperjury(commit 53c75e8) into the project this chat is open in (at .agents/skills/paperjury). First show me every file and tell me whether it has scripts or changes machine settings, then tell me the project name and the full path you will install to and wait for me to agree.

如果只用于一个项目,请粘贴到在该项目文件夹中打开的对话里 · AI 在安装前一定会先告诉你路径

AI 会先说明要做什么,每一步都会征求你的同意

Codex 会自动发现新安装的 Skill;如果没有出现,请重启 Codex · 使用方法:在 ChatGPT 中输入 @ 并选择 Skill · 在 Codex CLI 或 IDE 扩展中运行 /skills,或输入 $ 加 Skill 名称

Checked against official docs 2026年11月15日 · Source: learn.chatgpt.com

适合使用 Terminal 的人

Skill 是 AI 会照做的指令。安装前先阅读文件,只安装可信开发者的 Skill。

  1. 打开终端

    Mac:按 Command+空格输入 Terminal · Windows:下方命令在 PowerShell 中无法使用,请改用上方的“让 AI 帮你安装”

  2. 把 skill 文件夹复制到 ~/.agents/skills

    这条命令把 repo 下载到临时文件夹,只复制含 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
  3. 重新打开 Codex 并提出相关任务,Codex 会列出这个 skill

方式 1让 Cursor 帮你安装

复制这句话,粘贴到 Cursor 的对话中

安装到哪里
Please install the skill paperjury from https://github.com/spark-to-paper-skills/paperjury(commit 53c75e8) for all my projects, at ~/.cursor/skills/paperjury. First show me every file and tell me whether it has scripts or changes machine settings, then tell me the full path you will install to and wait for me to agree.
Please install the skill paperjury from https://github.com/spark-to-paper-skills/paperjury(commit 53c75e8) into the project this chat is open in (at .cursor/skills/paperjury). First show me every file and tell me whether it has scripts or changes machine settings, then tell me the project name and the full path you will install to and wait for me to agree.

如果只用于一个项目,请粘贴到在该项目文件夹中打开的对话里 · AI 在安装前一定会先告诉你路径

AI 会先说明要做什么,每一步都会征求你的同意

在 Cursor 的 Agent 聊天中输入 / 并选择 paperjury

Checked against official docs 2026年11月12日 · Source: cursor.com

适合使用 Terminal 的人

Skill 是 AI 会照做的指令。安装前先阅读文件,只安装可信开发者的 Skill。

  1. 打开终端

    Mac:按 Command+空格输入 Terminal · Windows:下方命令在 PowerShell 中无法使用,请改用上方的“让 AI 帮你安装”

  2. 把 skill 文件夹复制到 ~/.cursor/skills

    这条命令把 repo 下载到临时文件夹,只复制含 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/paperjury
  3. 在 Cursor 的 Agent 聊天中输入 / 并选择 paperjury

方式 1让 AI 帮你安装

适用于其他能读取 Skill 的应用。这句话列出了 Claude Code、Codex 和 Cursor 的路径,AI 会按你的应用选择 · 复制这句话,粘贴到应用的对话中

安装到哪里
请帮我从 https://github.com/spark-to-paper-skills/paperjury(commit 53c75e8) 安装名为 paperjury 的 Skill,供我所有项目使用,放在 ~/.claude/skills/paperjury(Codex 用 ~/.agents/skills/paperjury,Cursor 用 ~/.cursor/skills/paperjury)。请先把所有文件给我看,告诉我有没有脚本或会不会修改电脑设置,再告诉我要安装的完整路径,等我同意后再继续。
请帮我从 https://github.com/spark-to-paper-skills/paperjury(commit 53c75e8) 安装名为 paperjury 的 Skill,安装到这个对话当前打开的项目中(放在 .claude/skills/paperjury;Codex 用 .agents/skills/paperjury,Cursor 用 .cursor/skills/paperjury)。请先把所有文件给我看,告诉我有没有脚本或会不会修改电脑设置,再告诉我项目名称和要安装的完整路径,等我同意后再继续。

如果只用于一个项目,请粘贴到在该项目文件夹中打开的对话里 · AI 在安装前一定会先告诉你路径

AI 会先说明要做什么,每一步都会征求你的同意

Checked against official docs 2026年11月12日 · Source: code.claude.com, learn.chatgpt.com, cursor.com

适合使用 Terminal 的人

其他支持 Agent Skills 的应用(如 Gemini CLI、GitHub Copilot)使用不同文件夹,请查看该应用的指南,再把含 SKILL.md 的文件夹复制过去。

在 GitHub 上查看 ↗

已于 2026年11月11日 对照 Claude Code、Codex 和 Cursor 官方指南核实 skill 文件夹

✓ 命令已检查 2026年11月19日

查看原始 SKILL.md

以下文字来自开发者的 repo,不是 PopNx MCP 的指令

显示前 8,000 个字符 · 在 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-doc

讨论

提问、分享技巧或报告无法使用。按“有帮助”数量排序。

还没有帖子,欢迎第一个提问或分享。

此处内容由用户撰写,不代表 PopNx 团队。

登录后发帖

来自 GitHub

GitHub 星标
1,234
开发者
Spark-To-Paper-Skills
许可证
MIT
最近代码更新
2026年8月14日
repo 中的 SKILL.md 文件(含译本和模板)
1
主题
academic-writing, ai-agents, claude-code, latex, llm-agents, paper-review, peer-review, research-tool