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 Methods

ASecurity

Use when the research design and identification strategy are the bottleneck for a Journal of Accounting Research (JAR) manuscript — choosing the setting, source of identifying variation, and sample to support a causal accounting claim. Designs the study; it does not run the estimation, clustering, or robustness (jar-data-analysis).

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

Works with

api

Security Analysis

A100/100

Scanned 6/5/2026

Install to Claude Code

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

Installs into .claude/skills of the current project.

Are you the author of Jar Methods?

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

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

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

Download with Pro
Files
SKILL.md
---
name: jar-methods
description: Use when the research design and identification strategy are the bottleneck for a Journal of Accounting Research (JAR) manuscript — choosing the setting, source of identifying variation, and sample to support a causal accounting claim. Designs the study; it does not run the estimation, clustering, or robustness (jar-data-analysis).
---

# Research Design & Identification (jar-methods)

## When to trigger

- The design is a panel regression with no source of identifying variation
- The claim is causal but the variation is observational/endogenous
- A referee says "this is correlation, not causation" or "the channel is unidentified"
- You must choose between an archival, experimental, analytical, or field design

## JAR's dominant design: empirical-archival capital markets

JAR's defining methodology is **large-sample empirical-archival capital-markets** research (financial-statement and market-data econometrics in the **Ball-Brown** lineage). The journal also publishes **experimental**, **analytical/modeling**, and **field-study** work, and the **Registered Reports** track is well suited to higher-outcome-risk designs that require new data collection. The bar across all of them is **credible identification**: a referee must believe the estimate reflects the economic effect you claim, not an omitted variable, reverse causality, or selection.

## Find identifying variation (the core archival problem)

| Theoretical claim | Identification that earns it |
|-------------------|------------------------------|
| Effect of a rule/standard | Staggered or sharp adoption as a natural experiment (modern DiD) |
| Effect at a threshold | Regression discontinuity (e.g., index inclusion, size cutoffs) |
| Effect of an endogenous firm choice | IV/2SLS with a defensible instrument, or a shock to the choice |
| Information content of a disclosure | Short-window event study around the release |
| Causal mechanism under control | Experiment (lab/online/field), often paired with archival evidence |

- **Anticipate the threats by name**: omitted correlated variables, reverse causality, selection into treatment, and measurement error. State which one is the binding concern and how the design neutralizes it.
- **Parallel trends / pre-trends** for DiD; **bandwidth and manipulation tests** for RD; **instrument relevance and exclusion** for IV — plan the diagnostics now, not in the rebuttal.
- **Construct measurement**: define accounting constructs (earnings quality, disclosure, audit quality, comparability) with measures used in prior JAR work, and plan validation.

## Sample and reproducibility from the start

Specify the sample frame, screens, and data vintages (Compustat/CRSP/I/B/E/S/Audit Analytics/EDGAR). Because JAR **requires** posted data and code, design the pipeline to be top-to-bottom reproducible from raw extracts, recording exclusion rules and access dates.

## Checklist

- [ ] A specific source of identifying variation is named (shock/threshold/instrument/manipulation)
- [ ] The binding endogeneity threat is identified and the design addresses it
- [ ] Diagnostics planned (pre-trends / bandwidth / first-stage / manipulation checks)
- [ ] Accounting constructs measured with validated, prior-literature measures
- [ ] Sample frame, screens, and data vintages specified; pipeline reproducible
- [ ] If high-risk/new-data: Registered Reports (Stage 1 protocol) considered

## Anti-patterns

- **Kitchen-sink OLS** with controls standing in for identification.
- **Endogenous regressor** treated as exogenous with no strategy.
- **Weak/implausible instruments** failing relevance or exclusion.
- **Staggered DiD with two-way FE** ignoring heterogeneous-treatment-timing bias (use modern estimators).
- **Event windows fished** for significance; ad hoc bandwidths in RD.

## Output format

```
【Design】archival-NE / RD / IV / event-study / experiment / analytical / field
【Identifying variation】shock / threshold / instrument / manipulation
【Binding threat】OVB / reverse causality / selection / measurement — addressed by ...
【Diagnostics planned】pre-trends / bandwidth / first-stage / balance ...
【Constructs & measures】definitions + validation
【Sample & reproducibility】frame, screens, vintages; data/code pipeline
【Next step】jar-data-analysis
```

## 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) — archival data sources and identification tooling (reghdfe / csdid / rdrobust / ivreghdfe)

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 →