Video Understand
calesthio/OpenMontage
Understand video content locally using ffmpeg frame extraction and Whisper transcription.
A skill your agent uses when you want to understand how Organization Science review and decisions work before or after submitting — the decentralized senior-editor model with strong SE autonomy, the…
MITAuto-check passed
Install Orgsci Review Process
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill orgsci-review-process -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills orgsci-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-Science-Skills/skills/orgsci-review-process .claude/skills/orgsci-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 "orgsci-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Organization-Science-Skills/skills/orgsci-review-process into .claude/skills/orgsci-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "orgsci-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-Science-Skills/skills/orgsci-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 orgsci-review-process -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills orgsci-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-Science-Skills/skills/orgsci-review-process .agents/skills/orgsci-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 "orgsci-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Organization-Science-Skills/skills/orgsci-review-process into .agents/skills/orgsci-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "orgsci-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 orgsci-review-process -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills orgsci-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-Science-Skills/skills/orgsci-review-process .cursor/skills/orgsci-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 "orgsci-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Organization-Science-Skills/skills/orgsci-review-process into .cursor/skills/orgsci-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "orgsci-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-Science-Skills/skills/orgsci-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 orgsci-review-process -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills orgsci-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-Science-Skills/skills/orgsci-review-process .gemini/skills/orgsci-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 "orgsci-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Organization-Science-Skills/skills/orgsci-review-process into .gemini/skills/orgsci-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "orgsci-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 orgsci-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 orgsci-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-Science-Skills/skills/orgsci-review-process .github/skills/orgsci-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 "orgsci-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Organization-Science-Skills/skills/orgsci-review-process into .github/skills/orgsci-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "orgsci-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 orgsci-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 orgsci-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-Science-Skills/skills/orgsci-review-process .opencode/skills/orgsci-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 "orgsci-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Organization-Science-Skills/skills/orgsci-review-process into .opencode/skills/orgsci-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "orgsci-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
orgsci-review-process- GitHub stars
- 1.2k
- Token cost
- ~1.1k tokens
- SKILL.md length
- 499 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when you want to understand how Organization Science review and decisions work before or after submitting — the decentralized senior-editor model with strong SE autonomy, the…
- You want to understand how Organization Science review and decisions work before
- SKILL.md covers When to trigger, The decentralized…, What happens to your submission and Reading the decision letter, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- After submitting — the decentralized senior-editor model with strong SE autonomy
What it does
Orgsci Review Process is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when you want to understand how Organization Science review and decisions work before or after submitting — the decentralized senior-editor model with strong SE autonomy, the conflict-of-interest routing cascade, double-blind submission preparation, and how to read a decision letter at this venue.
Its SKILL.md is about 1.1k 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
- You want to understand how Organization Science review and decisions work before
- After submitting — the decentralized senior-editor model with strong SE autonomy
- The conflict-of-interest routing cascade
- Double-blind submission preparation
Example prompts
- “/orgsci-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
Orgsci Review Process loads about 1.1k tokens when it runs. Until then it costs about 81 tokens; SKILL.md has 499 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). 499 words, ~1,113 tokens.
Download SKILL.mdSave it as
.claude/skills/orgsci-review-process/SKILL.md (or your agent's skills folder).- name
- orgsci-review-process
- description
- Use when you want to understand how Organization Science review and decisions work before or after submitting — the decentralized senior-editor model with strong SE autonomy, the conflict-of-interest routing cascade, double-blind submission preparation, and how to read a decision letter at this venue.
Review Process (orgsci-review-process)
When to trigger
- You are about to submit and want to set expectations
- You received a decision letter and need to interpret who decided and why
- You are unsure how Organization Science routing differs from a departmental area-editor journal
The decentralized senior-editor model
Organization Science runs a decentralized model: Senior Editors plus an Editorial Review Board, under Editor-in-Chief Lamar Pierce (Washington University in St. Louis). Each Senior Editor has strong autonomy — an SE can independently accept, reject, or request an R&R. This differs sharply from sister journal Management Science's fixed departmental area-editor routing: here the SE decides your paper, not a department head dispatching to an area editor. Routing follows a conflict-of-interest cascade — the EIC handles deputy-editor submissions and deputy editors handle senior-editor submissions — so editors do not adjudicate their own work.
What happens to your submission
- Desk review. The EIC/SE can see the cover letter and abstract. An unconvincing contribution, poor fit, transparency gap, or excessive length can produce a desk reject (overlong submissions may be returned with an option to resubmit shorter).
- Peer review. If sent out, it goes to at least two reviewers; follow the submission guidelines' double-blind preparation rules and keep the main manuscript anonymized. The cover letter is seen by the EIC and SE but not by reviewers.
- Decision. The SE synthesizes reviews into accept / reject / R&R. First-round accepts are rare; the realistic best early outcome is a major R&R.
Reading the decision letter
- Identify the decider. The SE letter is binding; reviewer comments are inputs the SE weights — when they differ, the SE's framing governs your revision priorities.
- Find the core concern. Usually overall contribution, mechanism, or fit — not just method, given the "novelty is neither necessary nor sufficient" stance and the acceptance that causal identification is often impossible.
- Note the window. The submission guidelines ask authors to resubmit invited revisions within 6 months unless the editor grants an exception.
Show full SKILL.md (180 more words)Show less
Anti-patterns
- Treating reviewer comments as equal to the SE's verdict and ignoring the SE's prioritization.
- Expecting area-editor routing or ignoring the 2025 data/methods transparency policy.
- Assuming a desk return is a rejection when it may be a fixable compliance or length issue.
Review-risk pass for Organization Science
Use this as a second-pass capability check. First lock a level map, a mechanism paragraph, and the cover-letter contribution statement; then test whether the manuscript addresses interdisciplinary organization reviewers who ask whether the mechanism travels across levels of analysis.
- Primary move: Turn likely reviewer objections into a ledger with response evidence, manuscript location, and the decision-maker who must be convinced first.
- Decision ledger: return
claim / evidence / blocker / next editrows so the next pass can patch the manuscript directly. - Neighbor test: compare against AMJ for empirical management framing, ASQ for organization-theory depth, Management Science for formal/quantitative operations; if the neighboring outlet has the stronger audience claim, recommend re-routing before polishing.
- Submission-ready gate: before final advice, re-open
resources/official-source-map.mdfor upload-week rules and name the one live-check item that could change the recommendation.
Output format
【Decider】Senior Editor (autonomous accept/reject/R&R); EIC Lamar Pierce; COI cascade routing
【Stage reached】desk return / desk reject / out for review / R&R / reject
【Core concern】overall contribution / mechanism / fit (method usually secondary)
【SE vs reviewers】whose framing governs the revision
【Window】6-month invited-revision window unless editor grants an exception
【Next step】orgsci-rebuttal© 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-Science-Skills/skills/orgsci-review-process of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Orgsci 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 |
|---|---|---|---|---|---|---|
| Orgsci Review Process this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Video Understandcalesthio/OpenMontage | 66k | — | ~841 | Automated safety check: Pass | AGPL-3.0 | |
| Understand ExplainEgonex-AI/Understand-Anything | 86k | — | ~1.3k | Automated safety check: Pass | MIT | |
| Understanding by Design PlannerTHU-MAIC/OpenMAIC | 40k | — | ~548 | Automated safety check: Pass | MIT | |
| Understand Diff AnalysisEgonex-AI/Understand-Anything | 86k | — | ~1.4k | Automated safety check: Pass | MIT | |
| Understand Issuemastra-ai/mastra | 29k | — | ~3.1k | Automated safety check: Pass | Custom licence |
Similar skills
Understand Explain
Egonex-AI/Understand-Anything
Gives an in-depth explanation of one file, function or module by reading the project's knowledge graph and checking that the graph is still fresh.
Understanding by Design Planner
THU-MAIC/OpenMAIC
Plans an OpenMAIC lesson or course series by backward design: enduring understandings and essential questions first, then performance evidence, then learning activities.
Understand Diff Analysis
Egonex-AI/Understand-Anything
Reads your git changes or a pull request against a prebuilt knowledge graph of the project to explain what changed, which components are affected and what is risky.
Understand Issue
mastra-ai/mastra
Investigate a GitHub issue or reported bug the way a seasoned maintainer would — form an independent model before reading the thread's theories, trace the mechanism and history, verify the…
Understand PR
mastra-ai/mastra
Review a PR the way a seasoned maintainer would — build an independent model before seeing the diff, investigate the implementation and history, verify material claims, and return a concise briefing.
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 Orgsci Review Process
What does Orgsci Review Process do?
A skill your agent uses when you want to understand how Organization Science review and decisions work before or after submitting — the decentralized senior-editor model with strong SE autonomy, the…. Orgsci Review Process is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when you want to understand how Organization Science review and decisions work before or after submitting — the decentralized senior-editor model with strong SE autonomy, the conflict-of-interest routing cascade, double-blind submission preparation, and how to read a decision letter at this venue.
When should I use Orgsci Review Process?
Orgsci Review Process fits situations like: you want to understand how Organization Science review and decisions work before; after submitting — the decentralized senior-editor model with strong SE autonomy; the conflict-of-interest routing cascade; double-blind submission preparation.
How do I install Orgsci Review Process in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill orgsci-review-process -a claude-code`. Or copy the skill folder (Organization-Science-Skills/skills/orgsci-review-process in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/orgsci-review-process in your project. Claude Code loads it when a task matches its description.
How do I install Orgsci Review Process in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill orgsci-review-process -a codex`. Or copy the skill folder (Organization-Science-Skills/skills/orgsci-review-process in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/orgsci-review-process in your project. Codex loads it when a task matches its description.
Can I use Orgsci 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 orgsci-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/orgsci-review-process, .gemini/skills/orgsci-review-process, .github/skills/orgsci-review-process and .opencode/skills/orgsci-review-process in your project.
What does Orgsci Review Process need to run?
SKILL.md names no scripts, command-line tools or credentials: Orgsci Review Process is instructions for the agent only.
Does Orgsci 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 Orgsci 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 Orgsci Review Process use?
Orgsci 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 Orgsci Review Process use?
About 1.1k tokens (SKILL.md is roughly 4.5k 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 Orgsci Review Process?
Skills that share tags, products or a category with Orgsci Review Process: Video Understand (calesthio/OpenMontage, 66k stars), Understand Explain (Egonex-AI/Understand-Anything, 86k stars), Understanding by Design Planner (THU-MAIC/OpenMAIC, 40k stars) and Understand Diff Analysis (Egonex-AI/Understand-Anything, 86k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Orgsci 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.