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

Jm Rebuttal

ASecurity

Use when planning a revision and drafting the point-by-point response letter for a Journal of Marketing (JM) R&R — prioritizing the Coeditor's decisive concerns, strengthening substantive novelty and managerial relevance, and keeping the double-anonymized rules. Plans and drafts the response; it does not interpret the original decision (jm-review-process).

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

Works with

cli

Security Analysis

A100/100

Scanned 6/5/2026

Install to Claude Code

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

Installs into .claude/skills of the current project.

Are you the author of Jm Rebuttal?

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

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

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

Download with Pro
Files
SKILL.md
---
name: jm-rebuttal
description: Use when planning a revision and drafting the point-by-point response letter for a Journal of Marketing (JM) R&R — prioritizing the Coeditor's decisive concerns, strengthening substantive novelty and managerial relevance, and keeping the double-anonymized rules. Plans and drafts the response; it does not interpret the original decision (jm-review-process).
---

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

## When to trigger

- You received a JM major/minor revision and need a plan and a response letter
- A reviewer challenged the **substantive contribution**, **relevance**, or **identification**
- You must revise *before* writing the response (do not draft the letter on an unrevised paper)
- A subsequent round arrived and you need to show movement since the last revision

## Sequence: revise first, then respond

JM R&Rs are developmental and often multi-round. Revise the manuscript first; the response letter documents changes that already exist. Lead the work with the **Coeditor's decisive concerns** — at JM these almost always include the two gatekeeping bars: **substantive novelty** (compelling new insight, not a new-context replication) and **managerial/policy/societal relevance**. A revision that polishes peripheral points but leaves a gatekeeping concern unaddressed will not advance.

## Build the response letter

- **Open** with a brief summary of the most important changes and how the paper is stronger on JM's substantive-and-relevance bar.
- **Point-by-point**: restate each comment, then state the change, with **page/line or section pointers** to the revised manuscript (remember: no line numbers in the file — cite sections/pages or quote the revised text).
- **Quote new text** inline so the editor sees the change without hunting.
- **Stay anonymized**: no author-revealing language anywhere in the letter or revised files; keep any preregistration links anonymized.
- **Be candid on disagreements**: where you decline a suggestion, explain respectfully with evidence; do not silently ignore a comment.

## Address JM-specific concerns head-on

- **"Incremental / new-context"** → strengthen and foreground the new mechanism, reversal, boundary condition, or decisive magnitude; revise the contribution sentences (see `jm-contribution-framing`).
- **"So what for practice?"** → add or sharpen the managerial/policy/societal implications, quantified in real units (lift, CLV, WTP, welfare).
- **"Identification is weak"** → add the design-appropriate fix (better instrument, parallel-trends evidence, additional experiment, robustness/placebo tests) per `jm-data-analysis`.
- **"Significance without magnitude"** → ensure exact p-values, SEs, and **effect sizes** are reported throughout, in managerial units where possible.
- **Scope challenge** (too methods-y / too general-management) → re-center the paper on the substantive marketing question and its real-world stakes.

## Prepare transparency deliverables

If the revision is heading toward conditional acceptance, line up the **JM Dataverse** replication packet (data + analysis scripts, or qualitative materials), confirm the **Data Availability Statement**, and prepare preregistration links and the attestation. Doing this during the R&R avoids a scramble at acceptance.

## Checklist

- [ ] Manuscript revised before the letter was drafted
- [ ] Coeditor's decisive concerns addressed first
- [ ] Substantive-novelty and managerial-relevance challenges answered explicitly
- [ ] Point-by-point letter with section/page pointers and quoted new text
- [ ] Exact p-values, SEs, effect sizes verified throughout after revision
- [ ] Identification/robustness additions completed where requested
- [ ] Anonymization preserved in letter and files (incl. prereg links)
- [ ] Replication packet / Data Availability Statement prepared if nearing acceptance

## Anti-patterns

- **Letter before revision** — promising changes not yet made.
- **Cosmetic edits** to a gatekeeping (novelty/relevance) concern.
- **Defensive non-answers** that dodge a reviewer's point.
- **Reintroducing identity** in the response or revised files.
- **Over-claiming** new results beyond what the added analysis supports.

## Output format

```
【Revision done first】yes/no
【Coeditor decisive concerns addressed】[...]
【Novelty + relevance answers】[...]
【Identification/robustness additions】[...]
【Exact-statistic check】p / SE / effect size verified post-revision?
【Letter】point-by-point with pointers + quoted text drafted?
【Anonymization】preserved (incl. prereg links)?
【Transparency】JM Dataverse + DAS readiness if nearing acceptance: [...]
【Next step】resubmit via ScholarOne → jm-review-process for the next round
```

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 →