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

Jmr Rebuttal

ASecurity

Use after a Journal of Marketing Research (JMR) Revise-and-Resubmit — planning the revision and drafting a point-by-point response that satisfies two independent reviewers and the Coeditor, addresses rigor-bar concerns (identification, exact statistics, replication) and substance-bar concerns (contribution), and uses the 'W'-prefixed Web Appendix to absorb new analyses without breaking the 50-page limit.

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

Works with

api

Security Analysis

A100/100

Scanned 6/5/2026

Install to Claude Code

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

Installs into .claude/skills of the current project.

Are you the author of Jmr Rebuttal?

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

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

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

Download with Pro
Files
SKILL.md
---
name: jmr-rebuttal
description: Use after a Journal of Marketing Research (JMR) Revise-and-Resubmit — planning the revision and drafting a point-by-point response that satisfies two independent reviewers and the Coeditor, addresses rigor-bar concerns (identification, exact statistics, replication) and substance-bar concerns (contribution), and uses the 'W'-prefixed Web Appendix to absorb new analyses without breaking the 50-page limit.
---

# R&R Revision & Response (jmr-rebuttal)

## When to trigger

- You received a JMR R&R and need to plan revisions and the response letter
- Reviewers and the Coeditor raise concerns spanning rigor and contribution
- New studies/analyses are needed but the print paper is near the 50-page limit
- You must reconcile conflicting reviewer requests

## Plan before you draft

1. **Triage every point** by which bar it targets — **rigor** (identification, manipulation, exact p-values/SEs/effect sizes, robustness, replication) or **substance** (contribution, framing, "what do we learn?"). JMR's dual standard means both must end up satisfied.
2. **Find the Coeditor's priorities.** The editor's letter signals which concerns are pivotal; weight your effort there. With **two independent reviewers**, expect some conflict — resolve it explicitly rather than splitting the difference silently.
3. **Decide where new material lives.** New robustness, additional studies, and estimation detail usually belong in the **'W'-prefixed Web Appendix** (excluded from the 50-page limit), with a short pointer in the print text — this lets you respond fully without blowing the page budget.

## Draft the point-by-point response

- Reproduce each comment verbatim, then respond directly beneath it.
- For each: state **what you changed**, **where** (section / page / "Table W3 in the Web Appendix"), and **why** it resolves the concern.
- For **rigor** points: run the requested test, report **exact p-values (three digits), standard errors, and effect sizes** in AMA number style, and add the supporting exhibit (main text or Web Appendix).
- For **substance** points: sharpen the contribution sentences (see `jmr-contribution-framing`); if a new study is needed to establish the mechanism or generalizability, run it and report it.
- Where you **disagree**, do so respectfully with evidence — JMR reviewers are domain experts; a reasoned, data-backed pushback is acceptable when the editor's framing allows.
- Reconcile **conflicting** reviewer requests openly: explain the trade-off and the choice, and let the editor adjudicate.

## Keep conformance intact

- Re-check the **50-page limit** after additions; move overflow to the Web Appendix.
- Keep the Web Appendix a **single PDF** with **'W'-prefixed** exhibits; update the **Data Availability Statement** and **AI disclosure** if methods changed.
- Maintain double-anonymization in the revised manuscript and response letter.

## Anti-patterns

- A response letter written before the manuscript is actually revised.
- Cosmetic replies ("we have addressed this") with no concrete change or location.
- Letting new analyses push the print paper over 50 pages instead of using the Web Appendix.
- Capitulating to a reviewer in a way that breaks identification or over-claims.
- Reporting added results with thresholds/asterisks instead of exact statistics.

## Output format

```text
[Target] JMR
[Decision round] R&R #
[Per-comment plan] bar (rigor/substance) → change → location (main / Table Wx)
[Conflicts] reviewer A vs B → resolution + editor adjudication
[New material] Web Appendix additions; 50-page check
[Conformance] DAS / AI disclosure / anonymization updated
[Next step] resubmit → jmr-review-process
```

## Resources

- [`../../resources/official-source-map.md`](../../resources/official-source-map.md)
- [`../../resources/external_tools.md`](../../resources/external_tools.md)

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 →