SkillAgentSearch skills...

aeja-rebuttal

Use when an American Economic Journal: Applied Economics (AEJ: Applied) decision letter arrives (R&R or conditional accept) and a response-to-referees letter plus a revision plan must be drafted.

Install / Use

npx skills add brycewang-stanford/Awesome-Journal-Skills --skill aeja-rebuttal

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

85/100

Supported Platforms

Universal

Tags

Our assessment of aeja-rebuttal

aeja-rebuttal scores 85/100 on our quality scale, 2673rd of 4,702 Development & Engineering skills we index.

Its SKILL.md is 4.8 KB long, well organised into 9 sections with 1 code example: a solid amount of guidance for an agent.

With 1,158 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
26/30
Structure
17/20
Description
15/15
Adoption
13/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 2 months ago, so aeja-rebuttal is actively maintained.
  • Our last check on 2026-11-05 found the source still online.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-10-04. Automated pattern scan on 2026-10-04. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

aeja-rebuttal compared with similar skills

All 4 of these similar skills score higher than aeja-rebuttal; compare them before choosing.

SkillScoreStarsUpdatedFormat
aeja-rebuttal (this skill)by brycewang-stanford851.2k2mo agoSKILL.md
taste-skillby Leonxlnx100117.6k9d agoCLAUDE.md
ai-job-searchby ai-job-search-dev10072.3ktodayCLAUDE.md
claude-howtoby luongnv8910047.4k3d agoCLAUDE.md
lobehubby lobehub10085.7ktodayMCP Server

Frequently asked questions

How do I install aeja-rebuttal?
Run npx skills add brycewang-stanford/Awesome-Journal-Skills --skill aeja-rebuttal. The install tabs above show the steps for each supported agent.
Which AI agents does aeja-rebuttal work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is aeja-rebuttal safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is aeja-rebuttal still maintained?
The repository was last updated about 2 months ago, so aeja-rebuttal is actively maintained.

name: aeja-rebuttal description: Use when an American Economic Journal: Applied Economics (AEJ: Applied) decision letter arrives (R&R or conditional accept) and a response-to-referees letter plus a revision plan must be drafted. Plans and structures the response; it does not run the new analysis (aeja-identification / aeja-robustness) or the submission preflight.

Rebuttal & Response Letter (aeja-rebuttal)

When to trigger

  • An AEJ: Applied R&R or conditional acceptance decision letter has arrived
  • You need to triage referee comments into must-do / argue / defer
  • You are drafting the response-to-referees document and revision plan
  • A reject-and-resubmit invitation needs a strategy before re-engaging

How to read an AEJ: Applied decision

The editor's letter is the priority signal: it tells you which referee concerns are binding and which are optional. At AEJ: Applied the binding asks are almost always about design credibility (the identification, robustness, inference) before exposition. Address the editor's stated priorities first and in full; treat the referee reports as the menu the editor has already filtered. A revision is judged on whether the identification concerns are genuinely resolved, not on volume of new tables.

Response-letter structure

  1. Opening summary — thank the editor/referees; state the 3–5 substantive changes that define the revision (lead with the identification/robustness changes).
  2. Point-by-point — quote each comment, then respond with: what you did, where in the paper (section/table/page), and the result. Use a consistent format per point.
  3. Tone — gracious, concrete, non-defensive. Concede valid points fully; where you disagree, argue with evidence, not assertion.
  4. Triage discipline — every comment gets one of: done (changed + located), partially done (with reason), or respectfully declined (with an evidence-based argument). No comment is ignored.
  5. Highlight the decisive evidence — if a referee doubted the design, show the new heterogeneity-robust estimate / honest-DID bound / falsification result explicitly and quote the new number with its SE.

Triage table

| Referee ask | Default response | |-------------|------------------| | Core identification doubt (binding per editor) | do it in full; show the new estimate + SE; update the paper | | Robustness/inference request | run it; report stability of the point estimate | | External-validity / estimand | add a calibrated scope statement; do not overclaim | | Additional outcome/subgroup | run with MHT adjustment; or argue why it is out of scope | | Exposition / framing | revise; cheap to do, builds goodwill | | Out-of-scope new paper | respectfully decline with a one-line reason |

Checklist

  • [ ] Editor's stated priorities identified and addressed first, in full
  • [ ] Every referee comment answered: done / partial / declined — none ignored
  • [ ] Each "done" response cites the exact section/table/page and the new result
  • [ ] Decisive identification/robustness evidence quoted with numbers and SEs
  • [ ] Tone gracious and concrete; disagreements argued with evidence
  • [ ] Replication package updated to match the revised exhibits (aeja-replication-package)
  • [ ] A short cover note to the editor summarizing how the binding concerns were resolved

Worked vignette (illustrative)

Referee 2 says the staggered-DID estimate is biased and the parallel-trends story is thin; the editor's letter flags this as the binding concern. A weak response argues that TWFE "should be fine here." The AEJ: Applied response: re-estimate with Callaway–Sant'Anna, report the new ATT of 3.1pp (s.e. 0.9, vs. 3.6pp under TWFE), add the event-study leads and a Goodman-Bacon decomposition, and run an honest-DID bound — then in the letter quote the new number, cite the exact figure/table, and note the conclusion is unchanged but now robust. The editor sees the binding concern fully resolved with evidence, not assertion.

Anti-patterns

  • Answering the referees but ignoring the editor's prioritization
  • Defensive or dismissive tone; arguing by assertion instead of new evidence
  • Claiming a change without saying where in the paper it landed
  • Adding a wall of new tables that dodges the actual identification concern
  • Letting the replication package drift out of sync with the revised paper
  • Silently dropping a comment you found inconvenient

Output format

【Decision type】R&R / conditional accept / reject-and-resubmit
【Editor priorities】[binding asks, in order]
【Triage】done: [...] | partial: [...] | declined (with reason): [...]
【Decisive evidence】new identification/robustness result + number(SE) + location
【Tone check】gracious, concrete, evidence-based? [Y/N]
【Package sync】replication updated to match revision? [Y/N]
【Next step】aeja-submission (resubmit) → re-enter aeja-workflow if further rounds

Related Skills

View on GitHub
GitHub Stars1.2k
CategoryDevelopment
Updated2mo ago
Forks153

Languages

Stata

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions