跳到主要内容
知仓学习社ZHICANG

rje-workflow

Use when routing a RAND Journal of Economics (RJE) manuscript to the right rje-* skill across the industrial-organization lifecycle — from IO topic …

不碰外部(只输出文字)无严重或高危命中brycewang-stanford/Awesome-Journal-Skills

它会碰到什么

扫了多少1 个文本文件,6 KB
它会碰到什么不碰外部(只输出文字)
命中总数0 处
命中统计严重 0 · 高 0 · 中 0 · 低 0

这一栏是扫描器报的事实,不是结论。命中多不等于有毒(安全工具、规则库、示例脚本本来就会包含危险写法),命中少也不等于干净。它和你手上的凭据、文件、网络有什么关系,需要你自己看。

技能内容

RJE Workflow Router (rje-workflow)

When to trigger

  • You are starting or mid-way through an RJE manuscript and want to know the next step
  • You are unsure whether your applied-micro / IO project is an RJE fit at all
  • You need to map a reviewer request back to the right specialist skill

What RJE is (so the route is correct)

The RAND Journal of Economics (RJE), formerly the Bell Journal of Economics, is owned and sponsored by the RAND Corporation (Santa Monica) and published in partnership with Wiley. Its scope is deliberately narrow: applied microeconomics centered on industrial organization — regulated industries, antitrust/competition, regulation, market structure, firm strategy, and the economic analysis of organizations. It is widely regarded as the field's flagship IO journal. Both theoretical and empirical work is welcomed. This is not a general-interest or macro outlet, so route accordingly.

The route

rje-topic-selection          (Is this an IO question RJE wants?)
        ▼
rje-contribution-framing     (What is the one-sentence contribution?)
        ▼
rje-literature-positioning   (Stake it against the IO frontier)
        ▼
rje-identification-strategy  (Structural or reduced-form design)
        ▼
rje-data-analysis            (Estimate, diagnose, robustness)
        ▼
rje-tables-figures           (Exhibits under the RJE Style Guide)
        ▼
rje-writing-style            (House usage + author-date polish)
        ▼
rje-replication-and-data-policy (Package + supporting-info handling)
        ▼
rje-review-process           (Understand the editor screen + referees)
        ▼
rje-submission               (Page caps, abstract, fee, portal preflight)
        ▼
rje-rebuttal                 (Respond to the two referees + Editor)

How to pick

  • No clear IO angle yetrje-topic-selection
  • Have results, fuzzy on the "so what"rje-contribution-framing
  • Design is the bottleneckrje-identification-strategy
  • About to press submitrje-submission (page caps are hard)
  • Got an R&R from the handling Editorrje-rebuttal

Symptom-to-skill dispatch table

When a task or reviewer remark arrives mid-project, match the symptom to the specialist skill rather than guessing the stage.

| Symptom or request | Route to | Why |

|---|---|---|

| "Is this even an IO question for RJE?" | rje-topic-selection | Scope is deliberately narrow; screen fit first |

| "The intro reads like a methods exercise" | rje-contribution-framing | Make the IO advance legible by page 1 |

| "Referee says we miss the frontier" | rje-literature-positioning | Stake against the right IO strand |

| "Price is treated as exogenous" | rje-identification-strategy | Endogeneity is the central structural threat |

| "Counterfactual looks fragile" | rje-data-analysis | Bound it; validate against an episode |

| "Tables blow the 40-page cap" | rje-tables-figures | Triage exhibits to the appendix |

| "Subsections are numbered 2.1, 2.2" | rje-writing-style | RJE leaves subsections unnumbered |

| "What do we deposit for replication?" | rje-replication-and-data-policy | RJE hosts nothing; supporting info discouraged |

| "What happens after submit?" | rje-review-process | Editor screen then two anonymous referees |

| "Final checks before upload" | rje-submission | Page caps, abstract, fee, portal |

| "We got an R&R" | rje-rebuttal | Editor's letter is binding; respect caps |

Worked routing vignette

Suppose a collaborator says: "Our hospital-merger article got an R&R; one referee disputes the bargaining model's identification and the Editor wants the welfare number bounded — and we are over the page cap." Route in order:

  • Editor's binding ask (bound the welfare number) and identification disputerje-rebuttal to plan the response, drawing on rje-identification-strategy for the bargaining-identification defense and rje-data-analysis for the bounded counterfactual.
  • Over the page caprje-tables-figures and rje-submission to triage exhibits into the appendix before resubmission.
  • House-style drift in the revisionrje-writing-style for a final pass.

The router's job is to sequence these, not to perform any one of them.

Lifecycle calibration anchors

  • The lifecycle is roughly linear early (topic → framing → positioning → design → analysis → exhibits → style) but loops once an R&R arrives: rebuttal pulls back into identification, analysis, and exhibits before resubmission.
  • The two hard external gates are the editor screen (clear it with a legible IO hook and page-cap discipline) and the two-referee read (clear it with credible identification and bounded counterfactuals).
  • Treat these stages as a default ordering, not a rigid pipeline; an applied-theory IO article may compress the empirical skills and lean on framing, positioning, and writing-style. Confirm any process specifics against the journal's current author guidelines.

Output format

【Stage】topic / framing / design / analysis / exhibits / style / package / submission / rebuttal
【RJE fit risk】on-scope IO? [Y/N/uncertain]
【Next skill】rje-...
【Why】one line

想直接用这个技能?

本站把开放许可(MIT / Apache 等)的技能按仓库打包整理到网盘,点一下转存到你自己的网盘,不用一个个从 GitHub 拉。许可未声明的技能只给原始仓库链接,不打包。