eursr-transparency-and-data
Use when preparing the Data Availability Statement and the replication package for a European Sociological Review (ESR) manuscript. ESR requires a Data Availability Statement for every manuscript and (for submissions from 1 January 2025) a replication package for statistical/computational work upon conditional acceptance; qualitative work is exempt. Prepares documentation; it does not over-state or under-state the policy.
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill eursr-transparency-and-data --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.
# Transparency & Data (eursr-transparency-and-data) ESR's transparency expectations are **stricter than a sharing norm**: a **Data Availability Statement (DAS) is required for every manuscript**, and for **submissions received on or after 1 January 2025**, authors using **statistical or computational methods must deposit a replication package as a condition of publication** (assembled by acceptance, typically required at conditional acceptance). **Qualitative- data work is exempt** from the package requirement. **Confirm the current wording and effective dates on the live OUP/ESR page** — this skill states the policy as verified in 2026-06; treat specifics as volatile. ## When to trigger - Writing the **Data Availability Statement** (needed at submission) - Assembling the **replication package** ahead of conditional acceptance - Deciding what can be shared given confidentiality, DUA, or proprietary constraints (register data) - A reviewer or editor asked how the analysis can be reproduced ## What the ESR policy requires (verify current wording) - **Data Availability Statement** in every article — describing how the data can be accessed and the conditions for access (open, controlle
- When to trigger
- What the ESR policy requires (verify current wording)
- Build a package that reproduces (do this from the start)
- Transparency posture by data type (ESR)
- Worked micro-example (illustrative)
- Referee / editor pushback → ESR-specific fix
- Calibration anchors
- Anti-patterns
- Output format
- Supplementary resources
What does the eursr-transparency-and-data skill do?
Use when preparing the Data Availability Statement and the replication package for a European Sociological Review (ESR) manuscript. ESR requires a Data Availability Statement for every manuscript and (for submissions from 1 January 2025) a replication package for statistical/computational work upon conditional acceptance; qualitative work is exempt. Prepares documentation; it does not over-state or under-state the policy.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill eursr-transparency-and-data --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.