orgstud-review-process
Use when calibrating expectations for the Organization Studies (OS) review cycle — desk-screen odds, the developmental double-anonymized process, decision types, and how to read what reviewers and the handling editor are signalling. Sets expectations and reading strategy; it does not draft the response (see orgstud-rebuttal).
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill orgstud-review-process --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.
# Review Process (orgstud-review-process) ## When to trigger - You want to calibrate desk-reject odds and timeline before or after submitting - A decision letter arrived and you need to read what the editor is *actually* signalling - You are unsure whether an R&R is "major-but-encouraging" or "high-risk reject-with-resubmission" - You are deciding whether to revise for OS or reposition to a sibling journal ## How OS review works (and how it differs) OS runs a **double-anonymized**, **developmental** review handled by a co-editor with (typically) 2–3 reviewers drawn from the relevant conversation. The European, theory-first culture shapes what reviewers do: they engage your **theoretical contribution and your use of social theory** as the primary axis — not just method execution. Reviewers here often *co-develop* the theory across rounds, which is why OS R&Rs can be intellectually demanding and multi-round, but also why a serious R&R is a genuine signal of interest. Expect reviewers who know the canonical works in your conversation intimately. **Desk-screen** is real and theory-driven. The most common desk-rejects are not method failures but **"interesting phenomenon, no theoretical
- When to trigger
- How OS review works (and how it differs)
- Reading the decision
- Reading the reviewers and editor
- Deciding to revise vs. reposition
- Checklist
- Anti-patterns
- Worked vignette: reading an ambiguous letter (illustrative)
- Output format
What does the orgstud-review-process skill do?
Use when calibrating expectations for the Organization Studies (OS) review cycle — desk-screen odds, the developmental double-anonymized process, decision types, and how to read what reviewers and the handling editor are signalling. Sets expectations and reading strategy; it does not draft the response (see orgstud-rebuttal).
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill orgstud-review-process --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.