Individual skill
rfs-writing-style
Use as a late-stage polish when prose, contribution framing, or the abstract/introduction is the bottleneck for a The Review of Financial Studies (RFS) manuscript. Sharpens exposition; does NOT change the empirics, identification, or results.
Review-of-Financial-Studies-Skills/skills/rfs-writing-style/SKILL.md
Source commit 932eb23331721b16e967c59f093781be1928b498
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 9, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 1,410
- Repository last updated
- Sep 27, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- academic-writing Repository topic
- agent-skills Repository topic
- journal Repository topic
- academic-research Repository topic
- ai-agents Repository topic
- anthropic Repository topic
- awesome-list Repository topic
- claude Repository topic
- claude-code Repository topic
- economics Repository topic
- writing Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Read excerpt
# Writing & Contribution Framing (rfs-writing-style)
## When to trigger
- The abstract or introduction buries what is new
- Prose is dense, over-hedged, or jargon-heavy
- The contribution is implied but never stated as a crisp claim
- The paper is technically done and needs a final exposition pass
> Run this only after identification, robustness, and exhibits hold up. Do not polish prose around an unsettled result.
## How RFS papers read
The best RFS papers make the **new question and the answer legible in the first two pages**. An RFS Editor desk-screens before referees, so the contribution must land before page three or risk a desk reject. RFS welcomes theory + empirics, so the prose must integrate them, not present a model and then an unrelated regression — Brunnermeier and Pedersen (2009, RFS 22(6)) is a model of a tight theory→prediction→evidence arc. Two hard RFS house-style rules bind the writing: the **abstract must be ≤ 100 words** (RFS returns longer abstracts), and references follow **Chicago Manual of Style author-date** format. A long, literature-first abstract is both off-house-style and over the word limit.