SkillAgentSearch skills...

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.

Install / Use

npx skills add brycewang-stanford/Awesome-Journal-Skills --skill aeri-writing-style

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

85/100

Supported Platforms

Universal

Our assessment of aeri-writing-style

aeri-writing-style scores 85/100 on our quality scale, 811th of 1,156 Content & Media skills we index.

Its SKILL.md is 4.2 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 aeri-writing-style 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.

aeri-writing-style compared with similar skills

All 4 of these similar skills score higher than aeri-writing-style; compare them before choosing.

SkillScoreStarsUpdatedFormat
aeri-writing-style (this skill)by brycewang-stanford851.2k2mo agoSKILL.md
siyuanby siyuan-note10047.3ktodayMCP Server
x402by browser-use100121.0k4d agoSKILL.md
algorithmic-artby anthropics100177.9k56d agoSKILL.md
pptxby anthropics100177.9k56d agoSKILL.md

Frequently asked questions

How do I install aeri-writing-style?
Run npx skills add brycewang-stanford/Awesome-Journal-Skills --skill aeri-writing-style. The install tabs above show the steps for each supported agent.
Which AI agents does aeri-writing-style 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 aeri-writing-style 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 aeri-writing-style still maintained?
The repository was last updated about 2 months ago, so aeri-writing-style is actively maintained.

name: aeri-writing-style description: 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.

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 headline result with its magnitude and uncertainty (estimate + SE / confidence set), no asterisks.
  2. Sentence 3–4: why it matters / the prior it overturns (the surprise).
  3. One short paragraph: how it is identified (the design or the model's key restriction), in plain terms.
  4. One sentence: the single most important robustness/scope caveat, with a pointer to the appendix.
  5. Brief roadmap or none — the paper is short enough that heavy signposting wastes words.

The body then delivers exactly that arc: setup (tight), identification, result, the one or two checks, a short discussion. No second result, no survey, no extended derivations in-text.

Cutting to the cap (in priority order)

  1. Cut secondary results to the Supplemental Appendix (aeri-robustness).
  2. Compress the literature to one or two paragraphs (aeri-literature-positioning).
  3. Move proofs/derivations and estimation detail to the appendix (aeri-theory-model).
  4. Delete throat-clearing ("It is well known that…", over-signposted roadmaps).
  5. Merge exhibits to reclaim 200 words each (aeri-tables-figures).
  6. Tighten prose last — shorter sentences, fewer hedges, active voice.

Writing the ≤100-word abstract

  • State the result with its magnitude, the setting, and the identification in one breath.
  • No literature, no "we examine"; say what you found.
  • Verify the count; 100 words is a hard ceiling.

Checklist

  • [ ] First paragraph states the headline result with magnitude + SE/CI (no asterisks)
  • [ ] Main text under 7,000 − 200×(#exhibits) words (counted per AEA scope rules)
  • [ ] Abstract ≤100 words and states the result
  • [ ] One idea only in-text; secondary material in the Supplemental Appendix
  • [ ] Literature compressed to ≤2 paragraphs; no in-text survey
  • [ ] No significance asterisks/boldface anywhere
  • [ ] Roadmap minimal or absent; throat-clearing removed

Anti-patterns

  • A long build-up that reveals the result only in Section 4
  • Trimming prose while leaving a second result in-text (cut the result first)
  • An abstract over 100 words, or one that promises rather than reports
  • Counting the word budget only at the end and discovering you are 2,000 over
  • AER-length signposting in a short paper

Output format

【First paragraph】states result + magnitude + SE/CI? [Y/N]
【Word count】main text = __ ; cap = 7000 − 200×__ = __ ; under? [Y/N]
【Abstract】__ words (≤100?) and states the result? [Y/N]
【Cut list to hit cap】<secondary results / lit / proofs / exhibits merged>
【No-asterisk check】[Y/N]
【Next step】aeri-replication-package

Related Skills

View on GitHub
GitHub Stars1.2k
CategoryContent
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