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

Jbes Identification Strategy

ASecurity

Use when the methodological core of a Journal of Business & Economic Statistics (JBES) paper is the bottleneck — assumptions, regularity conditions, asymptotic theory, and Monte Carlo design for a new estimator, test, or algorithm. Stress-tests the method's validity, not a causal design.

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

Security Analysis

A100/100

Scanned 6/5/2026

Install to Claude Code

$npx -y skills add brycewang-stanford/Awesome-Journal-Skills --skill jbes-identification-strategy --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Jbes Identification Strategy?

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

Security grade badge for Jbes Identification Strategy
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/brycewang-stanford-jbes-identification-strategy/badge)](https://www.skillsdirectory.com/skills/brycewang-stanford-jbes-identification-strategy)

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

Download with Pro
Files
SKILL.md
---
name: jbes-identification-strategy
description: Use when the methodological core of a Journal of Business & Economic Statistics (JBES) paper is the bottleneck — assumptions, regularity conditions, asymptotic theory, and Monte Carlo design for a new estimator, test, or algorithm. Stress-tests the method's validity, not a causal design.
---

# Method Validity & Asymptotics (jbes-identification-strategy)

## When to trigger

- The estimator/test is proposed but its assumptions and limiting theory are not nailed down
- The asymptotic distribution, consistency, or rate is asserted without full conditions
- The Monte Carlo design does not yet show where the method holds and where it breaks
- For an applied paper, what parameter your method identifies (and under what conditions) is unclear

## What "identification" means at a methods journal

At JBES the load-bearing question is usually not a causal-design story but **whether the method delivers valid inference for its target under stated conditions**. Because JBES demands methodological novelty with **clear empirical relevance**, the assumptions cannot be so strong that no real data set — including the paper's own application — satisfies them. The credibility ladder a referee applies, strongest first:

1. **Identification of the target** — the parameter/functional is identified from the population moments the method uses, under stated conditions.
2. **Regularity conditions** — explicit (moment existence, smoothness, mixing/dependence, rate and rank conditions), each motivated and as weak as the result allows.
3. **Asymptotic theory** — consistency, limiting distribution, convergence rate, and the asymptotic variance; uniformity if claimed.
4. **Finite-sample evidence** — Monte Carlo on size, power, coverage, bias/RMSE across DGPs and sample sizes, including assumption-stressing regimes.
5. **Method robustness** — behavior under dependence, heavy tails, weak identification, high dimension, or misspecification, as the problem invites.

## Branch paths

- **New estimator** — identifying moment/objective; consistency and limiting distribution under explicit conditions; a consistent (often HAC/cluster-robust) variance estimator.
- **New test** — null, alternative, and null limiting distribution; asymptotic and finite-sample **size control** plus **power** against relevant alternatives; nuisance-parameter and boundary handling.
- **Computational/algorithmic** — correctness (same target as the slow method), complexity/scalability gain, numerical accuracy, timing, and the feasible-application payoff.
- **Applied paper** — what parameter is identified and the assumptions the method requires; dependence/weak-identification-robust inference; defend that the application needs the novelty.

## Checklist

- [ ] Target parameter/functional and its identification conditions stated
- [ ] Regularity conditions explicit and as weak as the result allows
- [ ] Consistency, limiting distribution, and rate established under those conditions
- [ ] A consistent, robust variance estimator provided
- [ ] Monte Carlo covers size, power, coverage, bias/RMSE across DGPs and n
- [ ] Breakdown regimes shown, not hidden; MC standard errors reported
- [ ] The required conditions are plausible in the empirical application

## Anti-patterns

- Asserting an asymptotic distribution with no full set of conditions
- Assumptions so strong no real data set (or the paper's own application) satisfies them
- Monte Carlo only under favorable DGPs; no breakdown shown
- Rejection rates reported with no Monte Carlo standard errors
- A "robust" variance claim with no proof or coverage simulation

## Output format

```
【Object】estimator / test / algorithm / applied-target
【Target + identification】parameter and conditions: ...
【Regularity conditions】[listed] — as weak as possible? [Y/N]
【Asymptotics】consistency / distribution / rate / variance estimator [status each]
【Monte Carlo】DGPs, n grid, size/power/coverage, MC SEs, breakdown shown? [Y/N each]
【Empirical plausibility】conditions hold in the application? [Y/N]
【Next step】jbes-data-analysis
```

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 →