Use when turning empirical results into an explicit contribution to accounting knowledge for a Journal of Accounting Research (JAR) manuscript — stating what we now know about how accounting information is produced, disclosed, audited, or used, and why it matters economically. Frames the contribution; it does not run the analysis (jar-data-analysis) or polish prose (jar-writing-style).
Scanned 6/5/2026
Install to Claude Code
npx -y skills add brycewang-stanford/Awesome-Journal-Skills --skill jar-contribution-framing --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Jar Contribution Framing?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/brycewang-stanford-jar-contribution-framing)More formats (shields.io, HTML) on the badges page.
---
name: jar-contribution-framing
description: Use when turning empirical results into an explicit contribution to accounting knowledge for a Journal of Accounting Research (JAR) manuscript — stating what we now know about how accounting information is produced, disclosed, audited, or used, and why it matters economically. Frames the contribution; it does not run the analysis (jar-data-analysis) or polish prose (jar-writing-style).
---
# Contribution Framing (jar-contribution-framing)
## When to trigger
- You have clean, identified results but the "so what for accounting" is thin
- A referee says "the contribution is incremental" or "this confirms what we knew"
- The discussion section restates results without stating what we learned
- You need intro and discussion contribution sentences that survive referees
## What counts as a contribution at JAR
JAR rewards research that changes our understanding of **how accounting information is produced, disclosed, audited, regulated, or used in markets and contracts**. A publishable contribution typically does one of: (a) identifies a previously unestablished **causal** effect of an accounting/disclosure/regulatory feature; (b) **adjudicates** between competing economic theories using a setting that separates them; (c) documents an economically important **mechanism** (not just a reduced-form correlation); or (d) introduces a **new measure or setting** that reopens a literature. The increment must be economically consequential — for investors, analysts, creditors, auditors, standard-setters, or managers — not merely statistically detectable.
## Write the contribution explicitly
- **One contribution sentence.** "We show that [accounting feature] causally affects [outcome] through [mechanism], using [identifying variation]." Put a version in the intro and the discussion.
- **Relative to the closest paper.** State the increment over the 2-3 nearest studies (from jar-literature-positioning), not over a generic gap.
- **Economic magnitude.** Translate the coefficient into something a referee feels (basis points of spread, percentage of a standard deviation, dollars), not just a star.
- **Implications.** Spell out what changes for theory, for empirical accounting practice, and — where relevant — for standard-setters/regulators (a recurring JAR audience).
- **Boundaries.** State the scope conditions and what the design cannot identify; honest limits strengthen credibility.
## Match the framing to the track
For a **Ray Ball JAR Annual Conference** submission the contribution should speak to the year's theme and to a broad accounting audience; for a **Registered Report**, frame the contribution around the *question and design* (since acceptance is outcome-independent), making a well-identified null genuinely informative.
## Checklist
- [ ] A single, explicit contribution sentence appears in both intro and discussion
- [ ] The increment is stated relative to the closest prior papers
- [ ] Economic magnitude is interpreted, not just statistical significance
- [ ] Implications for theory, practice, and (where relevant) regulators are drawn
- [ ] Scope conditions and what the design cannot identify are stated
- [ ] The framing matches the track (regular / conference theme / Registered Report)
## Anti-patterns
- **Restating results** as if description were contribution.
- **"First to study X"** as the contribution (novelty ≠ importance).
- **Significance without magnitude**: stars with no economic interpretation.
- **Overclaiming causality** beyond what the identification supports.
- **Ignoring the nearest paper**, leaving the increment ambiguous.
## Output format
```
【Contribution sentence】one sentence (causal / adjudication / mechanism / new measure)
【Increment vs. closest work】[...]
【Economic magnitude】interpreted (bps / %SD / dollars)
【Implications】theory / empirical practice / standard-setters
【Scope & limits】what the design cannot identify
【Track framing】regular / Ray Ball theme / Registered Report
【Next step】jar-tables-figures or jar-writing-style
```
## Resources
- [`../../resources/official-source-map.md`](../../resources/official-source-map.md) — official JAR/Chicago Booth/Wiley URLs (accessed 2026-06-01)
- [`../../resources/external_tools.md`](../../resources/external_tools.md) — data sources and tooling
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!