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.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jeem-replication-package --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 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 environme
- When to trigger
- JEEM's replication expectation
- Why environmental papers fail replication more often
- Building the package
- Notifying the Editor about data constraints
- Checklist
- Environmental data sources to document by name
- Worked vignette (illustrative)
- Reproducibility is part of the contribution
- Anti-patterns
- The README a JEEM replicator needs
- Output format
What does the jeem-replication-package skill do?
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.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jeem-replication-package --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.