aaai-artifact-evaluati…
Use when packaging AAAI code, data, multimedia appendices, technical appendices, reproducibility evidence, and post-acceptance…
Use when an AEJ: Economic Policy decision letter (R&R or reject-and-resubmit) has arrived and a response-letter strategy and revision plan are needed. Structures the response to referees and editor with policy-relevance front and center; it does not run new estimation or
Claude Code
$ npx -y skills add brycewang-stanford/Awesome-Journal-Skills --skill aejpol-rebuttal --agent claude-code
Codex
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill aejpol-rebuttal -a codex -y
Cursor
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill aejpol-rebuttal -a cursor -y
Gemini CLI
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill aejpol-rebuttal -a gemini-cli -y
GitHub Copilot
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill aejpol-rebuttal -a github-copilot -y
OpenCode
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill aejpol-rebuttal -a opencode -y
Windsurf
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill aejpol-rebuttal -a windsurf -y
name: aejpol-rebuttal description: Use when an AEJ: Economic Policy decision letter (R&R or reject-and-resubmit) has arrived and a response-letter strategy and revision plan are needed. Structures the response to referees and editor with policy-relevance front and center; it does not run new estimation or redesign identification from scratch.
The editor's letter is the contract — **prioritize what the editor emphasizes**, then address every referee point. At AEJ: Policy the recurring high-stakes asks are about (a) the **credibility of the causal claim**, (b) the **welfare / policy reading**, and (c) **robustness and reproducibility**. Treat the response as a chance to make the policy contribution *more* prominent, not just to patch holes.
1. **Editor-first summary.** Open the letter with a short paragraph naming the 2–3 changes that address the editor's main concerns, and how the paper is now a stronger *policy* contribution. 2. **Point-by-point, per referee.** Quote each comment; respond with what you changed, where (section/table/figure), and the result. Concede where the referee is right; defend with evidence where they are not — politely and with a specific exhibit. 3. **A "what's new" map.** A table mapping each major comment to the revision so the editor can verify coverage at a glance.
Respectful, specific, evidence-led. Every "we agree" is followed by a concrete change; every "we respectfully disagree" is followed by an exhibit or a citation. Keep claims calibrated — over-defending invites a second round.
For each referee point, write three short moves so the editor can verify coverage quickly: 1. **Restate** the comment in one neutral sentence (quote the key phrase). 2. **Act** — "We agree and have [change], now in [Section/Table/Figure]," or "We respectfully disagree; [exhibit/citation] shows [evidence]." 3. **Point** — name the exact location in the revised manuscript where the change lives.
Keep the agree:disagree ratio honest — concede the genuine points fully and reserve disagreement for places where you have a concrete exhibit. A letter that disagrees with everything reads as defensive and invites a second round.
An R&R on a transfer-program paper: the editor stresses "the welfare interpretation is not convincing"; Referee 1 doubts parallel trends; Referee 2 wants external validity. Plan: (1) letter opens with the new MVPF derivation answering the editor; (2) R1 → add honest-DID bounds and flat leads to Section 4, cite in the letter; (3) R2 → add heterogeneity by state characteristics and a scope paragraph. A comment→revision table closes the letter. The contribution reads as a sharper policy answer than the original.
【Editor's main concern】+ the 2–3 changes that address it (letter opener) 【Per-referee responses】[comment → change → location → result] 【Concede vs. defend】list, each with its evidence 【Welfare/policy strengthening】what was added (not just caveated) 【Reproducibility】package + restricted-data path confirmed? [Y/N] 【Comment→revision map】attached? [Y/N] 【Next step】resubmit via AEA system
Stanford REAP × CoPaper.AI · 由斯坦福实证方法论团队精选与维护 访问 copaper.ai 微信:CoPaper.AI 按 11 个主流学科板块覆盖 经管与商科 社会科学 人文学科 数学与物理科学 生命科学 医学与健康 工程与技术 计算机科学与 AI 体育科学 点击任一学科名可跳转到对应说明;每类下的代表子领域在正文总览中完整列出。下方封面墙按 venue 导航,完整分类见覆盖一览。 🧭 布局指南 · 📚 Skill Pack 一览 · ⚡ 如何使用 · 🧪 自动实证
Use when packaging AAAI code, data, multimedia appendices, technical appendices, reproducibility evidence, and post-acceptance…
Use when drafting an AAAI author response (rebuttal) under the single short character-limited author-feedback window, the no-URL…
Use when preparing an accepted AAAI paper for camera-ready source submission to AAAI Press, including proceedings page limits,…
Use when designing or auditing AAAI experiments for the broad-AI program committee, including baselines, ablations, statistical…
Use when positioning an AAAI paper's novelty against archival work, contemporaneous arXiv or workshop papers, and…
Use when strengthening an AAAI paper's reproducibility checklist (placed after references), experimental traceability, seed and…
Activates when the user asks about AI prompts, needs prompt templates, wants to search for prompts, or mentions prompts.chat. Use…
AI-driven presentation workflow for generating editable PPTX decks and slides, reconstructing page visuals, creating reusable…
Use this skill when the user wants a .pptx with smooth cross-slide animation — PowerPoint Morph transitions, Keynote-style…
Create stunning, animation-rich HTML presentations from scratch or by converting PowerPoint files. Use when the user wants to…