Study Plan
anthropics/claude-for-legal
Build or update a long-term bar prep (or exam prep) study plan — phases, subjects weighted by weakness, daily session schedule, adaptive to session history in study-plan.yaml.
A skill your agent uses when calibrating expectations for the Organization Studies (OS) review cycle — desk-screen odds, the developmental double-anonymized process, decision types, and how to read…
MITAuto-check passed
Install Orgstud Review Process
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill orgstud-review-process -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills orgstud-review-process --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/Organization-Studies-Skills/skills/orgstud-review-process .claude/skills/orgstud-review-process && rm -rf skills-srcUse ~/.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/
Install the "orgstud-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Organization-Studies-Skills/skills/orgstud-review-process into .claude/skills/orgstud-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "orgstud-review-process", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Organization-Studies-Skills/skills/orgstud-review-processType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill orgstud-review-process -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills orgstud-review-process --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/Organization-Studies-Skills/skills/orgstud-review-process .agents/skills/orgstud-review-process && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "orgstud-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Organization-Studies-Skills/skills/orgstud-review-process into .agents/skills/orgstud-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "orgstud-review-process", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill orgstud-review-process -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills orgstud-review-process --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/Organization-Studies-Skills/skills/orgstud-review-process .cursor/skills/orgstud-review-process && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "orgstud-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Organization-Studies-Skills/skills/orgstud-review-process into .cursor/skills/orgstud-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "orgstud-review-process", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/brycewang-stanford/Awesome-Journal-Skills.git --path Organization-Studies-Skills/skills/orgstud-review-process--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill orgstud-review-process -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills orgstud-review-process --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/Organization-Studies-Skills/skills/orgstud-review-process .gemini/skills/orgstud-review-process && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "orgstud-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Organization-Studies-Skills/skills/orgstud-review-process into .gemini/skills/orgstud-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "orgstud-review-process", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills orgstud-review-processInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill orgstud-review-process -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/Organization-Studies-Skills/skills/orgstud-review-process .github/skills/orgstud-review-process && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "orgstud-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Organization-Studies-Skills/skills/orgstud-review-process into .github/skills/orgstud-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "orgstud-review-process", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill orgstud-review-process -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills orgstud-review-process --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/Organization-Studies-Skills/skills/orgstud-review-process .opencode/skills/orgstud-review-process && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "orgstud-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Organization-Studies-Skills/skills/orgstud-review-process into .opencode/skills/orgstud-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "orgstud-review-process", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
orgstud-review-process- GitHub stars
- 1.2k
- Token cost
- ~1.5k tokens
- SKILL.md length
- 690 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when calibrating expectations for the Organization Studies (OS) review cycle — desk-screen odds, the developmental double-anonymized process, decision types, and how to read…
- Calibrating expectations for the Organization Studies (OS) review cycle — desk-screen odds
- SKILL.md covers When to trigger, How OS review works (and how…, Reading the decision and Reading the reviewers and editor, plus 5 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- The developmental double-anonymized process
What it does
Orgstud Review Process is an agent skill from brycewang-stanford/Awesome-Journal-Skills. 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).
Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
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
- Calibrating expectations for the Organization Studies (OS) review cycle — desk-screen odds
- The developmental double-anonymized process
- How to read what reviewers and the handling editor are signalling
Example prompts
- “/orgstud-review-process”
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
Orgstud Review Process loads about 1.5k tokens when it runs. Until then it costs about 88 tokens; SKILL.md has 690 words of instructions outside code blocks.
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). 690 words, ~1,478 tokens.
Download SKILL.mdSave it as
.claude/skills/orgstud-review-process/SKILL.md (or your agent's skills folder).- name
- orgstud-review-process
- description
- 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).
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 contribution," wrong-fit ("belongs at a sibling journal"), or superficial engagement with the literature it claims to advance. A clean dataset will not save a paper with a thin theoretical move.
Reading the decision
| Outcome | What it usually means | Your move |
|---|---|---|
| Desk reject | Fit/contribution problem caught pre-review | Re-diagnose with orgstud-topic-selection / orgstud-contribution-framing; consider sibling fit |
| Reject (post-review) | Reviewers see a fatal theoretical or evidentiary gap | Read for whether the core idea survives; usually reposition, don't resubmit |
| Reject & resubmit / high-risk R&R | Promising but currently not a contribution | Treat as a near-rewrite of the theory; only proceed if you can make the move land |
| Major revision | The contribution is real; theory/evidence need substantial development | The expected good outcome; plan a multi-issue revision (orgstud-rebuttal) |
| Minor revision | Rare on first round; contribution accepted, polishing needed | Address precisely; do not reopen settled points |
Reading the reviewers and editor
- The editor's letter is the binding instruction. When reviewers conflict, the co-editor usually signals which threads are essential — prioritize those.
- Theory comments outrank cosmetic ones. A reviewer asking you to "engage [conversation] more deeply" or "clarify the mechanism" is naming the contribution bar; treat it as central, not as a citation chore.
- Distinguish "develop this" from "drop this." OS reviewers frequently push you to develop an underdeveloped idea — that is an invitation, not a rejection of it.
- Reflexivity / positionality requests are substantive at OS, not box-ticking.
Show full SKILL.md (291 more words)Show less
Deciding to revise vs. reposition
- Revise for OS if the contribution is real and the reviewers' essential asks are achievable without breaking the paper.
- Reposition if the core asks would turn it into a different paper, or if the fit critique (too descriptive, wrong conversation, sibling-shaped) is fundamental —
orgstud-workflowcan route the repositioning.
Checklist
- You have separated essential asks (editor-flagged, theory-level) from optional ones
- You can state, in one line, whether the contribution survives the reviews
- Theory/mechanism/literature comments are treated as central, not cosmetic
- The outcome type is correctly read (R&R encouragement vs. high-risk resubmission)
- Revise-vs-reposition decision is made deliberately, not by default
- Timeline expectations are realistic (multi-round developmental review)
Anti-patterns
- Reading a "reject & resubmit" as a minor revision (or vice versa)
- Treating deep-engagement/theory requests as optional polish
- Cherry-picking easy reviewer points while dodging the editor's essential threads
- Resubmitting a desk-rejected paper to a sibling without fixing the contribution problem
- Ignoring reflexivity/positionality requests as if they were pro forma
Worked vignette: reading an ambiguous letter (illustrative)
A letter reads: "The phenomenon is fascinating and the fieldwork is impressive, but the contribution to institutional theory remains underdeveloped; we invite a resubmission if the authors can sharpen the theoretical move." Two authors read this oppositely — one as encouragement, one as a polite reject. The correct read at OS: this is a high-risk reject-and-resubmit, not a routine major revision. The praise is for the empirics; the binding problem is the theoretical contribution, which means the revision is closer to a partial rewrite than a polish. Proceed only if you can genuinely make the institutional-theory move land (route to orgstud-theory-development and orgstud-contribution-framing); otherwise reposition. Treating it as a minor revision and resubmitting with cosmetic edits is the fast path to a final reject.
Output format
【Outcome】desk reject / reject / reject-resubmit / major / minor
【Contribution survives?】yes / needs rebuild / no
【Editor's essential threads】the must-address asks
【Theory-level asks】mechanism / literature / reflexivity items flagged central
【Decision】revise for OS / reposition (which sibling)
【Next skill】orgstud-rebuttal (if revising)© 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 Organization-Studies-Skills/skills/orgstud-review-process of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Orgstud Review Process 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Orgstud Review Process this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.5k | Automated safety check: Pass | MIT | |
| Study Plananthropics/claude-for-legal | 9.6k | 3 repos | ~3.5k | Automated safety check: Pass | Apache-2.0 | |
| Lesson Study Cycle DesignerGarethManning/education-agent-skills | 837 | — | ~6.7k | Automated safety check: Pass | Custom licence | |
| Expectmillionco/expect | 3.6k | — | ~988 | Automated safety check: Pass | MIT | |
| CLI Anything CalibreHKUDS/CLI-Anything | 52k | — | ~1.8k | Automated safety check: Notes | Apache-2.0 | |
| Study BuddyLeoYeAI/openclaw-master-skills | 2.2k | — | ~5.5k | Automated safety check: Pass | MIT |
Similar skills
- Official
Lesson Study Cycle Designer
GarethManning/education-agent-skills
Design a complete lesson study cycle from research question through collaborative planning to research lesson.
Expect
millionco/expect
A skill your agent uses when editing .tsx/.jsx/.css/.html, React components, pages, routes, forms, styles, or layouts.
CLI Anything Calibre
HKUDS/CLI-Anything
Command-line interface for Calibre - A stateful CLI harness for e-book library management, metadata editing, and format conversion wrapping the real Calibre tools (calibredb, ebook-convert…
Study Buddy
LeoYeAI/openclaw-master-skills
When user asks to study, create flashcards, take a quiz, make notes, revise, set study timer, track study hours, create study plan, explain a topic, test knowledge, do spaced repetition, summarize a…
Credit Cycle Analysis
sickn33/agentic-awesome-skills
Debtor and creditor credit-cycle analysis: weighted collection or payment days, ageing buckets, credit limit utilisation and gap against benchmark.
More from brycewang-stanford/Awesome-Journal-Skills
All 2,387 skills in this repoAaag 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…
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…
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…
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…
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…
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…
Questions about Orgstud Review Process
What does Orgstud Review Process do?
A skill your agent uses when calibrating expectations for the Organization Studies (OS) review cycle — desk-screen odds, the developmental double-anonymized process, decision types, and how to read…. Orgstud Review Process is an agent skill from brycewang-stanford/Awesome-Journal-Skills. 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.
When should I use Orgstud Review Process?
Orgstud Review Process fits situations like: calibrating expectations for the Organization Studies (OS) review cycle — desk-screen odds; the developmental double-anonymized process; how to read what reviewers and the handling editor are signalling.
How do I install Orgstud Review Process in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill orgstud-review-process -a claude-code`. Or copy the skill folder (Organization-Studies-Skills/skills/orgstud-review-process in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/orgstud-review-process in your project. Claude Code loads it when a task matches its description.
How do I install Orgstud Review Process in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill orgstud-review-process -a codex`. Or copy the skill folder (Organization-Studies-Skills/skills/orgstud-review-process in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/orgstud-review-process in your project. Codex loads it when a task matches its description.
Can I use Orgstud Review Process 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 orgstud-review-process -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/orgstud-review-process, .gemini/skills/orgstud-review-process, .github/skills/orgstud-review-process and .opencode/skills/orgstud-review-process in your project.
What does Orgstud Review Process need to run?
SKILL.md names no scripts, command-line tools or credentials: Orgstud Review Process is instructions for the agent only.
Does Orgstud Review Process 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 Orgstud Review Process 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 Orgstud Review Process use?
Orgstud Review Process 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 Orgstud Review Process use?
About 1.5k tokens (SKILL.md is roughly 5.9k 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 Orgstud Review Process?
Skills that share tags, products or a category with Orgstud Review Process: Study Plan (anthropics/claude-for-legal, 9.6k stars), Lesson Study Cycle Designer (GarethManning/education-agent-skills, 837 stars), Expect (millionco/expect, 3.6k stars) and CLI Anything Calibre (HKUDS/CLI-Anything, 52k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Orgstud Review Process?
brycewang-stanford (a GitHub user) maintains it in brycewang-stanford/Awesome-Journal-Skills, which has 1,228 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.