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

Tar Theory Development

ASecurity

Use when the economic mechanism, analytical model, or predictions are the bottleneck for a The Accounting Review (TAR) manuscript — articulating why an accounting effect occurs and deriving testable predictions or model propositions. Builds the argument; it does not design identification (tar-methods) or run the estimation (tar-data-analysis).

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

Security Analysis

A100/100

Scanned 6/5/2026

Install to Claude Code

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

Installs into .claude/skills of the current project.

Are you the author of Tar Theory Development?

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

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

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

Download with Pro
Files
SKILL.md
---
name: tar-theory-development
description: Use when the economic mechanism, analytical model, or predictions are the bottleneck for a The Accounting Review (TAR) manuscript — articulating why an accounting effect occurs and deriving testable predictions or model propositions. Builds the argument; it does not design identification (tar-methods) or run the estimation (tar-data-analysis).
---

# Mechanism & Model Development (tar-theory-development)

## When to trigger

- Predictions read as bald associations ("disclosure X relates to outcome Y") with no economic logic
- You have archival results and are tempted to write predictions around them (HARKing risk)
- An analytical paper needs a clean model, equilibrium, and comparative statics
- Mediating channels (information asymmetry, agency costs, real effects) are claimed but not modeled
- A reviewer says "the prediction is mechanical," "what is the friction?", or "why would this hold?"

## The TAR theory bar

TAR is open to all methods, but it does not publish atheoretical regressions. Whether the paper is
archival, experimental, or analytical, every prediction must rest on an **explicit economic
mechanism** — typically an information friction (asymmetric information, adverse selection, moral
hazard), an agency conflict, a contracting or monitoring force, a processing/attention constraint,
or a real-decision channel through which accounting information changes behavior. Name the friction
and the channel verb (reduces information asymmetry, tightens monitoring, relaxes a covenant,
disciplines investment, deters tax aggressiveness).

## The three theory lanes at TAR

- **Archival/empirical:** derive directional predictions from accounting and information economics
  (disclosure theory, earnings-management incentives, audit-quality demand, conservatism,
  tax-avoidance trade-offs). Predictions are written *before* estimation; the data test them.
- **Analytical/modeling:** state primitives (players, information structure, payoffs), solve for
  equilibrium, and present **propositions with proofs** and **comparative statics** that yield
  testable or normative implications for accounting (optimal disclosure, signaling, the demand for
  conservatism, audit effort, performance measurement). Keep assumptions minimal and defend each.
- **Experimental/behavioral:** ground hypotheses in psychology and accounting theory (judgment,
  motivated reasoning, professional skepticism, investor processing) where archival data cannot
  isolate the mechanism; the experiment manipulates the construct to establish the channel directly.

## Building a prediction (the mechanism chain)

1. **Setting & construct** — the accounting object (disclosure, accrual, audit, tax position) and
   the institutional setting that makes it bite.
2. **Friction** — the information or agency friction the accounting acts on.
3. **Channel** — the economic process linking the construct to the outcome (pricing, contracting,
   real investment, litigation, reputation, regulatory enforcement).
4. **Direction & form** — sign, and whether monotone, non-monotone, or conditional.
5. **Cross-section / boundary** — where the effect strengthens or reverses, and *why* economically.

## For analytical papers specifically

- Make the **information structure** explicit (who knows what, when).
- Prove propositions; do not assert equilibrium properties.
- Translate comparative statics into empirical predictions or policy implications an accounting
  reader cares about; a model with no accounting payoff is a math paper.

## Checklist

- [ ] Every prediction rests on a named friction and channel, not a mechanical correlation
- [ ] The relevant accounting/information-economics theory is invoked through its logic, not a citation
- [ ] Archival predictions were fixed before estimation (no HARKing)
- [ ] Analytical claims are stated as proven propositions with comparative statics
- [ ] Cross-sectional/boundary predictions have an economic reason
- [ ] At least one alternative explanation is named and will be tested or modeled out

## Anti-patterns

- **HARKing**: writing predictions to match the regression output after the fact.
- **Mechanical predictions**: a sign that follows from accounting identities, not economics.
- **Borrowed friction**: invoking "information asymmetry" with no account of how it operates here.
- **Model without payoff**: an elegant equilibrium with no accounting implication.
- **Channel by proxy**: asserting a real-effects channel the design cannot distinguish from pricing.

## Output format

```
【Lane】archival / analytical / experimental
【Friction】information asymmetry / agency / attention / contracting ...
【Prediction P1 (focal)】construct → channel → outcome; direction/form
【Prediction P2 (channel/mediation)】...
【P3+ (cross-section/boundary)】... economic reason
【Analytical only】propositions proven? comparative statics stated? yes/no
【Rival explanation】named + how it will be ruled out
【Next step】tar-literature-positioning, then tar-methods
```

Attribution

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

Your tool, in front of Claude Code builders.

3 founder slots · $299/mo · GSC-verified traffic · sponsors can never buy grades.

See placements

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

Your tool, in front of Claude Code builders.

3 founder slots · $299/mo · GSC-verified traffic · sponsors can never buy grades.

See placements

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', ...

686011 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 →