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 Data Analysis

ASecurity

Use when running and reporting the estimation for a The Accounting Review (TAR) manuscript — the estimator, fixed effects, standard-error clustering, robustness, and the data-authenticity / code-access documentation TAR requires. Executes and reports the analysis; it does not design identification (tar-methods) or frame the contribution (tar-contribution-framing).

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

Security Analysis

A100/100

Scanned 6/5/2026

Install to Claude Code

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

Installs into .claude/skills of the current project.

Are you the author of Tar Data Analysis?

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

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

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

Download with Pro
Files
SKILL.md
---
name: tar-data-analysis
description: Use when running and reporting the estimation for a The Accounting Review (TAR) manuscript — the estimator, fixed effects, standard-error clustering, robustness, and the data-authenticity / code-access documentation TAR requires. Executes and reports the analysis; it does not design identification (tar-methods) or frame the contribution (tar-contribution-framing).
---

# Estimation, Robustness & Data Authenticity (tar-data-analysis)

## When to trigger

- The sample is built and it is time to estimate and report
- You are unsure whether your standard errors, fixed effects, or estimator match the design
- Reviewers will probe robustness, alternative measures, or sample-selection screens
- You must assemble the data-authenticity / code-access package TAR requires
- A reviewer says "the result is not robust" or "I cannot tell how the sample was built"

## Estimator and inference (large-sample archival core)

- **Match the estimator to the design** set in `tar-methods`: OLS with high-dimensional fixed
  effects (firm, year, industry-year) for panel associations; DiD / staggered-DiD with a modern
  estimator for adoption shocks; 2SLS for endogenous regressors; RDD for threshold settings; logit/
  probit/Poisson/Tobit for limited or count outcomes (e.g., restatement, going-concern, fraud).
- **Cluster standard errors** at the level of treatment assignment / correlation (firm, or two-way
  firm-and-year); for few clusters use the wild-cluster bootstrap.
- **Report fixed effects explicitly** and show how the coefficient moves as you add them — a result
  that survives tighter fixed effects is more credible than one that does not.
- For **accounting-specific measures** (discretionary accruals, real earnings management, abnormal
  audit fees, effective/cash tax rates, disclosure tone), state the construction model and screen,
  and show the result is not an artifact of the proxy.

## Robustness reviewers expect

- Alternative measures of the focal accounting construct (e.g., a second accruals model; cash vs.
  GAAP ETR; alternative disclosure proxy).
- Alternative samples and screens (drop financials/utilities; winsorize vs. truncate; subperiods).
- Sensitivity of the identifying assumption (pre-trends, placebo dates, alternative instruments,
  bandwidth choices for RDD).
- Falsification / placebo tests where the effect should be absent.
- Economic magnitude, not just significance — interpret the coefficient in accounting terms.

## Data-authenticity & code access (a TAR-specific requirement)

TAR requires authors to enable confirmation of data authenticity, with differentiated rules:

- **Publicly available databases** (Compustat, CRSP, I/B/E/S, Audit Analytics): provide a precise
  description of the data **and** access to the **computer code** used to process it.
- **Data abstracted from public sources** (hand-collected from filings, PCAOB reports): provide the
  **abstraction methodology** plus code access.
- **Privately collected data** (proprietary field data, experiments): provide enough detail for
  reader confidence; **corroborating third parties** are acceptable.

Code/data sufficiency is part of the submission and acceptance requirements (待核实 whether a named
public repository deposit is mandated at acceptance). Build clean, commented scripts from raw
extract to every table now — not after the R&R.

## Checklist

- [ ] Estimator matches the design; FEs reported; SEs clustered at the right level
- [ ] Coefficient stability shown across FE/control sets
- [ ] Focal accounting measure validated with an alternative construction
- [ ] Pre-trends/placebo/falsification tests reported where the design needs them
- [ ] Economic magnitude interpreted, not just p-values
- [ ] Data-authenticity package assembled per data type (description + processing code / methodology)
- [ ] Sample-construction screens documented and reproducible from raw data

## Anti-patterns

- **Uncluttered p-values, no magnitude** — significance without economic interpretation.
- **Single proxy** for a contested construct (e.g., one accruals model) presented as definitive.
- **TWFE on staggered adoption** ignoring heterogeneous-treatment-effect bias.
- **Robustness theater**: many tables that never vary the thing a skeptic doubts.
- **Unreproducible sample**: screens and merges that no one can rebuild from the raw data.
- **No processing code** ready, in violation of the data-authenticity policy.

## Output format

```
【Estimator】OLS-HDFE / staggered-DiD / 2SLS / RDD / logit-Poisson ...
【Fixed effects & clustering】... ; SE level ...
【Focal measure】construction + alternative proxy: pass/issues
【Robustness】alt measures / samples / placebo / pre-trends ...
【Economic magnitude】coefficient means ... in accounting terms
【Data authenticity】public-db / abstracted / private — code & description ready? yes/no
【Open issues for reviewers】...
【Next step】tar-contribution-framing
```

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 →