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 Rebuttal

ASecurity

Use when planning revisions and drafting the point-by-point response letter after a Journal of International Business Studies (JIBS) revise-and-resubmit — prioritizing by the area editor's letter, executing the cross-national measurement, CMV, and (dynamic-)endogeneity work reviewers demand, and citing the relevant methods editorials. Drafts the revision and response; it does not interpret the decision (jibs-review-process).

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

Security Analysis

A100/100

Scanned 6/5/2026

Install to Claude Code

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

Installs into .claude/skills of the current project.

Are you the author of Jibs Rebuttal?

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

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

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

Download with Pro
Files
SKILL.md
---
name: jibs-rebuttal
description: Use when planning revisions and drafting the point-by-point response letter after a Journal of International Business Studies (JIBS) revise-and-resubmit — prioritizing by the area editor's letter, executing the cross-national measurement, CMV, and (dynamic-)endogeneity work reviewers demand, and citing the relevant methods editorials. Drafts the revision and response; it does not interpret the decision (jibs-review-process).
---

# R&R Revision & Response Letter (jibs-rebuttal)

## When to trigger

- You received a JIBS major/minor revision and need a plan plus a response letter
- Reviewers asked for measurement-invariance, CMV, or endogeneity work and you must execute it
- A reviewer invoked a specific "From the Editors" methods editorial
- You need to reconcile conflicting reviewer requests across IB subfields

## Revise the manuscript before you write the letter

A JIBS response letter documents revisions that already exist; do not promise work you have not done. JIBS R&Rs are substantive and multi-round — budget real new analysis (a new estimator, an invariance test, an instrument), not just rhetoric.

## Prioritize by the area editor's letter

The **area editor's letter is the priority map.** Group reviewer comments under the editor's integrated themes; lead your plan with the concerns the editor elevated (typically: phenomenon/contribution, cross-national measurement, CMV, and endogeneity). Where two reviewers conflict, adjudicate transparently and defer to the editor's framing.

## Execute the IB-specific revision work

- **Phenomenon & contribution.** If "incremental" was raised, sharpen the non-incremental IB contribution and the country/culture-as-level payoff (use jibs-contribution-framing).
- **Measurement equivalence.** If equivalence was challenged, add configural/metric/scalar tests (or alignment/partial-invariance) and state which cross-country comparisons remain defensible.
- **Common-method variance.** If CMV was flagged, add a marker-variable or latent-method-factor analysis (not just Harman), or show interaction/cross-level effects survive; cite the JIBS CMV "From the Editors" editorial.
- **Endogeneity / dynamic endogeneity.** If raised for a process design, execute the identification (IV/first-stage strength, dynamic-panel GMM with Hansen/AR(2), DiD/natural experiment) and discuss assumptions; cite the relevant endogeneity editorial.
- **DART.** Update the Data Accessibility Statement if data-availability questions arose.

## Write the point-by-point response

- Restate each comment verbatim, then respond: what you changed, where (section, page, table), and the new result.
- Quote the relevant **methods editorial** when you adopt its recommended remedy — this signals compliance with JIBS standards.
- Be respectful and concrete; where you disagree, give evidence, not assertion, and offer an alternative.
- Provide a brief summary memo of the major changes at the top, and ensure the revised manuscript still fits the **inclusive** word limit.

## Output format

```
【Editor-priority map】ranked themes from the area-editor letter ...
【Per-comment plan】comment → revision (section/page/table) → status ...
【Measurement/CMV/endogeneity work】executed analyses + editorials cited ...
【Conflicts resolved】reviewer A vs. B adjudication ...
【DART/DAS update】 ...
【Word-budget check】revision still within inclusive limit ...
【Response letter】point-by-point draft ...
```

## Anti-patterns

- Promising analyses in the letter that are not actually in the revision.
- Treating reviewers as equal to the area editor's priority map.
- Answering a CMV/endogeneity request with rhetoric instead of new analysis.
- Ignoring a cited methods editorial the reviewer asked you to follow.
- Letting the revised manuscript drift over the inclusive word limit.

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 →