revacc-theory-development
Use when the economic mechanism, analytical model, or testable predictions are the bottleneck for a Review of Accounting Studies (RAST) manuscript — articulating the friction behind an accounting effect or building a parsimonious disclosure/contracting model with proven propositions. Builds the argument; it does not design identification (revacc-methods) or run estimation (revacc-data-analysis).
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill revacc-theory-development --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Theory & Model Development (revacc-theory-development) ## When to trigger - Predictions read as bald associations ("disclosure X relates to outcome Y") with no friction - You have archival results and are tempted to write predictions around them (HARKing risk) - An analytical paper needs a clean information structure, equilibrium, and comparative statics - A claimed channel (information asymmetry, agency, real effects) is asserted but not modeled - A referee says "what is the friction?", "the model is not minimal", or "the comparative static has no accounting reading" ## RAST is a genuine home for analytical accounting Unlike outlets where modeling is marginal, RAST runs a real **analytical lane** alongside archival and experimental work. That raises two distinct bars depending on the lane, and the most common failure is mixing them up. - **Analytical / modeling.** State primitives — players, **information structure** (who knows what, when), payoffs — then solve for equilibrium and present **propositions with proofs** and **comparative statics**. The RAST-specific demand: the model must be the **minimal structure** that delivers an *accounting* implication (optimal disclosure gra
- When to trigger
- RAST is a genuine home for analytical accounting
- The mechanism chain (archival/experimental)
- Building the analytical model (RAST-style)
- Checklist
- Anti-patterns
- Output format
What does the revacc-theory-development skill do?
Use when the economic mechanism, analytical model, or testable predictions are the bottleneck for a Review of Accounting Studies (RAST) manuscript — articulating the friction behind an accounting effect or building a parsimonious disclosure/contracting model with proven propositions. Builds the argument; it does not design identification (revacc-methods) or run estimation (revacc-data-analysis).
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill revacc-theory-development --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.