Agent skill · Documentation

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.

brycew6m878★ · +32/wk · 1 repos on radarProfile →
claude-codeMIT
Install
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill expecon-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: 7 KB
Bundled scripts: none
Path: Experimental-Economics-Skills/skills/expecon-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 (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]." 2. **Introduction.** Motivate, state the precise hypothesis, then say *how the design isolates it* and what is new about that design. The reader should know your treatments before the literature review ends. 3. **Design / Procedures (the load-bearing section).** This is wh

What's inside
Steps it walks through
  1. When to trigger
  2. Structure: the design is the narrative
  3. Voice an ExpEcon referee trusts
  4. Sentence-level habits
  5. Checklist
  6. The Procedures section, line by line
  7. Anti-patterns
  8. Writing the abstract as a contract
  9. Output format
More from Awesome-Journal-Skills
All skills →
About this skill
What does the expecon-writing-style skill do?

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.

How do I install it?

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