Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsCommunityBlog
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Jar Theory Development

ASecurity

Use when building the economic mechanism and deriving signed, falsifiable predictions for a Journal of Accounting Research (JAR) manuscript — grounding hypotheses in information economics, contracting, and disclosure theory rather than psychology-style construct chains. Builds the mechanism; it does not design the empirical test (jar-methods) or run it (jar-data-analysis).

1,052 stars
0 votes
0 copies
0 views
Added 6/5/2026
ai-agentsgo

Security Analysis

A100/100

Scanned 6/5/2026

Install to Claude Code

$npx -y skills add brycewang-stanford/Awesome-Journal-Skills --skill jar-theory-development --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Jar Theory Development?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Jar Theory Development
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/brycewang-stanford-jar-theory-development/badge)](https://www.skillsdirectory.com/skills/brycewang-stanford-jar-theory-development)

More formats (shields.io, HTML) on the badges page.

Download with Pro
Files
SKILL.md
---
name: jar-theory-development
description: Use when building the economic mechanism and deriving signed, falsifiable predictions for a Journal of Accounting Research (JAR) manuscript — grounding hypotheses in information economics, contracting, and disclosure theory rather than psychology-style construct chains. Builds the mechanism; it does not design the empirical test (jar-methods) or run it (jar-data-analysis).
---

# Theory & Prediction Development (jar-theory-development)

## When to trigger

- Predictions are descriptive ("X is associated with Y") with no economic channel
- A referee asks "what is the mechanism?" or "why would a rational agent do this?"
- The sign of the effect is ambiguous and needs an explicit argument
- You need to motivate an empirical prediction from an analytical/agency model

## How JAR theorizes: economics first

JAR's dominant tradition is **positive, economics-based** accounting research. Predictions are derived from the behavior of informed economic agents — managers, investors, analysts, auditors, regulators — under asymmetric information, contracting frictions, and proprietary costs. The relevant toolkit is **information economics** (signaling, disclosure, adverse selection), **agency/contracting theory** (incentives, monitoring, debt covenants), **market price-formation** logic (how information enters prices and expectations, in the Ball-Brown lineage), and **standard-setting/political-economy** arguments. This is *not* the latent-construct, mediator-moderator style of psychology-based fields: a JAR mechanism is an economic argument about incentives and information, often disciplined by a simple model.

## Build the mechanism

- **Name the friction.** Information asymmetry between whom and whom? A contracting incompleteness? A proprietary cost? The friction is what makes accounting information matter.
- **Specify the agent's problem.** What does the manager/investor/auditor maximize, and how does the accounting variable change their optimal action or belief?
- **Sign the prediction.** State the predicted direction and *why*. If two channels push opposite ways (transparency vs. proprietary cost; recognition vs. disclosure), say so and let the data adjudicate — an ex-ante ambiguous sign is acceptable if argued, but it must be argued.
- **Derive observable implications.** Beyond the main effect, predict **cross-sectional variation**: where should the effect be stronger (high information asymmetry, weak governance, binding covenants)? These conditional predictions make the channel testable and separate it from alternatives.
- **Consider a model.** Analytical work is welcome at JAR; a stylized model that yields the comparative static you test sharpens the prediction and pre-empts "story-time" critiques.

## Registered Reports note

On the **Registered Reports** track, the theory and signed predictions are locked in the **Stage 1 protocol** before data are seen — strong a priori derivation is essential because in-principle acceptance is granted on the protocol's quality, not the eventual results.

## Checklist

- [ ] The friction (information asymmetry / agency / proprietary cost) is named explicitly
- [ ] The agent's optimization problem and the accounting variable's role are specified
- [ ] Each prediction has a stated sign and an economic reason (or a justified ambiguous sign)
- [ ] Cross-sectional / conditional predictions sharpen the channel
- [ ] Alternative (non-causal or mechanical) explanations are anticipated
- [ ] If analytical: comparative statics map to the empirical predictions

## Anti-patterns

- **Construct-chain theorizing**: psychology-style mediators with no economic agent or friction.
- **Sign by hand-waving**: predicting a direction with no incentive argument.
- **Kitchen-sink hypotheses**: many associations, no unifying mechanism.
- **Mechanism only in the title**: a channel asserted in the intro but never tested cross-sectionally.
- **Rational/behavioral muddle**: invoking efficiency and mispricing interchangeably without committing.

## Output format

```
【Friction】information asymmetry / agency / proprietary cost (between whom)
【Agent's problem】who maximizes what; role of the accounting variable
【Main prediction(s)】sign + economic reason
【Conditional predictions】where stronger/weaker (and why)
【Model?】comparative static derived / not needed
【Alternative explanations to rule out】[...]
【Next step】jar-literature-positioning or jar-methods
```

## 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) — empirical-accounting data sources and analytical/econometric software

Attribution

brycewang-stanfordbrycewang-stanford
View sourceMore from brycewang-stanford →
SSkills DirectorySkills Directory

Know which skills are safe — weekly.

Best new skills + every skill we flagged as malicious. From the team that scanned 103,619.

Join free

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Know which skills are safe — weekly.

Best new skills + every skill we flagged as malicious. From the team that scanned 103,619.

Join free

Related Skills

Caveman

Ultra-compressed communication mode that cuts output tokens while keeping technical accuracy. Levels: lite, full, ultra and the wenyan variants. Use for /caveman, "caveman mode", "talk like caveman", "be brief" or "less tokens".

1066601 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

693161 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3351 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

651 votes

math-skill

A comprehensive mathematical reasoning skill for AI assistants — handles arithmetic to research-level problems with rigorous step-by-step reasoning, systematic verification, and transparent uncertainty handling

381 votes
View all in ai-agents →