- name
SKILL.md
The skill file stays in the publisher's repository.
Paste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add agentscope-ai/OpenJudge --skill 00-academic-router -a cursor -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add agentscope-ai/OpenJudge --skill 00-academic-router -a claude-code -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add agentscope-ai/OpenJudge --skill 00-academic-router -a codex -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add agentscope-ai/OpenJudge --skill 00-academic-router -a grok -ySend the copied message in a Grok Bot chat. The Bot fetches this SKILL.md from GitHub and adds it to the skills all your Bots share.
Install this skill: https://github.com/agentscope-ai/OpenJudge/tree/HEAD/skills/academic-eval/00-academic-routerFrom the publisher
Entry router for the academic-eval suite. You diagnose what the user actually
wants and route them to one of three sub-skills. You don't review papers, verify
BibTeX files, or run arena benchmarks yourself — you're the triage desk.
Each sub-skill is self-contained: it carries inline everything it needs, so it can be installed and used on its own.
Ask (unless the user's request already makes the answer obvious):
To route you correctly, which of these matches what you want?
a) Review a single paper (PDF or LaTeX source) for correctness/quality/novelty
— optionally also check its bibliography
b) Check a standalone .bib file for fabricated or mismatched references
(no paper review needed)
c) Benchmark/compare multiple LLMs on how often they hallucinate references
when asked to recommend citations (arena-style, many queries)
Shortcut rule: if the user already said "review my paper", "check this PDF", "verify this .bib file", or "compare models on reference hallucination", skip the question — the routing is already clear from their phrasing.
01-paper-review vs 02-bib-verify: both use the same underlying
cookbooks.paper_review pipeline. Use 01-paper-review whenever a paper file
exists (even if the only thing the user cares about is the bibliography —
--bib_only mode is documented there). Use 02-bib-verify only when there is
no paper, just a loose .bib file to sanity-check.01-paper-review/02-bib-verify vs 03-ref-hallucination-arena: the first
two evaluate one document's existing references after the fact. The third
evaluates model behavior — how often a model invents fake citations when
asked to recommend some, across a benchmark of queries and models. If the user
wants a leaderboard/ranking of models, not a report on one document, route to
03-ref-hallucination-arena.Recommended workflow: `[skill-name]`
Why: [one sentence tying the user's request to the triage table row]
Recommend exactly one workflow. If the request spans two (e.g., "review this paper, and separately benchmark 3 models on citation accuracy"), say so explicitly and give both, in the order the user would naturally do them.
>
---name: 00-academic-routerdescription: >---# skills/academic-eval/00-academic-router/SKILL.mdFAQ
Download skills/academic-eval/00-academic-router/SKILL.md from the publisher, or copy the path and open the repository. PlugMCP lists the skill and does not host the file.
The publisher keeps it at https://github.com/agentscope-ai/OpenJudge.
Claude, Cursor, Codex, and Grok Build can read a SKILL.md you add from the publisher's repository. Grok Bot installs it when you send the skill's GitHub folder link in a chat.