Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsCommunityBlog
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Orgsci Review Process

ASecurity

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-anonymous reviewing, and how to read a decision letter at this venue.

1,052 stars
0 votes
0 copies
1 views
Added 6/6/2026
ai-agentsgo

Security Analysis

A100/100

Scanned 6/6/2026

Install to Claude Code

$npx -y skills add brycewang-stanford/Awesome-Journal-Skills --skill orgsci-review-process --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Orgsci Review Process?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Orgsci Review Process
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/brycewang-stanford-orgsci-review-process/badge)](https://www.skillsdirectory.com/skills/brycewang-stanford-orgsci-review-process)

More formats (shields.io, HTML) on the badges page.

Download with Pro
Files
SKILL.md
---
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-anonymous reviewing, 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 read the **<500-word contribution statement and the abstract** first. A missing statement gets the paper **returned before editorial review**; an unconvincing contribution, poor fit, 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** under **double-anonymous** review; 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.** Resubmit an R&R promptly (a ~one-year window is reported but **待核实** — confirm in your letter).

## Anti-patterns

- Treating reviewer comments as equal to the SE's verdict and ignoring the SE's prioritization.
- Expecting area-editor routing or a code-and-data deposit mandate (those are Management Science).
- Assuming a desk return is a rejection when it may be a fixable missing contribution statement.

## 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】resubmission timeframe (confirm; ~1 year 待核实)
【Next step】orgsci-rebuttal
```

Attribution

brycewang-stanfordbrycewang-stanford
View sourceMore from brycewang-stanford →
SSkills DirectorySkills Directory

Your tool, in front of Claude Code builders.

3 founder slots · $299/mo · GSC-verified traffic · sponsors can never buy grades.

See placements

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Your tool, in front of Claude Code builders.

3 founder slots · $299/mo · GSC-verified traffic · sponsors can never buy grades.

See placements

Related Skills

Caveman

Ultra-compressed communication mode that cuts output tokens while keeping technical accuracy. Levels: lite, full, ultra and the wenyan variants. Use for /caveman, "caveman mode", "talk like caveman", "be brief" or "less tokens".

1066601 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

693161 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3351 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

651 votes

math-skill

A comprehensive mathematical reasoning skill for AI assistants — handles arithmetic to research-level problems with rigorous step-by-step reasoning, systematic verification, and transparent uncertainty handling

381 votes
View all in ai-agents →