jaar-review-process
Use to understand how the Journal of the American Academy of Religion (JAAR) evaluates a manuscript — editor pre-screening for broad significance, double-blind review, a roughly 90% rejection rate, a months-long timeline, and a commissioned-only book-review section. Sets expectations and shapes the article to survive; it does not contact editors.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jaar-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 (jaar-review-process) JAAR is highly selective (about **90% of submissions are rejected**) and screens hard **before** peer review. Knowing the gates lets you avoid the common early deaths and set realistic expectations. ## When to trigger - Before submitting, to stress-test against JAAR's gates - Interpreting a decision letter and timeline - Wondering whether to propose a book review (don't submit unsolicited — see below) ## How JAAR review works 1. **Editorial pre-screening (the first gate).** The editorial office reads **every** submission and decides whether to send it out. Two common pre-review outcomes: returned to **reframe** for broad significance (if it reads as subfield-only), or advised that **another journal** suits it better. 2. **Double-blind (double-anonymous) review.** Reviewers do not know authors and authors do not know reviewers; you submit an **anonymized main document** plus a **separate title page** (see `jaar-submission`). 3. **Selectivity.** ~90% rejection; roughly **eight articles per issue / ~32 per year**. Strong, field-significant, thesis-driven, method-conscious work clears; description does not. 4. **Timeline.** Plan for a months-long
- When to trigger
- How JAAR review works
- Book reviews (a separate, commissioned track)
- Shape the article to pass
- Anti-patterns
- Output format
- The two-gate map of a JAAR decision
- Worked vignette: predicting the bounce before you submit
- Referee-stance patterns and what they signal
- Supplementary resources
What does the jaar-review-process skill do?
Use to understand how the Journal of the American Academy of Religion (JAAR) evaluates a manuscript — editor pre-screening for broad significance, double-blind review, a roughly 90% rejection rate, a months-long timeline, and a commissioned-only book-review section. Sets expectations and shapes the article to survive; it does not contact editors.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jaar-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.