How do I install the Rt Simulated Referee skill?

Run npx skillmds@latest add brycewang-stanford/rt-simulated-referee in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Rt Simulated Referee safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Rt Simulated Referee?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Rt Simulated Referee free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Rt Simulated Referee?

brycewang-stanford (@brycewang-stanford) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Rt Simulated Referee by brycewang-stanford

Name: Rt Simulated Referee
Rating: 4.5 (4 reviews)
Author: brycewang-stanford

Rt Simulated Referee

Use to rehearse peer review before submitting — a calibrated Associate Editor desk-screen plus 2–3 distinct-lens referees for the target venue, adversarially verified and synthesized into a referee report, a decision band, and a prioritized, skill-mapped fix list. A rehearsal that predicts the attack surface; it does not replace real review.

brycewang-stanford Updated Sep 8, 2026 1k repo stars

File contents

Simulated Referee (rt-simulated-referee)

Run the substantive gauntlet before a real referee does. Full protocol + a worked example: shared-resources/submission-readiness/simulated-referee.md.

When to trigger

After rt-submission-readiness clears the mechanical bar.
When the author wants to know the decisive objection before submitting.

Calibrate first (this is what makes it realistic)

Pull the venue's bar from the target pack, not generic intuition: acceptance/desk-reject reality + mechanics from resources/official-source-map.md; what this venue's referees attack from *-referee-strategy + the shared reviewer-objection-checklist; the fit/identification/robustness bar from the pack's skills. Set strictness to the venue's selectivity.

Protocol

AE desk-screen — fit, general interest, fatal flaws → desk-reject risk; stop if a clear desk reject.
Independent referees (distinct lenses: identification skeptic · contribution/fit · robustness/reproducibility) each write a structured report.
Adversarial verification — every major concern must be real + specific + addressable or be downgraded.
AE synthesis — one decision band (reject / major / minor / lean-accept) + the 1–3 decisive issues.
Skill-mapped fix list — each decisive issue → the pack skill (and its execution bridge) that fixes it.

Orchestration

Spawn one subagent per role with the same manuscript + the calibrated venue bar; collect independent reports; a final AE-synthesis agent. Distinct lenses + independence catch more than a single read.

Hard rules

Calibrate from the pack + source-map, never generic.
Verify before reporting (real / specific / addressable).
Map every decisive issue to a skill + execution bridge.
It's a rehearsal — output a decision band and the decisive issues, never a fake accept probability.

Output format

【Venue】… (calibrated)
【Desk-screen】send out / desk reject — reason; risk low/med/high
【Decision band】reject / major / minor / lean-accept
【Decisive issues (1–3)】each with owning pack skill + concrete fix
【Author action plan】ordered; tie each to a skill + tool

Next: address the decisive issues, then rt-response-to-referees for a real R&R.

---name: rt-simulated-refereedescription: Use to rehearse peer review before submitting — a calibrated Associate Editor desk-screen plus 2–3 distinct-lens referees for the target venue, adversarially verified and synthesized into a referee report, a decision band, and a prioritized, skill-mapped fix list. A rehearsal that predicts the attack surface; it does not replace real review.---# Simulated Referee (rt-simulated-referee)Run the substantive gauntlet before a real referee does. Full protocol + a worked example:[`shared-resources/submission-readiness/simulated-referee.md`](../../../shared-resources/submission-readiness/simulated-referee.md).## When to trigger- After `rt-submission-readiness` clears the mechanical bar.- When the author wants to know the decisive objection before submitting.## Calibrate first (this is what makes it realistic)Pull the venue's bar from the target pack, not generic intuition: acceptance/desk-rejectreality + mechanics from `resources/official-source-map.md`; what this venue's refereesattack from `*-referee-strategy` + the shared[`reviewer-objection-checklist`](../../../shared-resources/empirical-methods/reviewer-objection-checklist.md);the fit/identification/robustness bar from the pack's skills. Set strictness to thevenue's selectivity.## Protocol1. **AE desk-screen** — fit, general interest, fatal flaws → desk-reject risk; stop if a clear desk reject.2. **Independent referees** (distinct lenses: identification skeptic · contribution/fit · robustness/reproducibility) each write a structured report.3. **Adversarial verification** — every major concern must be **real + specific + addressable** or be downgraded.4. **AE synthesis** — one decision band (reject / major / minor / lean-accept) + the 1–3 decisive issues.5. **Skill-mapped fix list** — each decisive issue → the pack skill (and its execution bridge) that fixes it.## OrchestrationSpawn one subagent per role with the same manuscript + the calibrated venue bar; collectindependent reports; a final AE-synthesis agent. Distinct lenses + independence catch morethan a single read.## Hard rules1. **Calibrate from the pack + source-map**, never generic.2. **Verify before reporting** (real / specific / addressable).3. **Map every decisive issue to a skill + execution bridge.**4. **It's a rehearsal** — output a decision *band* and the decisive issues, never a fake accept probability.## Output format```【Venue】… (calibrated)【Desk-screen】send out / desk reject — reason; risk low/med/high【Decision band】reject / major / minor / lean-accept【Decisive issues (1–3)】each with owning pack skill + concrete fix【Author action plan】ordered; tie each to a skill + tool```Next: address the decisive issues, then `rt-response-to-referees` for a real R&R.

Frequently asked questions