jais-review-process
Use when calibrating expectations for the Journal of the Association for Information Systems (JAIS) editorial process — the developmental, Senior-Editor-led, double-blind review; how the seven-category routing works; what a JAIS decision letter means; and when to engage the journal's developmental culture. Sets expectations and reads decisions; it does not draft the response (jais-rebuttal) or run the submission preflight (jais-submission).
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jais-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 (jais-review-process) ## When to trigger - You are about to submit and want to understand how JAIS will handle the paper - A decision letter arrived and you need to read it correctly before reacting - You are unsure who owns the decision (Senior Editor vs. reviewers) and how to weight comments - You want to understand JAIS's "developmental reviewing" culture and how to engage it - You are deciding whether a major-revision invitation is worth the effort or signals a likely path to acceptance ## Fit is screened before quality Like its Basket siblings, JAIS screens **fit** before it spends reviewer effort on quality — the Editor-in-Chief (or a deputy) assesses whether the paper belongs in JAIS and in the declared category before routing it for full review. This is why a technically excellent paper can be desk-rejected: not because the work is weak, but because the contribution is not a JAIS contribution, or the category is wrong. Practically, the fit screen rewards the upstream work in `jais-topic-selection` and `jais-contribution-framing` more than any amount of late polish. If you keep getting desk rejects, the problem is almost always fit or contribution, not execu
- When to trigger
- Fit is screened before quality
- How JAIS review actually works
- Category routing shapes the review
- What the seven Senior Editors signal about routing
- Read the decision letter for what it actually says
- Timeline and expectations, calibrated
- Weight the comments by authorship
- Checklist
- Engage the developmental culture deliberately
- Worked reading of a decision letter (illustrative)
- Anti-patterns
- Output format
What does the jais-review-process skill do?
Use when calibrating expectations for the Journal of the Association for Information Systems (JAIS) editorial process — the developmental, Senior-Editor-led, double-blind review; how the seven-category routing works; what a JAIS decision letter means; and when to engage the journal's developmental culture. Sets expectations and reads decisions; it does not draft the response (jais-rebuttal) or run the submission preflight (jais-submission).
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jais-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.