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

Smj Rebuttal

ASecurity

Use when drafting the response letter and revising a Strategic Management Journal (SMJ) manuscript after an R&R decision. Structures the point-by-point response; it assumes the revision plan from smj-review-process is set.

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

Security Analysis

A100/100

Scanned 6/6/2026

Install to Claude Code

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

Installs into .claude/skills of the current project.

Are you the author of Smj Rebuttal?

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

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

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

Download with Pro
Files
SKILL.md
---
name: smj-rebuttal
description: Use when drafting the response letter and revising a Strategic Management Journal (SMJ) manuscript after an R&R decision. Structures the point-by-point response; it assumes the revision plan from smj-review-process is set.
---

# R&R Response & Rebuttal (smj-rebuttal)

## When to trigger

- You received a Major/Minor Revision and have revised (or are revising) the manuscript
- You need to write the response-to-reviewers letter
- You must decide how to respond to a comment you disagree with
- The manuscript changes are in progress but the response document is not yet written

> Revise the manuscript first. A response letter written before the actual edits exist will over-promise and drift from the paper.

## The response-letter structure

1. **Opening to the editor.** Thank the action editor and reviewers; state that you have revised substantially; summarize the **2–4 most important changes** (lead with how you addressed the gating concern — usually endogeneity or contribution).
2. **Point-by-point response.** For *every* comment, in order, per reviewer:
   - Quote or paraphrase the comment (verbatim is safest).
   - State your response and **exactly what changed**.
   - Point to the location: "see revised Section 4.2, pp. 18–20, and new Table 5."
3. **Reviewer-by-reviewer grouping** with clear headers (Reviewer 1, 2, …, Editor).
4. **Summary of changes** (optional) and a clean revised manuscript plus, where helpful, a tracked-changes version.

## Responding well

- **Address every comment** — none silently dropped. Even a comment you reject gets a respectful, evidence-based reply.
- **Show, don't assert.** "We now address endogeneity with an instrument (new Section 4.3) and report the first-stage F (Table 4)" beats "we believe endogeneity is not a concern."
- **Lead each reply with the action taken**, then the rationale.
- **Disagree respectfully and with evidence.** When pushing back, acknowledge the concern, present the counter-evidence or theoretical reason, and offer a compromise (e.g., a robustness check or appendix note) where possible.
- **Reconcile conflicting reviewers** explicitly; if two reviewers want opposite things, explain your choice and flag it for the editor.
- **Match tone to the editor's priorities** from the decision letter; the gating concern gets the most thorough treatment.

## SMJ-specific emphases in the response

- If the gating concern was **endogeneity**, your strongest reply is a *design* improvement (instrument, shock, matching, selection model, or partial-identification bounds) with the identification evidence shown — not more controls or rhetoric. This aligns with SMJ's own standard (Bettis, Gambardella, Helfat & Mitchell, 2014, *SMJ* 35: 949–953): a good-faith effort to address endogeneity, and **no spec-mining for better p-values** (SMJ disapproves of data snooping / p-hacking). If causation remains imperfect, reframe the claim honestly — SMJ accepts this.
- If the gating concern was **contribution**, sharpen the theoretical advance and its strategy stakes (loop back to `smj-contribution-framing`); do not merely add findings.
- Keep the manuscript's framing consistent with the letter — reviewers re-read the intro and discussion to check that promised changes actually landed.

## Checklist

- [ ] The manuscript is actually revised before the letter is finalized
- [ ] Every comment from every reviewer and the editor has a response
- [ ] Each reply states the concrete change and its location (section/page/table)
- [ ] The gating concern is addressed first and most thoroughly
- [ ] Push-backs are respectful and evidence-based, with a compromise offered where possible
- [ ] Conflicting reviewer requests are reconciled and flagged to the editor
- [ ] A clean and (if useful) tracked-changes manuscript accompany the letter
- [ ] Tone is professional and grateful throughout

## Anti-patterns

- Silently ignoring or partially answering a comment
- Asserting a concern is unfounded without new evidence (especially on endogeneity)
- Adding more control variables in place of a real identification fix the reviewer asked for
- Defensive or combative tone toward reviewers or the editor
- Promising changes in the letter that are not actually in the revised manuscript
- Letting the intro/discussion framing contradict the changes claimed in the letter
- Treating a "contribution" critique as solvable by piling on more empirical results

## Output format

```
【Decision being answered】major / minor
【Gating concern + how addressed】endogeneity → [new design] / contribution → [sharpened claim]
【Comments answered】all (n) / outstanding: [...]
【Push-backs】[comment → evidence-based reply + compromise]
【Reviewer conflicts reconciled】yes / flagged to editor
【Manuscript versions】clean + tracked
【Tone】grateful, evidence-led
【Next step】re-preflight via smj-submission, then resubmit → smj-review-process for the next round
```

## Templates & resources

- [`../../resources/official-source-map.md`](../../resources/official-source-map.md) — SMJ endogeneity / p-hacking policy (Bettis et al. 2014) and Co-Editor roster
- [`../../resources/external_tools.md`](../../resources/external_tools.md) — packages for added identification / robustness analyses

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 →