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

Mksc Rebuttal

ASecurity

Use when drafting the revision and response letter after a Marketing Science revise-and-resubmit — structuring point-by-point responses to the Senior/Associate Editor and reviewers across a multi-round process, especially on assumptions, identification, counterfactuals, computation, and replication. Drafts the response after revising; it does not interpret the decision (mksc-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 mksc-rebuttal --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Mksc Rebuttal?

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

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

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

Download with Pro
Files
SKILL.md
---
name: mksc-rebuttal
description: Use when drafting the revision and response letter after a Marketing Science revise-and-resubmit — structuring point-by-point responses to the Senior/Associate Editor and reviewers across a multi-round process, especially on assumptions, identification, counterfactuals, computation, and replication. Drafts the response after revising; it does not interpret the decision (mksc-review-process).
---

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

## When to trigger

- You received an MKSC R&R and have planned the revision (via `mksc-review-process`)
- You have actually made (or scoped) the manuscript and code changes and need to write the response
- You must reconcile conflicting reviewer demands for the AE
- A later-round decision asks you to defend or extend prior changes

> Write the response **after** revising the manuscript and re-running the analysis — it documents changes, not promises. The process is developmental and typically multi-round; resubmit the revised manuscript, response document, and updated replication materials through ScholarOne (mc.manuscriptcentral.com/mksc), keeping the same handling team where possible and the manuscript blinded.

## Response-document structure

1. **Opening letter to the Senior/Associate Editor.** Thank the team; summarize the most important changes in 2–4 sentences; explicitly address the AE's prioritized concerns. Note where reviewers conflicted and how you resolved it. (The cover letter/response is seen by the Editor/AE; keep the manuscript anonymized.)
2. **Per-reviewer sections.** Restate every comment (numbered/faithfully), then respond.
3. **Point-by-point format**: **Comment** → **Response** (what you did and the modeling/econometric reasoning) → **Location** (section/table). Quote new manuscript text where helpful.

## Responding to MKSC's signature demands

- **"Identification is not credible."** Add the explicit identification argument, stronger/alternative instruments, a sensitivity-of-estimates analysis, or a Monte Carlo recovering known parameters — and explain why it resolves the concern (see `mksc-data-analysis`).
- **"The model is too restrictive / an assumption drives the result."** Relax the assumption and re-estimate, or show the result is robust to it; report the new comparative static/counterfactual.
- **"The counterfactual is not valid."** Re-solve allowing firms to re-optimize, report magnitudes with uncertainty, and bound the scope of validity.
- **"Computation / multiple equilibria."** Report solver settings, convergence, multiple starting values, and how multiplicity is handled.
- **"Replication."** Update the data-and-code package; confirm the master script reproduces every revised table/figure/counterfactual.
- **Adding analysis vs. length.** Heavy new derivations or robustness usually live in the **online appendix**; for a **Frontiers** paper, the 6,000-word total cap still binds, so move detail online.

## Tone and tactics

- Be respectful and substantive; concede gracefully and make the change.
- Disagree with evidence (an alternative estimation, a robustness result), not assertion.
- Address every point; silent omissions read as evasion.
- Surface reviewer conflicts to the AE with your chosen resolution.

## Checklist

- [ ] Manuscript and code actually revised before the letter was written
- [ ] AE's prioritized concerns addressed first and explicitly
- [ ] Every reviewer comment restated and answered, with locations
- [ ] Identification / assumption / counterfactual demands met with real re-analysis
- [ ] Computation and replication-package updates documented
- [ ] Declined requests justified with evidence and an alternative test
- [ ] Manuscript stays blinded; length/Frontiers cap respected

## Anti-patterns

- Writing the response before re-running the analysis.
- Answering "deepen identification" by adding citations instead of re-estimating.
- A counterfactual left unchanged when firm re-optimization was the objection.
- Skipping an inconvenient comment or de-blinding the manuscript.

## Output format

```
【Round】1st R&R / 2nd / ...
【AE priorities addressed】1... 2... 3...
【Per-reviewer coverage】R1 x/x, R2 x/x, R3 x/x — all answered?
【Major changes】model/identification: ... counterfactual: ... computation: ...
【Replication】updated package reproduces revised exhibits?
【Declined + justification】...
【Status】drafted / final → resubmit via ScholarOne
【Next step】on next decision → mksc-review-process
```

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 →