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 Replication And Data Policy

ASecurity

Use when assembling the reproducible data-and-code supplement for a Journal of Business & Economic Statistics (JBES) paper under the American Statistical Association (ASA) data-sharing and reproducibility policy. Builds the supplement; it does not run the analysis itself.

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

Security Analysis

A100/100

Scanned 6/5/2026

Install to Claude Code

$npx -y skills add brycewang-stanford/Awesome-Journal-Skills --skill jbes-replication-and-data-policy --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Jbes Replication And Data Policy?

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

Security grade badge for Jbes Replication And Data Policy
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/brycewang-stanford-jbes-replication-and-data-policy/badge)](https://www.skillsdirectory.com/skills/brycewang-stanford-jbes-replication-and-data-policy)

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

Download with Pro
Files
SKILL.md
---
name: jbes-replication-and-data-policy
description: Use when assembling the reproducible data-and-code supplement for a Journal of Business & Economic Statistics (JBES) paper under the American Statistical Association (ASA) data-sharing and reproducibility policy. Builds the supplement; it does not run the analysis itself.
---

# Replication & Data Policy (jbes-replication-and-data-policy)

## When to trigger

- The paper is heading toward submission/acceptance and a code+data supplement is needed
- You want a reproducible pipeline early to pre-empt referee replication requests
- Raw data are restricted/proprietary and you need a disclosure-compliant plan
- You need to write a data availability statement

## Why this matters at JBES

JBES is owned by the **American Statistical Association** and published by Taylor & Francis, so it follows **ASA's data-sharing and reproducibility policy** rather than the AEA Data Editor regime. Under that policy, the ASA **strongly encourages** authors to include **data sets and code as supplementary material** that demonstrate the article's results, to make the underlying data **publicly available**, and to include a **data availability statement**; individual ASA journal editors may set their own (possibly stricter) rules, and authors may request a **waiver** for confidentiality/security reasons. Important: JBES does **NOT** use the JAE Data Archive — that archive belongs to the *Journal of Applied Econometrics*, a separate Wiley journal. Whether JBES **mandates** code+data at acceptance with a dedicated reproducibility check (as JASA does) versus merely encouraging it could not be confirmed and is **待核实** — verify on the live instructions page.

## Supplement anatomy (methods paper)

```
supplement/
  README.{md,pdf}      # data sources, software versions, run order, runtime, exhibit map
  code/
    00_setup           # installs/pins packages, sets paths, sets seeds
    01_simulation      # regenerates every Monte Carlo table/figure
    02_application     # regenerates every empirical table/figure
  data/
    raw/               # as obtained, or access instructions if restricted
    derived/           # built by code, never hand-edited
  output/              # regenerated, checked against the manuscript
```

## README must specify

- **Provenance** of every data source (version/vintage, access date); for restricted data, exact access steps.
- **Software environment** with pinned versions (`renv.lock`, `requirements.txt`, recorded `ssc`/`net` + Stata version).
- **Run order** via one master script; expected wall-clock runtime, hardware, and total Monte Carlo replications.
- **Seeds** for every simulation/bootstrap/randomization step.
- **Exhibit map** linking each table/figure (including simulation tables) to the script that produces it.

## Checklist

- [ ] One master script regenerates every table and figure, including all Monte Carlo numbers
- [ ] Software and package versions pinned and documented
- [ ] Random seeds set and reported for all stochastic steps
- [ ] Data availability statement drafted (ASA expectation)
- [ ] Restricted/proprietary data have documented access steps + a runnable proxy
- [ ] No hand-edited derived data; absolute paths removed
- [ ] Output regenerated and checked against the manuscript numbers
- [ ] Live JBES enforcement (mandatory vs encouraged) verified (待核实)

## Anti-patterns

- A zip of scripts with no README and no run order
- Hard-coded local paths that break on another machine
- Missing seeds, so Monte Carlo numbers cannot be reproduced
- Assuming the JAE Data Archive applies (it does not — that is a different journal)
- Asserting JBES mandates deposit without checking (status is 待核实)

## Output format

```
【Master script】regenerates all tables/figures incl. Monte Carlo? [Y/N]
【Env pinned】versions + packages documented? [Y/N]
【Seeds】set + reported? [Y/N]
【Data availability statement】drafted? [Y/N]
【Restricted data】access steps + runnable proxy? [Y/N / NA]
【Policy check】live JBES enforcement verified? [Y/N — 待核实]
【Next step】jbes-review-process
```

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 →