New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Jue Referee Strategy

by brycewang-stanford in brycewang-stanford/Awesome-Journal-Skills

A skill your agent uses when anticipating the objections a Journal of Urban Economics (JUE) referee will raise before submission, so the manuscript pre-empts them.

MITAuto-check passedResearch & Science

Install Jue Referee Strategy

skills CLI
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jue-referee-strategy -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install brycewang-stanford/Awesome-Journal-Skills jue-referee-strategy --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/Journal-of-Urban-Economics-Skills/skills/jue-referee-strategy .claude/skills/jue-referee-strategy && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
jue-referee-strategy
GitHub stars
1.2k
Token cost
~2k tokens
SKILL.md length
1,016 words
Files
1
Skills in repo
2,387
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses when anticipating the objections a Journal of Urban Economics (JUE) referee will raise before submission, so the manuscript pre-empts them.

  • Works in 5 steps: Map every likely objection to a specific… → Distinguish fatal from cosmetic. A… → Pre-empt in the text, not the appendix… → …
  • Anticipating the objections a Journal of Urban Economics (JUE) referee will raise before submission
  • SKILL.md covers When to trigger, The JUE referee reads for…, Strategy craft and Two referee personas to write…, plus 6 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Jue Referee Strategy is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when anticipating the objections a Journal of Urban Economics (JUE) referee will raise before submission, so the manuscript pre-empts them. Maps the recurring JUE spatial pushbacks to where each is answered in the paper; it does not run the analysis or draft the response letter (jue-rebuttal).

Its SKILL.md is about 2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Research & Science, covering Peer review. The repository describes itself as: Journal-specific Claude Code/Codex skill packs covering mainstream journals — AER, QJE, Nature, Cell, 管理世界, 经济研究 & 200+ more — your fast track to getting published. ｜ 覆盖主流期刊的… The licence is MIT.

When your agent uses it

  • Anticipating the objections a Journal of Urban Economics (JUE) referee will raise before submission
  • So the manuscript pre-empts them

Example prompts

  • “/jue-referee-strategy”

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. Map every likely objection to a specific exhibit or paragraph. If an objection has no home in the paper, you have found the gap to close…
  2. Distinguish fatal from cosmetic. A sorting or SUTVA objection can sink the paper; a "add one more control" objection cannot. Invest…
  3. Pre-empt in the text, not the appendix alone. The first reader is the editor deciding desk-reject; the main text must show the design…
  4. Use the cover letter for what referees cannot infer — a confidential-data exemption, a deliberate scope choice, why a sibling journal is…
  5. Seed the rebuttal. Note, for each anticipated objection, the check you would run if asked, so jue-rebuttal is fast.

What it can do on your machine

Read from SKILL.md and the folder at commit 932eb23. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Jue Referee Strategy loads about 2k tokens when it runs. Until then it costs about 80 tokens; SKILL.md has 1,016 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~80
When it runs · the whole SKILL.md, loaded when a task matches
~2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from brycewang-stanford/Awesome-Journal-Skills at commit 932eb23, republished under its MIT licence (© brycewang-stanford). 1,016 words, ~1,954 tokens.

Download SKILL.mdSave it as .claude/skills/jue-referee-strategy/SKILL.md (or your agent's skills folder).
name
jue-referee-strategy
description
Use when anticipating the objections a Journal of Urban Economics (JUE) referee will raise before submission, so the manuscript pre-empts them. Maps the recurring JUE spatial pushbacks to where each is answered in the paper; it does not run the analysis or draft the response letter (jue-rebuttal).

Referee Strategy (jue-referee-strategy)

When to trigger

  • The paper is close to submission and you want to pre-empt the predictable JUE objections
  • You suspect a referee will say "this is sorting, not the treatment" and the paper does not answer it
  • The control geography or spatial scale could be attacked and no pre-emptive check exists
  • You need to decide which referee concerns to answer in the paper vs. flag for the editor
  • A coauthor is over-confident that the design is bulletproof against spatial critiques

The JUE referee reads for spatial credibility first

A JUE referee is an urban economist who has seen every spatial confound. Before submission, walk the paper through the objections they reliably raise and confirm each is already answered in the text, not deferred to a hoped-for revision.

Predictable JUE referee objectionWhere the paper must already answer it
"This is spatial sorting/selection, not the treatment."jue-identification balance/composition + a placebo pre-trend; the prose says so
"Your control areas are contaminated by spillovers."spillover-ring estimate; controls outside the ring; SUTVA addressed
"Standard errors ignore spatial autocorrelation."Conley/spatial-cluster SEs with a defended cutoff, vs naive
"The result is an artifact of your spatial scale (MAUP)."estimates at multiple scales; scale-stability shown
"The boundary/buffer is arbitrary."radius/donut sensitivity; covariate smoothness at the boundary
"What does this mean in equilibrium once agents re-sort?"jue-theory-model: short-run vs long-run, incidence located
"Why JUE and not RSUE/JEG/JPubE?"jue-literature-positioning: the strand and delta are explicit
"The magnitude is uninterpretable / not policy-relevant."result in % or elasticity; welfare/policy reading threaded in
"Shift-share exogeneity is asserted."Rotemberg weights or BHJ diagnostics reported

Strategy craft

  1. Map every likely objection to a specific exhibit or paragraph. If an objection has no home in the paper, you have found the gap to close before submission, not after.
  2. Distinguish fatal from cosmetic. A sorting or SUTVA objection can sink the paper; a "add one more control" objection cannot. Invest defense effort accordingly.
  3. Pre-empt in the text, not the appendix alone. The first reader is the editor deciding desk-reject; the main text must show the design survives the obvious spatial attacks.
  4. Use the cover letter for what referees cannot infer — a confidential-data exemption, a deliberate scope choice, why a sibling journal is wrong.
  5. Seed the rebuttal. Note, for each anticipated objection, the check you would run if asked, so jue-rebuttal is fast.

Two referee personas to write for

JUE papers are typically read by at least two reviewers with different priors; design the paper to satisfy both:

  • The design referee wants the spatial identification airtight — sorting, SUTVA, spatial SEs, boundary/scale sensitivity. They will not be moved by policy relevance if the design leaks. Your identification and robustness sections are written for this reader.
  • The urban-economics referee wants the mechanism and the magnitude to matter for cities — is the elasticity new, does it discipline theory, does it speak to housing/transport/place-based policy? A perfectly identified but uninteresting result loses this reader. Your framing, theory, and conclusion are written for them.

A paper that pleases only one persona stalls. The introduction must signal both a credible spatial design and a contribution an urban economist cares about.

Checklist

  • Every recurring spatial objection (sorting / spillover / spatial SE / MAUP / boundary) has a home in the text
  • Sorting and SUTVA — the fatal ones — are answered in the main text, not only the appendix
  • The sibling-fit objection is pre-empted in the introduction
  • The magnitude is interpretable and tied to policy/welfare
  • Cover letter flags what referees cannot infer (exemptions, scope, venue choice)
  • For each anticipated objection, a fallback check is ready for the rebuttal
  • Page one satisfies both the design referee and the urban-economics referee
  • Suggested reviewers are spatial-design-fluent; opposed reviewers have a defensible reason
Show full SKILL.md (399 more words)Show less

Anti-patterns

  • Assuming the design is obvious and leaving sorting/spillover objections unanswered
  • Burying the answer to a fatal objection in an appendix the editor may not reach
  • Treating all referee comments as equally important and over-investing in cosmetic ones
  • No cover-letter framing, so the editor must guess scope and venue fit
  • Entering the R&R with no pre-planned checks for the objections you could see coming

Suggesting and excluding reviewers

Editorial Manager often asks for suggested and opposed reviewers; use it strategically. Suggest urban economists who know the spatial design you use and the strand you contribute to — a referee fluent in boundary discontinuities or shift-share will engage your evidence rather than fault its absence. Oppose only with a defensible reason (direct competition, conflict). A thoughtful suggestion list signals to the editor that you know the field's reviewers, which is itself a small fit signal; a list of distant or non-spatial names suggests the paper may not belong at JUE.

Worked vignette (illustrative)

Before submitting the light-rail capitalization paper, the team lists the JUE referee's likely fire: sorting into the corridor, displaced demand contaminating controls, non-spatial SEs, and "why not RSUE." Each gets a pre-emptive home: a pre-period demographic balance table (sorting), a spillover-ring estimate (SUTVA), Conley SEs at a 5km cutoff (spatial dependence), and an intro paragraph staking the agglomeration-vs-transport strand (venue). The remaining anticipated ask — robustness to the ring radius — is pre-run and parked for the rebuttal. The paper now answers its referees before they write.

The desk-reject gate is the first referee

At a high-volume field flagship the editor's triage is the first review, and it is unforgiving. Before submission, read your own first page as the handling editor: in two minutes can they see (1) it is genuinely spatial, (2) the identification is credible against the obvious confounds, (3) the magnitude matters for cities, and (4) why JUE and not a sibling? If any of these is not visible on page one, the paper risks a desk-reject before a referee ever weighs in. The cover letter is your one chance to supply what the first page cannot — frame it for the editor, not the eventual referee.

Output format

text
【Objection → home】sorting: ___ | spillover: ___ | spatial-SE: ___ | MAUP: ___ | boundary: ___ | venue: ___ | magnitude: ___
【Fatal vs cosmetic】fatal objections answered in main text? [Y/N]
【Cover-letter framing】exemptions/scope/venue stated? [Y/N]
【Rebuttal seeds】fallback checks pre-planned for each objection? [Y/N]
【Open gap】objection with no home in the paper: ___
【Next skill】jue-submission

If a likely objection has no home in the paper and you cannot build one before the deadline, that is a signal to delay submission rather than gamble on the referee not noticing — at a field flagship, they will.

© brycewang-stanford, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in Journal-of-Urban-Economics-Skills/skills/jue-referee-strategy of brycewang-stanford/Awesome-Journal-Skills.

Open the folder on GitHubat commit 932eb23

Compare with similar skills

Jue Referee Strategy next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Jue Referee Strategy compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Jue Referee Strategy this skillbrycewang-stanford/Awesome-Journal-Skills1.2k—~2kAutomated safety check: PassMIT
Peer Reviewspacering-net/codeg3.9k17 repos~5.9kAutomated safety check: NotesMIT
Scholar Evaluationspacering-net/codeg3.9k11 repos~3.2kAutomated safety check: PassMIT
Academic Paper Writing PipelineImbad0202/academic-research-skills51k—~16kAutomated safety check: PassCustom licence
Academic Paper ReviewerImbad0202/academic-research-skills51k—~11kAutomated safety check: PassCustom licence
Peer ReviewK-Dense-AI/claude-scientific-writer2.4k2 repos~3.1kAutomated safety check: NotesMIT

Similar skills

  • Peer Review

    spacering-net/codeg

    Structured manuscript/grant review with checklist-based evaluation.

    3.9k GitHub starsUsed in 17 repos~5.9k tokens
    Research & ScienceAuto-check: notes

  • Scholar Evaluation

    spacering-net/codeg

    Systematically evaluate scholarly work using the ScholarEval framework, providing structured assessment across research quality dimensions including problem formulation, methodology, analysis, and…

    3.9k GitHub starsUsed in 11 repos~3.2k tokens
    Research & ScienceAuto-check passed

  • Academic Paper Writing Pipeline

    Imbad0202/academic-research-skills

    Runs a 12-agent pipeline that plans, drafts, cites, reviews and formats academic papers, with modes for revision, rebuttals, abstracts and citation checks.

    51k GitHub stars~16k tokensUpdated today
    Research & ScienceAuto-check passed

  • Academic Paper Reviewer

    Imbad0202/academic-research-skills

    Simulates a journal peer review of a manuscript with a five-seat reviewer panel, an editorial synthesizer and several review modes.

    51k GitHub stars~11k tokensUpdated today
    Research & ScienceAuto-check passed

  • Peer Review

    K-Dense-AI/claude-scientific-writer

    Prepare evidence-bounded, constructive peer-review drafts and structured manuscript assessments.

    2.4k GitHub starsUsed in 2 repos~3.1k tokens
    Research & ScienceAuto-check: notes

  • Academic Research Pipeline

    Imbad0202/academic-research-skills

    Orchestrates a ten-stage academic workflow from research to finished manuscript, including integrity checks, two rounds of peer review and revision.

    51k GitHub stars~15k tokensUpdated today
    Research & ScienceAuto-check passed

More from brycewang-stanford/Awesome-Journal-Skills

All 2,387 skills in this repo

  • Aaag Data Analysis

    brycewang-stanford/Awesome-Journal-Skills

    A skill your agent uses when running and reporting the analysis for an Annals of the American Association of Geographers manuscript — spatial statistics and modeling, remote-sensing accuracy, or…

    1.2k GitHub stars~1.3k tokensUpdated 14 days ago
    Auto-check passed

  • Aaag Literature Positioning

    brycewang-stanford/Awesome-Journal-Skills

    A skill your agent uses when positioning an Annals of the American Association of Geographers manuscript in the literature — engaging geographic scholarship across the relevant area and the…

    1.2k GitHub stars~1.3k tokensUpdated 14 days ago
    Auto-check passed

  • Aaag Rebuttal

    brycewang-stanford/Awesome-Journal-Skills

    A skill your agent uses when responding to an Annals of the American Association of Geographers decision letter (major/minor revision) — building a point-by-point response to the subject editor and…

    1.2k GitHub stars~1.4k tokensUpdated 14 days ago
    Auto-check passed

  • Aaag Research Design

    brycewang-stanford/Awesome-Journal-Skills

    A skill your agent uses when defending the research design of an Annals of the American Association of Geographers manuscript — spatial/quantitative analysis and GIScience, remote-sensing and…

    1.2k GitHub stars~1.4k tokensUpdated 14 days ago
    Auto-check passed

  • Aaag Review Process

    brycewang-stanford/Awesome-Journal-Skills

    A skill your agent uses when you need to understand how the Annals of the American Association of Geographers evaluates a manuscript — double-anonymous review routed through a subject editor by…

    1.2k GitHub stars~1.3k tokensUpdated 14 days ago
    Auto-check passed

  • Aaag Submission

    brycewang-stanford/Awesome-Journal-Skills

    A skill your agent uses when running the final pre-submission preflight for the Annals of the American Association of Geographers via ScholarOne Manuscripts — area/article-type selection…

    1.2k GitHub stars~1.6k tokensUpdated 14 days ago
    Auto-check passed

Categories

Questions about Jue Referee Strategy

What does Jue Referee Strategy do?

A skill your agent uses when anticipating the objections a Journal of Urban Economics (JUE) referee will raise before submission, so the manuscript pre-empts them. Jue Referee Strategy is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when anticipating the objections a Journal of Urban Economics (JUE) referee will raise before submission, so the manuscript pre-empts them.

When should I use Jue Referee Strategy?

Jue Referee Strategy fits situations like: anticipating the objections a Journal of Urban Economics (JUE) referee will raise before submission; so the manuscript pre-empts them.

How do I install Jue Referee Strategy in Claude Code?

Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jue-referee-strategy -a claude-code`. Or copy the skill folder (Journal-of-Urban-Economics-Skills/skills/jue-referee-strategy in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/jue-referee-strategy in your project. Claude Code loads it when a task matches its description.

How do I install Jue Referee Strategy in Codex?

Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jue-referee-strategy -a codex`. Or copy the skill folder (Journal-of-Urban-Economics-Skills/skills/jue-referee-strategy in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/jue-referee-strategy in your project. Codex loads it when a task matches its description.

Can I use Jue Referee Strategy in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jue-referee-strategy -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/jue-referee-strategy, .gemini/skills/jue-referee-strategy, .github/skills/jue-referee-strategy and .opencode/skills/jue-referee-strategy in your project.

What does Jue Referee Strategy need to run?

SKILL.md names no scripts, command-line tools or credentials: Jue Referee Strategy is instructions for the agent only.

Does Jue Referee Strategy access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Jue Referee Strategy safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Jue Referee Strategy use?

Jue Referee Strategy is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Jue Referee Strategy use?

About 2k tokens (SKILL.md is roughly 7.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Jue Referee Strategy?

Skills that share tags, products or a category with Jue Referee Strategy: Peer Review (spacering-net/codeg, 3.9k stars), Scholar Evaluation (spacering-net/codeg, 3.9k stars), Academic Paper Writing Pipeline (Imbad0202/academic-research-skills, 51k stars) and Academic Paper Reviewer (Imbad0202/academic-research-skills, 51k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Jue Referee Strategy?

brycewang-stanford (a GitHub user) maintains it in brycewang-stanford/Awesome-Journal-Skills, which has 1,231 GitHub stars. The repository holds 2,387 skills in this directory. The repository was last updated on September 27, 2026.

Source: brycewang-stanford/Awesome-Journal-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.