Individual skill
jegeo-replication-package
Use when assembling data, code, and spatial-data documentation for a Journal of Economic Geography (JEG) manuscript. Builds a credible, shareable package under JEG's encouragement-based post-acceptance policy; it does not invent data.
Journal-of-Economic-Geography-Skills/skills/jegeo-replication-package/SKILL.md
Source commit 932eb23331721b16e967c59f093781be1928b498
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Network or broad shell
- Last checked
- Nov 9, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 1,405
- Repository last updated
- Sep 27, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- academic-writing Repository topic
- agent-skills Repository topic
- journal Repository topic
- academic-research Repository topic
- ai-agents Repository topic
- anthropic Repository topic
- awesome-list Repository topic
- claude Repository topic
- claude-code Repository topic
- economics Repository topic
- data Derived category
- docs Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Read excerpt
# Replication Package (jegeo-replication-package)
## When to trigger
- The analysis uses spatial data (shapefiles, geocoded points, raster, network ties) whose provenance and processing are not documented
- A referee asks "can this be reproduced?" and the answer is currently no
- You are deciding what to share given JEG's policy and any confidentiality constraints
- Spatial joins, projections, and unit-boundary versions were done interactively and are not scripted
## What JEG actually requires (and what it does not)
JEG's data/code policy is **encouragement-based and triggered after acceptance**, not a mandatory pre-acceptance replication archive (检索于 2026-06；以官网为准). Authors are asked at acceptance whether associated data exist and whether they wish to publish them as supplementary material; ORCID is required at submission. This is a genuine point of difference from QE, AEJ, and the AEA journals, which run a Data Editor reproducibility check before acceptance.
The practical implication: at JEG you are not forced to deposit, but a credible, well-documented package is a strong signal and pre-empts the reproducibility objection. **Build it as if it were required** — referees increasingly expect it, and editors may ask — but understand the timing and the discretion the policy gives you.