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

Jbv Review Process

ASecurity

Use when understanding how the Journal of Business Venturing (JBV) review process works — field-editor routing under the EIC, 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.

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

Security Analysis

A100/100

Scanned 6/5/2026

Install to Claude Code

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

Installs into .claude/skills of the current project.

Are you the author of Jbv Review Process?

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

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

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

Download with Pro
Files
SKILL.md
---
name: jbv-review-process
description: Use when understanding how the Journal of Business Venturing (JBV) review process works — field-editor routing under the EIC, 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.
---

# 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

- **Field-editor routing**: under EIC Jeffery S. McMullen, manuscripts are managed by **field editors (handling editors)** who own the decision for papers in their domain. Field editors curate their own trusted reviewer pools, so fit with a field editor's 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 field 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 incidental, or insufficiently theorized; sometimes a fit/scope mismatch.
- **Reject after review**: a fatal identification/selection/survivorship problem, or a contribution judged incremental.
- **Major revision (R&R)**: the phenomenon and contribution are promising but theory, identification, or framing need substantial work — the normal path to acceptance.
- **Minor revision**: targeted fixes; less common on a first decision.

## Reading the decision letter

1. **Field editor's letter first** — it states the decision and the *priority* concerns; these are the make-or-break issues.
2. **Sort reviewer points** into: theory/contribution, identification/selection/survivorship, framing/positioning, and presentation.
3. **Find the integrative concern** — the cross-cutting worry (often "is the entrepreneurship contribution real?") that, if solved, resolves several points.
4. **Gauge invitation strength** — does the editor signal genuine interest, or a courtesy R&R? Calibrate effort accordingly.

## Norms & culture

- JBV's editorial office is embedded in an entrepreneurship center (Kelley/Indiana) with a strong reviewer-development and best-reviewer/best-paper-award culture — a community-stewardship ethos. Expect developmental, substantive reviews.
- Reviewing reciprocity is part of the community; engage constructively.

## Checklist

- [ ] Identified the field editor's priority concerns
- [ ] Reviewer points sorted (theory / identification / framing / presentation)
- [ ] Integrative concern named
- [ ] Invitation strength gauged (genuine R&R vs. courtesy)
- [ ] Desk-reject risks (off-phenomenon, thin theory) checked pre-submission

## Anti-patterns

- **Treating reviewers as a checklist** while ignoring the field editor's priorities.
- **Underestimating desk-reject risk** for entrepreneurship-as-setting papers.
- **Assuming first-round acceptance** — multi-round R&R is the norm.

## Output format

```
【Decision】desk-reject | reject | major R&R | minor ...
【Field-editor priorities】top concerns ...
【Integrative concern】the cross-cutting issue ...
【Point map】theory / identification / framing / presentation ...
【Invitation strength】genuine | courtesy ...
【Next step】jbv-rebuttal (if R&R)
```

Attribution

brycewang-stanfordbrycewang-stanford
View sourceMore from brycewang-stanford →
SSkills DirectorySkills Directory

Know which skills are safe — weekly.

Best new skills + every skill we flagged as malicious. From the team that scanned 103,619.

Join free

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

Know which skills are safe — weekly.

Best new skills + every skill we flagged as malicious. From the team that scanned 103,619.

Join free

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', ...

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