Individual skill
jeem-replication-package
Use when assembling the data and code deposit for a Journal of Environmental Economics and Management (JEEM) manuscript — meeting JEEM's data-availability/replication expectation, documenting monitoring/satellite/admin/restricted environmental data, and writing a README that reproduces every exhibit. Builds the package; it does not run the analysis or invent data.
Journal-of-Environmental-Economics-and-Management-Skills/skills/jeem-replication-package/SKILL.md
Source commit 932eb23331721b16e967c59f093781be1928b498
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- 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,411
- 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
- writing Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
Read excerpt
# Replication Package (jeem-replication-package)
## When to trigger
- The paper is heading to submission or acceptance and the data/code deposit is not assembled
- The analysis uses **restricted or proprietary** environmental data (utility, satellite, admin pollution, parcel) and you must document a replication path you cannot fully share
- The Editor must be told *at submission* that the data-availability conditions cannot be fully met
- Code reproduces exhibits manually rather than from a single master script
## JEEM's replication expectation
JEEM has a long-standing policy: **all data used must be clearly documented, computational methods explained in enough detail to permit replication, and the data made available to any researcher for replication** — and the **Editor must be notified at submission if these conditions cannot be met** (检索于 2026-06;以官网为准; re-check the current guide for authors, as Elsevier data-availability and code-sharing requirements are tightening). Environmental papers routinely hit this wall because the data are spatial, sensor-derived, or proprietary; the package must show a *credible reproduction path* even when raw data cannot be posted.
## Why environmental papers fail replication more often