Ahr structure and exposition

Skill brycewang-stanford/Awesome-Journal-Skills/American-Historical-Review-Skills/skills/ahr-structure-and-exposition

Use when organizing an American Historical Review (AHR) article so narrative and analysis work together within the roughly 8,000-word target (notes excluded). The AHR prizes articles that tell a story and argue a point at once. Shapes structure and flow; it does not generate the underlying argument or evidence.From its SKILL.md

Install

npx -y skills add brycewang-stanford/Awesome-Journal-Skills --skill ahr-structure-and-exposition

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

SKILL.md

3.3 KB, 664 tokens by cl100k_base, as published. Nobody here has run it

Structure & Exposition (ahr-structure-and-exposition)

An AHR article must tell a story and make an argument at the same time, within roughly 8,000 words of text (notes, tables, and charts excluded — verify the current figure). This skill is about architecture: where the thesis sits, how chronology and analysis interleave, and how to keep a long historical argument legible.

When to trigger

Outlining the article or reorganizing a draft that "wanders"
The narrative and the argument feel like two separate papers
Over the word target and unsure what to cut
A reader said the structure is "hard to follow" or "front-loaded with background"

Architecture of an AHR article

Open with the stakes, not the background. A vivid entry point (an episode, a document, a puzzle) that quickly states the question, the argument, and why it matters across fields.
Place the historiographical intervention early. The reader should know what you are revising before the evidence arrives (see ahr-historiography-positioning).
Interleave narrative and analysis. Use chronology to carry the argument; pause to interpret at the moments that bear the claim. Avoid a long context dump followed by a separate "analysis."
Signpost the moves. Section breaks and transitions should track the steps of the argument, not merely the passage of time.
Let evidence breathe but earn its space. Quote and narrate enough to convince; cut color that does not advance the claim.
Close on significance. End by returning to the stakes — what historians elsewhere should take from this — not with a flat summary.

Fitting the ~8,000-word target (notes excluded)

Move exhaustive background and tangents into notes (the AHR's note apparatus is substantial, guideline ~2:1 text-to-notes).
Cut redundant examples; one well-read document beats three that make the same point.
Resist the urge to narrate everything you found — the archive is larger than the article.

Anti-patterns

A long "background" section before any argument appears
Narrative and analysis quarantined into separate halves
Section headings that mark only time, not the argument's progress
Padding the text with material that belongs in the notes
A conclusion that summarizes rather than re-states the stakes

Output format

【Opening】the stakes/entry point (not background)
【Intervention placed early?】[Y/N]
【Structure】section map — narrative + analysis interleaved
【Word target】~8,000 words of text (notes excluded) — over/under?
【Conclusion】returns to general significance? [Y/N]
【Next】ahr-writing-style

Supplementary resources

../../resources/external_tools.md — drafting and outlining tools
../../resources/official-source-map.md — AHR word target and text-to-notes guideline

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.