Agent skill

jru-referee-strategy

Use when anticipating likely referee objections for a Journal of Risk and Uncertainty (JRU) manuscript before submission. Wargames the report a risk/uncertainty specialist would write; it does not invent evidence or citations.

brycew6m4,252★ · +31/wk · 3 repos on radarProfile →
claude-codeMIT
Install
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jru-referee-strategy --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 7 KB
Bundled scripts: none
Path: Journal-of-Risk-and-Uncertainty-Skills/skills/jru-referee-strategy/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 984 · +31 this week
Language: Stata
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Referee Strategy (jru-referee-strategy) ## When to trigger - The draft is nearly done and you want to pre-empt the objections a JRU referee will raise - You are choosing what to put in the main text vs. the appendix to disarm predictable pushback - The paper makes a strong EU-vs-alternatives claim and you expect a referee from the camp it challenges - You suspect the elicitation or the VSL identification has a soft spot a specialist will find ## Who reviews for JRU, and what they hunt for JRU's reviewer pool is specialized — decision theorists, experimental risk researchers, and VSL/insurance empiricists, under a single-blind model typical of Springer econ journals (待核实). Each subculture has a signature objection. Wargame the report by reading the paper as each of these referees would. | Referee type | Their reflex objection | Pre-empt by | |--------------|------------------------|-------------| | Decision theorist | "The representation has no behavioral content / the reference point is fit, not fixed" | Stating one prediction the model forbids; fixing the reference point a priori (`jru-theory-model`) | | Experimentalist | "The elicitation is not incentive-compatible / it confoun

What's inside
Steps it walks through
  1. When to trigger
  2. Who reviews for JRU, and what they hunt for
  3. How to wargame
  4. The questions a JRU report almost always asks
  5. Worked second pass: choosing what to promote
  6. Checklist
  7. Suggesting and excluding reviewers
  8. Anti-patterns
  9. Worked vignette (illustrative)
  10. Output format
More from Awesome-Journal-Skills
All skills →
About this skill
What does the jru-referee-strategy skill do?

Use when anticipating likely referee objections for a Journal of Risk and Uncertainty (JRU) manuscript before submission. Wargames the report a risk/uncertainty specialist would write; it does not invent evidence or citations.

How do I install it?

Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jru-referee-strategy --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 984 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.

Keep going