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.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill rt-simulated-referee --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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-reject reality + mechanics from `resources/official-source-map.md`; what this venue's referees attack 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 the venue's selectivity. ## Protocol 1. **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
- When to trigger
- Calibrate first (this is what makes it realistic)
- Protocol
- Orchestration
- Hard rules
- Output format
What does the rt-simulated-referee skill do?
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.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill rt-simulated-referee --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From brycewang-stanford/Awesome-Journal-Skills, a repository with 909 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.