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 Methods

ASecurity

Use when the research design and identification strategy are the bottleneck for a The Accounting Review (TAR) manuscript — choosing the setting, shock, and design that credibly identify an accounting effect, or structuring an analytical model or experiment. Designs the study; it does not run the estimation and robustness (tar-data-analysis) or frame the contribution (tar-contribution-framing).

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

Security Analysis

A100/100

Scanned 6/5/2026

Install to Claude Code

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

Installs into .claude/skills of the current project.

Are you the author of Tar Methods?

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

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

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

Download with Pro
Files
SKILL.md
---
name: tar-methods
description: Use when the research design and identification strategy are the bottleneck for a The Accounting Review (TAR) manuscript — choosing the setting, shock, and design that credibly identify an accounting effect, or structuring an analytical model or experiment. Designs the study; it does not run the estimation and robustness (tar-data-analysis) or frame the contribution (tar-contribution-framing).
---

# Research Design & Identification (tar-methods)

## When to trigger

- Your treatment (a disclosure, a standard adoption, an audit/tax regime) may be endogenous
- Adoption is staggered across firms/years and you need a defensible DiD
- You have an association and a reviewer will ask "is this causal or just correlation?"
- You are designing an experiment to isolate a channel archival data cannot separate
- You are building an analytical model and need to fix primitives and solution concept

## TAR is method-agnostic but identification-obsessed

TAR's stated policy is open to all rigorous methods; the bar is the contribution. In the dominant
**large-sample archival** lane, "rigorous" almost always means a **credible identification
strategy**, because accounting treatments (disclosure choices, conservatism, auditor selection, tax
positions) are rarely randomly assigned. Pick the design that breaks the endogeneity for *your*
accounting setting.

## Identification toolkit for archival accounting

| Identification threat / setting                          | Design                                                        |
|----------------------------------------------------------|--------------------------------------------------------------|
| Regulation / standard adoption with a clean date         | Difference-in-differences; event study around the date       |
| Staggered adoption across firms/states/countries         | Staggered DiD with modern estimators (avoid the TWFE bias)   |
| Endogenous accounting/auditor/tax choice                 | Instrumental variables / 2SLS with a defensible exclusion    |
| A threshold rule (covenant, index inclusion, size cutoff)| Regression discontinuity                                     |
| Selection on observables                                 | Matching (PSM/entropy) as a complement, not the main claim   |
| A plausibly exogenous shock to information environment    | Natural experiment; pre-trends shown                         |

State the **estimating equation**, the **unit and level**, the **fixed effects** (firm, year,
industry-year), and the **identifying variation** explicitly. The design section should make a
skeptic believe the variation is as-good-as-random conditional on controls.

## If the lane is experimental

- Manipulate the focal accounting construct; use realistic stimuli and an appropriate participant
  pool (investors, auditors, managers) — IRB documentation is required and reviewers expect it.
- Pre-register where feasible; include manipulation and attention checks; power the design for the
  interaction, not just the main effect.

## If the lane is analytical

- Fix the information structure, players, and payoffs before solving; state the equilibrium concept.
- Show the model is the *minimal* structure that generates the accounting result.

## Design hygiene

- Show **parallel pre-trends** for any DiD; report dynamic (event-time) effects.
- Defend the **exclusion restriction** for any IV — relevance is not enough.
- Pre-commit the main specification; relegate alternatives to robustness (see `tar-data-analysis`).
- Plan the **data-authenticity** trail now: the processing code for the sample is part of submission.

## Checklist

- [ ] The identifying variation (shock/setting/threshold) is named and defended
- [ ] Estimating equation, unit, level, and fixed effects are stated
- [ ] DiD designs show pre-trends and dynamic effects; staggered designs use a modern estimator
- [ ] IV exclusion restriction is argued, not asserted; matching is a complement, not the claim
- [ ] Experiments have IRB, realistic stimuli, manipulation/attention checks, and adequate power
- [ ] Analytical models fix primitives and the solution concept before solving

## Anti-patterns

- **Kitchen-sink controls** standing in for identification ("we control for everything").
- **TWFE on staggered adoption** without addressing heterogeneous-treatment-effect bias.
- **IV by convenience**: an instrument that fails exclusion (correlated with the outcome directly).
- **Matching as causal proof** when selection is on unobservables.
- **An experiment with no IRB** or with a participant pool unfit for the construct.

## Output format

```
【Lane】archival / experiment / analytical
【Setting & identifying variation】...
【Design】DiD / staggered-DiD / IV / RDD / event study / experiment / model
【Spec】equation; unit/level; fixed effects; clustering plan
【Identification defense】pre-trends / exclusion / discontinuity / randomization ...
【Data-authenticity plan】processing code + data description ready? yes/no
【Next step】tar-data-analysis
```

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 →