Individual skill

expecon-writing-style

Use when the prose of an Experimental Economics (ExpEcon) manuscript buries the design or the result, or when the intro/abstract do not land for an experimentalist reader. Polishes structure and voice; it does not change the analysis.

Experimental-Economics-Skills/skills/expecon-writing-style/SKILL.md

Read pinned source

Source commit 932eb23331721b16e967c59f093781be1928b498

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Network or broad shell
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,405
Repository last updated
Sep 27, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Writing Style (expecon-writing-style)

## When to trigger

- The abstract names a topic but never states the treatment contrast or the headline effect
- A reader reaches the results before understanding *what subjects actually did*
- The design is described as scattered implementation notes instead of a clean procedure section
- The intro reads like a JEBO behavioral essay or a GEB theory paper rather than an experimental-methods paper

## Structure: the design is the narrative

ExpEcon papers have a near-canonical, **design-forward** shape. Honor it; referees read for it.

1. **Abstract (the contract).** Within a few sentences: the question, the **treatment contrast**, the **incentivized design** in one clause, the **headline effect with a number and direction**, and the takeaway. "We run a lab experiment in which [contrast]; [outcome] is X% higher under [T] (p=…); this adjudicates between [model A] and [model B]."
Back to top