Aer Submission logo

Aer Submission

Community
brycewang-stanford
aer-submission

Use when running the final pre-submission audit for an AER, AER:Insights, or AEJ manuscript — length, format, cover letter, per-author disclosure statements, file packaging, and routing among the AEA journal family. Apply immediately before clicking submit.

Overview

Publisherbrycewang-stanford
RepositoryAER-Skills
Skill nameaer-submission
Stars
62
Forks
11
Bundled files
2
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 2 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by brycewang-stanford on GitHub. Read the source before you install it.

Installation

Install the Aer Submission AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/brycewang-stanford/AER-Skills/tree/main/skills/aer-submission
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/brycewang-stanford/AER-Skills.git /tmp/AER-Skills
mkdir -p .claude/skills
cp -r /tmp/AER-Skills/skills/aer-submission .claude/skills/aer-submission
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Aer Submission in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Aer Submission on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Aer Submission is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

AER Submission

Overview

The final submission audit catches the formatting and routing mistakes that produce avoidable desk rejections. AER's editorial office returns submissions for non-compliance with length, format, or policy requirements before the editor sees the paper — a turnaround that can cost weeks.

This skill is the last gate.

When to Use

  • Within 48 hours of submission
  • After every R&R, before resubmission
  • When the user is undecided between AER and AER: Insights as the final target
  • After a rejection elsewhere, when routing into the AEA family

Hard Format Constraints

ItemAERAER: Insights
Abstract length≤ 100 words≤ 100 words
Main text length~40 pages (11-pt, 1.5-spaced, 1" margins)≤ 7,000 words minus 200 per exhibit; ≤ 6,000 with five exhibits
Maximum exhibitsNo formal cap5; each exhibit reduces budget by 200 words
Word-count basisPage guideline includes figures, tables, references, and in-paper appendicesMain body, footnotes, endnotes, and in-paper appendices; excludes references, exhibits, and Supplemental Appendix
File formatSingle PDF for reviewSingle PDF for review
Separate title pageNone — title and byline on page 1Same
Cover letterOptionalOptional
Submission systemScholarOne (mc.manuscriptcentral.com/aer)ScholarOne

Manuscripts exceeding AER: Insights length are returned without review. This is enforced automatically.

Length Audit (AER)

The 40-page guideline counts:

  • Main text
  • Footnotes
  • In-paper tables and figures
  • References
  • In-paper appendix

The 40-page count does not include: title, abstract, supplemental appendix, online appendix.

If over 40 pages: cut, then cut again, then move material to the online appendix. AER editors explicitly state that excessive online-appendix reliance is itself a desk-rejection signal. The supplemental appendix is for additional material, not for the main result.

Length Audit (AER: Insights)

Count main-body words including footnotes, endnotes, and in-paper appendices; exclude title, byline, abstract, acknowledgement footnote, references, exhibits, and Supplemental Appendix. Word-count discipline:

  • One exhibit costs ~200 words
  • Five exhibits leave 6,000 words
  • Zero exhibits leave 7,000 words

If you cannot fit, the paper is an AER (or AEJ) paper, not an AER: Insights paper.

Manuscript Structure

[Title]
[Authors and affiliations]
[Abstract — ≤ 100 words]
[JEL codes]
[Keywords]

[Introductory paragraphs — NO heading "Introduction"]

\section{Data}             (or whatever the next titled section is)
\section{...}
...
\section{Conclusion}

\bibliography{...}

[Tables in numerical order]
[Figures in numerical order]

\appendix
\section{...}              (in-paper appendix only — short)

AER numbers sections with Roman numerals (I., II., III.) and subsections with capital letters (A., B., C.); the introduction is unnumbered. In LaTeX, set \renewcommand{\thesection}{\Roman{section}} or use the AEA sample article class, which applies house style automatically.

Move long appendices to a separate Supplemental Appendix file.

File Package for ScholarOne

Prepare in advance:

  1. Manuscript PDF — single file: text + references + tables + figures + in-paper appendix
  2. Supplemental Appendix PDF — optional, separate file
  3. Cover letter — only if needed (see below); via form field, not separate document
  4. JEL classification codes — primary and secondary
  5. Disclosure Statement PDFs — one separate PDF per coauthor; if nothing to disclose, say that explicitly
  6. Coeditor conflict disclosures — list any coeditor who has a personal or professional conflict
  7. Suggested editor — optional, in form field
  8. AI usage disclosure — required if AI software was used in drafting or editing; brief description

If the paper has supplementary materials (videos, large datasets), provide URLs to a public repository.

Cover Letter — When and How

AER does not require a cover letter. Use one only to communicate substantive information:

  • Conflict of interest with a coeditor (e.g., recent coauthor, advisor, family member). Identify by name.
  • Data access limitations that the editor needs to know in advance (e.g., restricted data with specific replication arrangements).
  • Previous submission history to another AEA journal if relevant.

If you include one, keep it ≤ 200 words and submit via the ScholarOne form field, not as a separate uploaded document.

Do not use the cover letter to:

  • Pitch the paper's contribution (the abstract does that)
  • List the seminars where the paper was presented (the title-page footnote does that)
  • Argue against potential referees (this is counterproductive)

Routing Decision: AER vs. AER: Insights vs. AEJ

Run this decision tree before submission:

Is the contribution sharp enough to fit the AER: Insights word/exhibit formula?
├── Yes → Is it cross-subfield interest?
│   ├── Yes → AER: Insights
│   └── No → AEJ: Applied / Policy / Macro / Micro (by subfield)
└── No → Does it have broad cross-subfield interest?
    ├── Yes → AER
    └── No → AEJ (most fitting)

Common mistakes:

  • Submitting a long-form paper to Insights "in case." Insights requires brevity by design, not by truncation.
  • Submitting to AER when the contribution is solidly within one subfield. AEJ acceptance is faster, cheaper, and similar in audience for many topics.
  • Treating the AEJ family as a fallback after AER rejection. The clock resets; conditional probability of acceptance is unchanged. Submit where the paper actually fits.

Submission Fees

AER charges a submission fee that scales with AEA membership status and country income group. Authors from low- and middle-income countries pay reduced or waived fees. Verify current fee schedule on the AEA submissions page before the corresponding author finalizes the form.

Final Preflight Checklist

  • aer-consistency audit reports all-pass on the final PDF's source
  • aer-referee-sim verdict is at least major R&R on a fresh run
  • Abstract ≤ 100 words (run a word count, not a glance)
  • Main text within length limit (≤ 40 pages for AER; word-count for Insights)
  • No "Introduction" heading; introductory material starts on page 1 after title
  • All tables use booktabs rules; captions positioned correctly
  • All figures are vector (PDF / EPS); each has a notes block
  • References complete; in-text citations match bibliography
  • JEL codes selected (primary + secondary)
  • Disclosure Statement PDF prepared for each coauthor
  • Coeditor conflicts disclosed
  • AI usage disclosed if applicable
  • Replication package deposit started (not required at submission but plan it now)
  • If field experiment: AEA RCT Registry entry exists and is referenced
  • Author contributions and acknowledgements present in the title-page footnote
  • No tracked changes, no comments, no draft watermarks in the PDF
  • Single self-contained PDF; supplemental appendix as separate file
  • Corresponding author email and ORCID up to date

Repository Resources

Bundled with the installed skill, no repository checkout needed --- read it before the repo resources below:

  • references/final-audit-checklist.md --- desk-rejection no-go audit, length accounting, portal checklist

When working from the AER-skills repository or plugin bundle, load only the relevant resource:

  • Submission no-go checklist: docs/desk-rejection-audit.md
  • Current policy source register: docs/source-register.md
  • Replication planning surface: skills/aer-replication/SKILL.md
  • Deposit-ready scaffold: examples/replication-package-skeleton/

After Submission

  • Expect 8-12 weeks to first decision for AER (median); shorter for Insights
  • Desk rejection: typically within 2-4 weeks
  • A "reject and resubmit" (rare) signals interest but requires substantial restructuring
  • Track via ScholarOne; do not email the editorial office for status before 12 weeks

Handoff

text
TARGET VENUE: <AER | AER:Insights | AEJ:...>
LENGTH AUDIT: <pass / fail with details>
FORMAT AUDIT: <pass / fail with details>
COVER LETTER: <none / drafted, <n> words>
DISCLOSURE STATEMENTS: <complete / missing>
CONFLICTS DISCLOSED: <list / none>
REPLICATION DEPOSIT STATUS: <planned / drafted / complete>
READY TO SUBMIT: <yes / no — with blockers>
NEXT SKILL: <none — submit | aer-rebuttal once decision arrives>

Anti-Patterns

  • Submitting a manuscript whose abstract is 108 words "but should be fine"
  • Including a 600-word cover letter that pitches the paper
  • Uploading the LaTeX source as the review PDF
  • Listing JEL codes that do not match the paper's content
  • Submitting an Insights paper at 7,800 words because it has only two exhibits — the formula gives ≤ 6,600
  • Holding the replication deposit until "after acceptance" — the Data Editor delay is now part of the publication timeline

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Aer Submission AI skill do?

Use when running the final pre-submission audit for an AER, AER:Insights, or AEJ manuscript — length, format, cover letter, per-author disclosure statements, file packaging, and routing among the AEA journal family. Apply immediately before clicking submit.

Why use Aer Submission on TypingMind?

Because you install it once and use it with any model. Aer Submission is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Aer Submission in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/brycewang-stanford/AER-Skills/tree/main/skills/aer-submission. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Aer Submission?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Aer Submission?

As many as you like. As long as a model supports skills, you can use Aer Submission with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Aer Submission AI skill free?

Yes. It is published on GitHub by brycewang-stanford under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇