jmis-review-process
Use when calibrating expectations for the Journal of Management Information Systems (JMIS) editorial process — the EIC-led, email-intake, double-anonymized review by Associate Editors and expert referees, likely decision types, and timing. Sets expectations and revision posture; it does not draft the response letter (jmis-rebuttal).
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jmis-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 (jmis-review-process) ## When to trigger - Before submitting, to understand who decides and how long it takes at JMIS - A decision letter arrived and you need to read its severity correctly before responding - You are weighing JMIS against MISQ/ISR/JAIS on process and turnaround - You want to know what a desk-reject vs. a review-and-reject signals ## How JMIS review actually runs JMIS is an **Editor-in-Chief-led** journal: founding and current EIC **Vladimir Zwass** receives submissions directly by email and steers the process. Papers are **refereed in a double-anonymized process** by internationally recognized expert referees and by **Associate Editors** on the Editorial Board. Practically, this means: - **The EIC is the first gate.** A paper that is out of scope (not an IS-management/economics question), over length, or not anonymized can be returned or desk-rejected before external review. Fit is judged against JMIS's management/economics-of-IS identity, not generic IS breadth. - **AEs and referees carry the substantive review.** Expect method-literate referees who will press on identification (empirical), assumptions and insight (analytical), measurement and CM
- When to trigger
- How JMIS review actually runs
- Read the decision letter for what it is asking
- What the EIC-led model means for you, concretely
- Match the review style to your evidence type
- Calibrate timing and expectations
- Checklist
- Anti-patterns
- Decide whether to revise or reroute
- Set author expectations before the wait
- Output format
What does the jmis-review-process skill do?
Use when calibrating expectations for the Journal of Management Information Systems (JMIS) editorial process — the EIC-led, email-intake, double-anonymized review by Associate Editors and expert referees, likely decision types, and timing. Sets expectations and revision posture; it does not draft the response letter (jmis-rebuttal).
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jmis-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.