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

Misq Review Process

ASecurity

Use to understand how MIS Quarterly's editorial process works and to read a decision letter — the double-anonymous model, the Senior-Editor/Associate-Editor routing where the SE owns the decision, what a major/minor revision versus reject signals, and what to expect across one or more revision rounds. Sets expectations and interprets decisions; the response itself is drafted with misq-rebuttal.

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

Works with

terminal

Security Analysis

A100/100

Scanned 6/5/2026

Install to Claude Code

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

Installs into .claude/skills of the current project.

Are you the author of Misq Review Process?

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

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

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

Download with Pro
Files
SKILL.md
---
name: misq-review-process
description: Use to understand how MIS Quarterly's editorial process works and to read a decision letter — the double-anonymous model, the Senior-Editor/Associate-Editor routing where the SE owns the decision, what a major/minor revision versus reject signals, and what to expect across one or more revision rounds. Sets expectations and interprets decisions; the response itself is drafted with misq-rebuttal.
---

# Review Process (misq-review-process)

## When to trigger

- You want to set expectations before or just after submitting to MISQ
- A decision letter arrived and you need to read it correctly before reacting
- You are unsure who owns the decision and how the editors and reviewers relate
- You need to gauge whether a decision is encouraging or terminal

## How MISQ review is structured

MISQ uses **double-anonymous (double-blind) peer review**: authors and reviewers do not know each other's identities. Author and reviewer identities are known to the **Editor-in-Chief, the Senior Editor, the Associate Editor, and editorial staff**, but never to reviewers. The manuscript itself must contain no identifying information.

The routing is two-tier and distinctive:
1. A **Senior Editor (SE)** and an **Associate Editor (AE)** conduct the initial review;
2. if it advances, the paper goes to **external reviewers**;
3. the **Senior Editor owns the decision**, informed by the AE's and reviewers' input.

This SE-owns-the-decision structure (with the EIC overseeing) differs from INFORMS-style departmental area-editor desks; whether MISQ runs a formal area-editor desk structure is 待核实. The current Editor-in-Chief is Susan A. (Sue) Brown (University of Arizona; term Jan 1, 2024 – Dec 31, 2026) — verify the masthead before relying on it.

## Read the decision letter for what it actually says

| Decision | What it usually means | Your posture |
|----------|------------------------|--------------|
| **Major revision** | The SE sees a path; substantial work expected | A genuine opportunity — take every point seriously |
| **Minor revision** | Close; specific fixes remain | Address precisely; do not reopen settled issues |
| **Reject (with reasons)** | Not viable here as framed | Mine the reasons; consider a different framing/venue |
| **Reject and resubmit** (if offered) | Core idea has promise; current execution does not | Treat as a near-new paper |

Expect **one or more rounds of revision** — first-round acceptance is essentially unheard of. The SE's letter, not any single reviewer, is the authoritative guide to what must change.

## Calibrate to the SE letter, not the loudest reviewer

When reviewers conflict, the SE letter signals priorities. Identify which concerns the SE elevated (often theory contribution, identification/evaluation rigor, or transparency) versus reviewer points the SE did not endorse. Plan the revision around the SE's hierarchy.

## What reviewers and the SE will push on

- **Contribution to IS theory** within your tradition (or a defensible cross-tradition blend).
- **Methodological rigor** appropriate to the genre — identification (economics), validity/CMB (behavioral), evaluation against baselines (design science), trustworthiness (qualitative).
- **Research transparency** — whether your genre-appropriate materials and procedures/code support replication.
- **Fit and length** — does the contribution justify the category and stay within the page limit.

## Checklist

- [ ] You can name the SE's top priorities from the letter
- [ ] You distinguish SE-endorsed points from individual-reviewer points
- [ ] You correctly classify the decision (major/minor/reject/reject-and-resubmit)
- [ ] You know which tradition-specific rigor standard you are being held to
- [ ] Expectations set for multiple revision rounds

## Anti-patterns

- Treating every reviewer comment as equally binding regardless of the SE letter.
- Reading a major revision as a near-acceptance (it is real work).
- Reacting to a reject before extracting its reusable lessons.

## Output format

```
【Decision class】major / minor / reject / reject-and-resubmit
【SE priorities】ranked list from the letter
【SE-endorsed vs reviewer-only points】...
【Rigor standard in play】behavioral / economics / design science / qualitative
【Next step】misq-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', ...

686011 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 →