geb-replication-and-data-policy
Use when planning data and code sharing for a Games and Economic Behavior (GEB) manuscript. GEB encourages but does NOT mandate a replication archive — unlike AER/Econometrica/JAE — so this skill helps you share well voluntarily and avoid assuming requirements that do not exist here.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill geb-replication-and-data-policy --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Replication & Data Policy (geb-replication-and-data-policy) ## When to trigger - You have experimental data, simulation code, or solver inputs and are unsure what GEB requires - You assumed GEB has a mandatory data archive (it does not) and are budgeting effort accordingly - You want to make a theory paper's numerical examples reproducible - An accepted-stage checklist is being assembled ## The GEB data policy — encouraged, not required This is a **meaningful distinction** for a journal that publishes experimental work: GEB does **not** operate a mandatory data/code replication archive comparable to the AEA journals (AEJ/AER), Econometrica, or the JAE Data Archive. GEB follows Elsevier's **"encourages and enables"** research-data stance (Option C): authors are *invited* to deposit data and code in a repository (e.g., **Mendeley Data**, free and open access), to include a **data-availability statement**, or to publish a **Data Brief** — but deposit is **not a condition of publication**. Do not assume a required openICPSR-style archive; verify the current wording on the Guide for Authors (some details here are 待核实 — drawn from secondary sources). Even though it is optional, sharing
- When to trigger
- The GEB data policy — encouraged, not required
- What to prepare (voluntarily, but recommended)
- For experimental papers
- For theory papers with computation
- Statement and deposit
- Why voluntary sharing still pays at GEB
- Worked micro-example: the availability statement
- Anti-patterns
- Reproducibility pass for Games and Economic Behavior
- Output format
What does the geb-replication-and-data-policy skill do?
Use when planning data and code sharing for a Games and Economic Behavior (GEB) manuscript. GEB encourages but does NOT mandate a replication archive — unlike AER/Econometrica/JAE — so this skill helps you share well voluntarily and avoid assuming requirements that do not exist here.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill geb-replication-and-data-policy --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From brycewang-stanford/Awesome-Journal-Skills, a repository with 909 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.