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 Rebuttal

ASecurity

Use after a Journal of Business Venturing (JBV) R&R to plan revisions and draft the point-by-point response letter — prioritizing the field editor's concerns, defending or strengthening the entrepreneurship contribution, and addressing selection/survivorship/identification threats across multiple rounds. Drafts the revision plan and response; interpret the letter first with jbv-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 jbv-rebuttal --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Jbv Rebuttal?

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

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

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

Download with Pro
Files
SKILL.md
---
name: jbv-rebuttal
description: Use after a Journal of Business Venturing (JBV) R&R to plan revisions and draft the point-by-point response letter — prioritizing the field editor's concerns, defending or strengthening the entrepreneurship contribution, and addressing selection/survivorship/identification threats across multiple rounds. Drafts the revision plan and response; interpret the letter first with jbv-review-process.
---

# R&R Rebuttal (jbv-rebuttal)

## When to trigger

- You received a major-revision (R&R) decision from a JBV field editor
- You have revised (or are planning to revise) and need the response letter
- Reviewers disagree, or a reviewer doubts the entrepreneurship contribution
- You are in a later round and must show cumulative progress

## Revise first, then write the letter

Do not draft the response before the manuscript is actually revised — a response that promises changes not yet made reads as evasive to a developmental field editor.

## Prioritize the field editor's concerns

Because **field editors own the decision** at JBV, their letter sets the priorities:

1. Address the field editor's make-or-break concerns first and most thoroughly, especially any "is the entrepreneurship contribution central and real?" worry.
2. Then resolve the integrative cross-cutting concern that unlocks several reviewer points.
3. Then the remaining reviewer points, grouped by theme.

## Defend the phenomenon-driven contribution

JBV's bar is advancing theory about the entrepreneurial phenomenon. If a reviewer says "this could be any organization," do not just add startup vocabulary — show the mechanism is specifically entrepreneurial (uncertainty, novelty/liability of newness, opportunity, founding choice) and sharpen the contribution statement.

## Handle the recurring empirical objections

- **Selection into founding / survivorship**: add a selection model, bounds, an alternative frame including failed ventures, or a robustness sample; report what changes.
- **Identification/endogeneity**: add IV/DiD/matching or a design-based check, and state the identifying assumption plainly.
- **Generalizability of a novel dataset**: document the frame and add external corroboration where possible.

## Write a disciplined point-by-point response

- Reproduce each comment verbatim, then respond directly beneath it.
- Quote the new manuscript text and give the page/line so the editor can verify quickly.
- Be respectful and concede where the reviewer is right; where you disagree, give evidence, not assertion.
- Summarize the major changes in an opening cover note to the field editor.
- Maintain anonymity in any shared materials across rounds.

## Checklist

- [ ] Manuscript revised before the letter is written
- [ ] Field editor's priority concerns addressed first and fully
- [ ] Entrepreneurship contribution defended/strengthened, not just relabeled
- [ ] Selection/survivorship/identification objections answered with new analysis
- [ ] Every comment reproduced and answered with page/line pointers
- [ ] Disagreements supported by evidence; concessions made where due
- [ ] Cover note summarizes major changes for the field editor

## Anti-patterns

- **Response before revision** — promising edits not yet in the paper.
- **Vocabulary fix** for an "entrepreneurship is incidental" critique instead of a real mechanism fix.
- **Defensiveness** — arguing rather than addressing a fair identification concern.
- **Treating all comments as equal weight**, ignoring the field editor's priorities.

## Output format

```
【Round】1 / 2 / ... ; decision = major R&R ...
【Field-editor priorities addressed】...
【Entrepreneurship contribution】how strengthened ...
【Selection/survivorship/identification】new analyses ...
【Point-by-point status】addressed / partially / pushed back (with evidence) ...
【Cover note】major-changes summary drafted? ...
【Next step】resubmit via Editorial Manager
```

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 →