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

Qe Rebuttal

ASecurity

Use when a Quantitative Economics (QE) decision letter arrives (R&R or major/conditional revision) and a response strategy and letter are needed. Structures the revision and response; it does not redo the analysis (route to the relevant qe-* skill for that).

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

Security Analysis

A100/100

Scanned 6/6/2026

Install to Claude Code

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

Installs into .claude/skills of the current project.

Are you the author of Qe Rebuttal?

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

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

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

Download with Pro
Files
SKILL.md
---
name: qe-rebuttal
description: Use when a Quantitative Economics (QE) decision letter arrives (R&R or major/conditional revision) and a response strategy and letter are needed. Structures the revision and response; it does not redo the analysis (route to the relevant qe-* skill for that).
---

# Rebuttal & Revision (qe-rebuttal)

## When to trigger

- A QE decision letter arrived: revise-and-resubmit, or a conditional/major revision
- You have referee reports and need a response strategy
- You are unsure how to prioritize conflicting referee demands
- The revised manuscript exists and you need to draft the response letter

## QE reality: the coeditor's letter is the contract, and the clock runs ~12 months

At QE a **handling coeditor** owns the decision and synthesizes the referees (often including an Associate Editor). The **coeditor's letter ranks the issues** — it tells you which referee points are binding and which are optional; read it first and let it set priorities. **Revise offers are normally valid for 12 months**, so plan the analysis, estimation, and reproducibility work against that window rather than rushing a thin resubmission. Because QE is the empirical/quantitative ES journal, expect referees to probe **identification, estimation, robustness, and reproducibility** specifically — keep the public-posting and replication obligations in view as you revise.

## Triage protocol

1. **Decode the coeditor.** A point the coeditor underscores is binding; a point only one referee raised and the coeditor ignored is lower priority (still answer it).
2. **Classify every comment.** Tag each: *fundamental* (must add/redo analysis or estimation), *clarification* (rewrite/explain), or *disagreement* (you will push back, politely, with evidence).
3. **Sequence the work.** Do the analysis first — route fundamentals to `qe-identification-strategy`, `qe-data-analysis`, or `qe-tables-figures`; update the replication package via `qe-replication-and-data-policy`; *then* write the letter.
4. **Settle it with a check, not a fight.** If a robustness check, an added moment, or a Monte Carlo settles the point, run it; reserve disagreement for where the referee is genuinely mistaken.

## Response-letter structure

- **Opening:** thank the coeditor and referees; summarize the main changes in a short paragraph.
- **Point-by-point:** quote each comment, then respond — what you did + where in the revised paper it now appears (section/table/figure/page).
- **Disagreements:** state the referee's point fairly, then give the evidence-based reason you respectfully differ; offer a compromise (e.g., add to the Supplemental Appendix, ≤25 pages) where possible.
- **Reproducibility:** note any changes to data/code so the eventual ES Data Editor check stays clean.
- **Tone:** gracious, concrete, never defensive.

## Checklist

- [ ] Coeditor's priorities decoded and used to rank responses
- [ ] Every referee comment classified (fundamental / clarification / disagreement)
- [ ] All fundamental requests resolved with actual new analysis/estimation, not promises
- [ ] Each response cites the exact location of the change in the revised paper
- [ ] Disagreements are evidence-based, fair, and offer a compromise
- [ ] Replication package and public posting updated to match the revision
- [ ] Revised manuscript updated *before* the letter was written
- [ ] No significance asterisks reintroduced; no new over-claiming

## Anti-patterns

- Writing the response letter before the manuscript reflects the changes
- Promising future work instead of doing the analysis within the ~12-month window
- Arguing where an added moment / robustness check / Monte Carlo would settle it
- Letting the replication package drift out of sync with the revised results
- Defensive or curt tone; treating reports as attacks rather than help

## Output format

```
【Decision】R&R / major / conditional
【Coeditor's binding points】[...]
【Comment classification】fundamental: [...] / clarification: [...] / disagreement: [...]
【Analysis routed to】qe-identification-strategy / qe-data-analysis / qe-tables-figures
【Letter status】point-by-point with locations? [Y/N]
【Reproducibility synced】package + posting updated? [Y/N]
【Next step】resubmit via the ES portal (qe-submission for file checks)
```

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', ...

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 →