jbv-review-process
Use when understanding how the Journal of Business Venturing (JBV) review process works — Co-EIC / area-editor routing, double-anonymized review by a minimum of two reviewers, desk-reject risk for off-phenomenon work, and reading a JBV decision letter. Explains the process and reads the letter; the response is drafted with jbv-rebuttal.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jbv-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 (jbv-review-process) ## When to trigger - You want to set expectations before or after submitting to JBV - You received a decision letter and need to interpret it - You are unsure who decides and what the bar is - You want to gauge desk-reject risk before submitting ## How JBV review works - **Area-editor routing**: ScienceDirect lists current Co-Editors-in-Chief Sophie Bacq and Simon Parker and an editorial-board structure with area editors by domain. Fit with the relevant area shapes both routing and outcome — make your home conversation obvious so the paper reaches a sympathetic, expert editor. - **Double-anonymized review**: suitable manuscripts are sent to a **minimum of two reviewers**; neither side sees identities. Off-fit or insufficiently theorized papers may be **desk-rejected** by the editor before review — common at this FT50 flagship. - **The bar**: reviewers and the handling editor judge whether the paper advances theory about the **entrepreneurial phenomenon**, not just whether the method is clean. "Entrepreneurship is only the setting" is a frequent reject rationale. ## Likely decision outcomes - **Desk reject**: off-topic, entrepreneurship incident
- When to trigger
- How JBV review works
- Likely decision outcomes
- Reading the decision letter
- Norms & culture
- Checklist
- Desk-reject pattern map (read before submitting)
- Worked micro-example: reading a JBV letter (illustrative)
- Calibration anchors (hedged)
- Anti-patterns
- Output format
What does the jbv-review-process skill do?
Use when understanding how the Journal of Business Venturing (JBV) review process works — Co-EIC / area-editor routing, double-anonymized review by a minimum of two reviewers, desk-reject risk for off-phenomenon work, and reading a JBV decision letter. Explains the process and reads the letter; the response is drafted with jbv-rebuttal.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jbv-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.