Agent skill · Code Review & Quality

aeri-writing-style

Use when revising an American Economic Review: Insights (AER: Insights) short-format manuscript to lead with the result, fit the hard word cap (7,000 words minus 200 per exhibit), and write the ≤100-word abstract. Enforces the length budget and the lead-with-the-result arc; it does not change the analysis.

brycew6m878★ · +32/wk · 1 repos on radarProfile →
claude-codeMIT
Install
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill aeri-writing-style --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 4 KB
Bundled scripts: none
Path: AER-Insights-Skills/skills/aeri-writing-style/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 909 · +31 this week
Language: Stata
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Writing Style — Lead With the Result, Fit the Cap (aeri-writing-style) ## When to trigger - The intro buries the headline result under setup, literature, or methods - The draft is over the word cap and needs cutting, not just polishing - The abstract exceeds 100 words or does not state the result - Late-stage polish once identification, robustness, and exhibits have settled ## The two hard constraints (检索于 2026-06;以官网为准) - **Word cap:** main text **≤7,000 words with no exhibits; each exhibit subtracts 200 words; ≤5 exhibits** (so ≥6,000 at the cap). The count includes body, footnotes, endnotes, and in-paper appendices; it **excludes** title, authors, abstract, acknowledgement footnote, references, exhibits, and the Supplemental Appendix. **Over the cap = returned unreviewed.** - **Abstract: ≤100 words.** It must state the result, not promise it. Treat the cap as a design constraint from the first draft, not a final trim. Every sentence competes with the insight for space. ## The AER: Insights arc (lead with the result) Unlike a long paper that builds to its result, an AER: Insights paper **states the answer in the first paragraph**: 1. **Sentence 1–2:** the question and the **hea

What's inside
Steps it walks through
  1. When to trigger
  2. The two hard constraints (检索于 2026-06;以官网为准)
  3. The AER: Insights arc (lead with the result)
  4. Cutting to the cap (in priority order)
  5. Writing the ≤100-word abstract
  6. Checklist
  7. Anti-patterns
  8. Output format
More from Awesome-Journal-Skills
All skills →
About this skill
What does the aeri-writing-style skill do?

Use when revising an American Economic Review: Insights (AER: Insights) short-format manuscript to lead with the result, fit the hard word cap (7,000 words minus 200 per exhibit), and write the ≤100-word abstract. Enforces the length budget and the lead-with-the-result arc; it does not change the analysis.

How do I install it?

Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill aeri-writing-style --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.

Keep going