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

Jibs Review Process

ASecurity

Use when setting expectations for, or interpreting, the Journal of International Business Studies (JIBS) editorial process — the desk-screen, double-blind review, area-editor routing by IB subfield, the methods-editorial standards reviewers apply, and how to read a JIBS decision letter. Explains the process; the response letter itself is drafted with jibs-rebuttal.

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

Security Analysis

A100/100

Scanned 6/5/2026

Install to Claude Code

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

Installs into .claude/skills of the current project.

Are you the author of Jibs Review Process?

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

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

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

Download with Pro
Files
SKILL.md
---
name: jibs-review-process
description: Use when setting expectations for, or interpreting, the Journal of International Business Studies (JIBS) editorial process — the desk-screen, double-blind review, area-editor routing by IB subfield, the methods-editorial standards reviewers apply, and how to read a JIBS decision letter. Explains the process; the response letter itself is drafted with jibs-rebuttal.
---

# Understanding JIBS Review (jibs-review-process)

## When to trigger

- Before submitting, to calibrate expectations for the JIBS process
- You received a JIBS decision letter and need to interpret it
- You are unsure how area editors and the methods canon shape your review
- You want to know what "revise and resubmit" implies at JIBS specifically

## How the JIBS process works

1. **Editorial desk-screen.** Submissions are first screened by the editorial team for fit and contribution before going to reviewers; weak-fit or phenomenon-free papers can be desk-rejected quickly. (The EIC vision piece reports an approximate ~5-day desk-reject and ~62-day first-decision target — treat as indicative, not guaranteed.)
2. **Area-editor routing.** JIBS uses a departmental/area-editor structure organized by IB subfield (economics-finance-accounting, strategy, organization & management, marketing & operations, entrepreneurship, political economy/public policy, culture-conflict-cognition, HR/IR). Your keyword/area choice routes the paper; the area editor manages the review and writes the integrative decision.
3. **Double-blind review.** Authors and reviewers are mutually anonymous; usually multiple reviewers from the relevant IB conversation. The editorial board also includes a Research Methods Advisory Committee and a Societal Impact Advisory Committee as full editors, reflecting JIBS's emphasis on method rigor and impact.

## What reviewers hold you to

JIBS reviews are demanding on a recognizable set of IB-specific points:

- **Phenomenon & contribution.** Is there a real cross-border phenomenon, and an explicit, non-incremental contribution to IB theory?
- **Cross-national measurement equivalence and construct validity** — first-order, not an afterthought.
- **Common-method variance** — survey/same-respondent papers showing CMV symptoms are routinely asked to run validity checks and resubmit (a dedicated CMV editorial exists).
- **Endogeneity / dynamic endogeneity** — especially for internationalization-as-process designs.
- **The methods-editorial canon.** The ~28 AIB Research Methods SIG "From the Editors" editorials (2008–2022) on endogeneity, multilevel models, interactions, QCA, replication, CMV, and p-values function as de facto standards; reviewers cite them by name.

## Reading a JIBS decision letter

- **Reject / desk-reject:** usually a fit, phenomenon, or fundamental-identification problem; re-target (JWB/MIR/IBR) or rebuild.
- **Major revision (R&R):** the common path forward — the contribution is plausible but theory, measurement, or identification must be strengthened. First-round accepts are essentially unheard of.
- **Minor revision:** confirm and tighten; address each point precisely.
- Read the **area editor's letter as the priority map** — it integrates and ranks the reviewer concerns. Where a reviewer cites a specific methods editorial, treat compliance with it as required, not optional.

## Output format

```
【Decision type】desk-reject / reject / major R&R / minor / accept ...
【Editor's priorities】ranked from the area-editor letter ...
【Recurring IB concerns flagged】phenomenon / invariance / CMV / endogeneity ...
【Methods editorials invoked】which, and what they require ...
【Feasibility】addressable in one round? ...
【Next step】jibs-rebuttal (plan revisions, then draft response)
```

## Anti-patterns

- Treating the reviewers and the area editor as equal voices — the area editor sets priorities.
- Ignoring a cited "From the Editors" methods editorial.
- Reading a major R&R as a near-accept; budget substantive new analysis.
- Re-submitting elsewhere without fixing a phenomenon/fit problem.

Attribution

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

Your tool, in front of Claude Code builders.

3 founder slots · $299/mo · GSC-verified traffic · sponsors can never buy grades.

See placements

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

Your tool, in front of Claude Code builders.

3 founder slots · $299/mo · GSC-verified traffic · sponsors can never buy grades.

See placements

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

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