aejmic-robustness
Use when extensions, edge cases, or applied robustness checks are missing for an American Economic Journal: Microeconomics (AEJ: Micro) manuscript — covering theory extensions (relaxed assumptions, alternative concepts, perturbations) and applied/experimental robustness. Decides which extensions earn their place; it does not prove the main result (see aejmic-theory-model).
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill aejmic-robustness --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Robustness, Extensions & Edge Cases (aejmic-robustness) ## When to trigger - The main result is proved but referees will ask "does it survive [relaxation]?" - You have many possible extensions and must decide which belong in the paper - A knife-edge or boundary case is unaddressed - (Applied) The empirical/experimental result needs a robustness battery ## What robustness means at AEJ: Micro For
What does the aejmic-robustness skill do?
Use when extensions, edge cases, or applied robustness checks are missing for an American Economic Journal: Microeconomics (AEJ: Micro) manuscript — covering theory extensions (relaxed assumptions, alternative concepts, perturbations) and applied/experimental robustness. Decides which extensions earn their place; it does not prove the main result (see aejmic-theory-model).
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill aejmic-robustness --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From brycewang-stanford/Awesome-Journal-Skills, a repository with 909 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.