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

Car Data Analysis

ASecurity

Use when running and reporting the analysis for a Contemporary Accounting Research (CAR) manuscript — the right estimator for archival/capital-markets, experimental, or analytical-calibration work, robustness, and CAR's Data Integrity & Code Sharing Policy (code archiving, variable definitions, data availability statement). Executes and reports; it does not design the study (car-methods).

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

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 car-data-analysis --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Car Data Analysis?

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

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

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

Download with Pro
Files
SKILL.md
---
name: car-data-analysis
description: Use when running and reporting the analysis for a Contemporary Accounting Research (CAR) manuscript — the right estimator for archival/capital-markets, experimental, or analytical-calibration work, robustness, and CAR's Data Integrity & Code Sharing Policy (code archiving, variable definitions, data availability statement). Executes and reports; it does not design the study (car-methods).
---

# Data Analysis & Reproducibility (car-data-analysis)

## When to trigger

- Data are collected and it is time to estimate and report
- You are unsure the estimator matches the design (panel, experiment, limited DV)
- Reviewers will probe identification, robustness, or measurement choices
- You must prepare the code, variable definitions, and data availability statement CAR requires

## Choose the estimator that matches the design

| Data / claim                                     | Estimator                                                          |
|--------------------------------------------------|--------------------------------------------------------------------|
| Firm-year panel, archival effect                 | OLS/panel with firm & year fixed effects; SE clustered by firm     |
| Causal archival claim                            | Difference-in-differences, IV/2SLS, RD, entropy balancing/matching |
| Randomized experiment                            | ANOVA/ANCOVA, planned contrasts; report cell means and effect sizes|
| Process/mechanism (experiment)                   | Mediation with bootstrap CIs; moderated mediation as theorized     |
| Binary/count/censored outcome                    | Logit/probit, Poisson/NB, Tobit as fits                            |
| Analytical predictions                           | Calibration/simulation or an archival test of the model's implications |

Cluster standard errors to match the data structure (firm and/or time); for experiments, respect the randomization unit. Justify winsorizing/truncating and document the cutoffs.

## Robustness CAR reviewers expect

- Alternative specifications (controls in/out, alternative measures, subsamples).
- Sensitivity of identification (alternative instruments, parallel-trends evidence, placebo tests, bounding).
- Address competing explanations empirically; report how outliers and missing data were handled (and why).

## Data Integrity & Code Sharing Policy (CAR-specific, plan from the start)

CAR's policy (effective May 1, 2020) governs all empirical submissions — archival, experimental, field, surveys, simulations:

- **At submission (in Editorial Manager):** (1) describe how the data were acquired/produced and their sources, and attach the full instrument for surveys/experiments; (2) for proprietary organizational data, agree to provide a credible verification means on editor request and disclose any NDA restrictions; (3) disclose which authors had data access and ran the analyses.
- **Before acceptance:** (4) a **data availability statement** with a repository link, with the data **cited in the reference list**; (5) assurance — consistent with NSF guidelines — that data and code are retained by at least one author for **at least six years**.
- **Final version:** archive the **code** that builds the final dataset in a public repository, documenting **variable definitions**, observation-omission criteria (e.g., outliers), and modifications (winsorizing, truncating). Proprietary code may be withheld only if you instead explain how others can reproduce the final dataset. Exception requests accompany the initial submission and are approved by the EIC only in exceptional circumstances.
- A **title-page data availability statement** is required whenever the paper uses data.

## Checklist

- [ ] Estimator matches the design; SEs clustered to the structure / randomization respected
- [ ] Identification tests reported (parallel trends, placebos, alternative instruments) for causal archival claims
- [ ] Mediation via bootstrap CIs; effect sizes and cell means reported for experiments
- [ ] Winsorizing/truncating, outlier and missing-data handling documented with cutoffs
- [ ] Robustness and competing-explanation tests reported
- [ ] Code archived; variable definitions, omission rules, and modifications documented
- [ ] Data availability statement (with repository link, data cited) and 6-year retention assurance prepared

## Anti-patterns

- **Unclustered SEs** on panel data; ignoring the randomization unit in experiments.
- **Causal language** on an associational archival design with no identification tests.
- **Undocumented winsorizing/sample screens** that the code repository cannot reproduce.
- **Leaving code-sharing to the end** — it shapes how you build variables from day one.

## Output format

```
【Estimator】panel-FE / DiD-IV-RD / ANOVA-experiment / calibration; SE clustering ...
【Identification/robustness】tests reported ...
【Experiment】effect sizes, mediation (bootstrap CI) ...
【Screens】winsorizing/truncating, outliers, missing data — documented?
【Code & data policy】repo, variable defs, data availability statement, 6-yr retention ...
【Next step】car-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 →