Use when documenting the coverage account of an Annual Review of Sociology (ARSoc) review and the transparency obligations of any systematic-review search or meta-analysis the review itself contains. Builds the search/selection record and the reproducibility plan; it does not gather the literature (arsoc-literature-synthesis) or appraise individual studies' designs (arsoc-comprehensiveness-and-balance).
Transparency & Reproducibility for a Review (arsoc-transparency-and-reproducibility)
When to trigger
The synthesis is settled and you must show how the literature was searched and selected
The review reports a quantitative synthesis (meta-analysis, meta-regression, citation analysis) of its own
A Committee member or referee is likely to ask "how did you decide what to include?"
You want the coverage account to pre-empt the predictable "you omit literature X" pushback
What "transparency" means in a review with no primary data
An ARSoc review reports no new data of its own, so the usual replication-package machinery (raw data, estimation code, a reproducibility README of your analysis) does not apply to the review's claims about the world. Transparency instead bites on two things you do produce:
The coverage account — a documented, near-PRISMA-style record of how the literature was searched, screened, and selected. This is what makes "comprehensive" a verifiable claim rather than a boast.
Any analysis the review itself runs — if the review contributes a meta-analysis, a citation/bibliometric analysis, or a re-coded dataset of studies, that artefact must be reproducible and depositable like any quantitative work.
Distinguish the two clearly: you are not defending an identification strategy of your own (there is none); you are documenting how you found and weighed others' work, and reproducing any synthesis you actually computed.
The coverage account (near-PRISMA, adapted for sociology)
Carry forward the saturation log from arsoc-literature-synthesis into a brief, sharable record:
Element
What to document
Databases & dates
Sociological Abstracts, Web of Science, Scopus, JSTOR, Google Scholar — with search dates
Search terms & traditions
keyword strings and the theoretical-tradition names swept
Inclusion / exclusion
what counted (years, methods/modes, languages, publication types) and what was excluded and why
Mode coverage
how qualitative, computational, demographic, and theoretical work were captured (not just quant)
Saturation
where forward/backward snowballing stopped yielding new must-cites
Counts
rough numbers screened vs. discussed, so "comprehensive" is auditable
Sociology reviews are rarely strict PRISMA systematic reviews, but a near-PRISMA narrative of the search makes the coverage defensible and is increasingly expected. Confirm whether the topic warrants a formal PRISMA flow on the author pages (检索于 2026-06;以官网为准).
When the review runs its own analysis
If the review contributes a meta-analysis or bibliometric study:
Deposit data + code in a public repository (OSF, Dataverse, Zenodo) so the synthesis is reproducible; cite the DOI.
State the protocol: inclusion criteria, effect-size extraction, coding rules, weighting, heterogeneity and publication-bias diagnostics.
Pool only commensurable studies — never reduce qualitative or theoretical work to a spurious effect size (see arsoc-tables-figures).
Make the coding reproducible: a second coder could re-derive your study-level codes from your codebook.
1---2name: arsoc-transparency-and-reproducibility3description: Use when documenting the coverage account of an Annual Review of Sociology (ARSoc) review and the transparency obligations of any systematic-review search or meta-analysis the review itself contains. Builds the search/selection record and the reproducibility plan; it does not gather the literature (arsoc-literature-synthesis) or appraise individual studies' designs (arsoc-comprehensiveness-and-balance).4---567# Transparency & Reproducibility for a Review (arsoc-transparency-and-reproducibility)
89## When to trigger
1011- The synthesis is settled and you must show *how* the literature was searched and selected
12- The review reports a quantitative synthesis (meta-analysis, meta-regression, citation analysis) of its own
13- A Committee member or referee is likely to ask "how did you decide what to include?"
14- You want the coverage account to pre-empt the predictable "you omit literature X" pushback
1516## What "transparency" means in a review with no primary data
1718An ARSoc review reports **no new data of its own**, so the usual replication-package machinery (raw data, estimation code, a reproducibility README of *your* analysis) does not apply to the review's claims about the world. Transparency instead bites on two things you *do* produce:
19201. **The coverage account** — a documented, near-PRISMA-style record of how the literature was searched, screened, and selected. This is what makes "comprehensive" a verifiable claim rather than a boast.
212. **Any analysis the review itself runs** — if the review contributes a meta-analysis, a citation/bibliometric analysis, or a re-coded dataset of studies, *that* artefact must be reproducible and depositable like any quantitative work.
2223Distinguish the two clearly: you are not defending an identification strategy of your own (there is none); you are documenting how you found and weighed others' work, and reproducing any synthesis you actually computed.
2425## The coverage account (near-PRISMA, adapted for sociology)
2627Carry forward the saturation log from `arsoc-literature-synthesis` into a brief, sharable record:
2829| Element | What to document |
30|---------|------------------|
31| Databases & dates | Sociological Abstracts, Web of Science, Scopus, JSTOR, Google Scholar — with search dates |
32| Search terms & traditions | keyword strings *and* the theoretical-tradition names swept |
33| Inclusion / exclusion | what counted (years, methods/modes, languages, publication types) and what was excluded and why |
34| Mode coverage | how qualitative, computational, demographic, and theoretical work were captured (not just quant) |
35| Saturation | where forward/backward snowballing stopped yielding new must-cites |
36| Counts | rough numbers screened vs. discussed, so "comprehensive" is auditable |
3738Sociology reviews are rarely strict PRISMA systematic reviews, but a *near*-PRISMA narrative of the search makes the coverage defensible and is increasingly expected. Confirm whether the topic warrants a formal PRISMA flow on the author pages (检索于 2026-06;以官网为准).
3940## When the review runs its own analysis
4142If the review contributes a meta-analysis or bibliometric study:
4344- **Deposit data + code** in a public repository (OSF, Dataverse, Zenodo) so the synthesis is reproducible; cite the DOI.
45- **State the protocol:** inclusion criteria, effect-size extraction, coding rules, weighting, heterogeneity and publication-bias diagnostics.
46- **Pool only commensurable studies** — never reduce qualitative or theoretical work to a spurious effect size (see `arsoc-tables-figures`).
47- **Make the coding reproducible:** a second coder could re-derive your study-level codes from your codebook.
4849## Checklist
5051- [ ] Coverage account documented (databases, dates, terms, inclusion/exclusion, saturation, counts)
52- [ ] Search captured qualitative, computational, demographic, and theoretical modes, not only quant
53- [ ] Near-PRISMA narrative (or formal flow if warranted) prepared; format confirmed on author pages (volatile)
54- [ ] Any meta-analysis/bibliometric analysis: data + code deposited with a citable DOI
55- [ ] Synthesis protocol stated (inclusion, extraction, coding rules, weighting, bias diagnostics)
56- [ ] Study-level coding reproducible from a documented codebook
57- [ ] Only commensurable studies pooled into any quantitative synthesis
58- [ ] Coverage account ready to pre-empt "why did you omit X?" at review
5960## Anti-patterns
6162- Claiming "comprehensive coverage" with no documented search to back it
63- Importing primary-research replication machinery for claims the review does not itself estimate
64- Treating a narrative review as exempt from any coverage account (the gap referees probe)
65- Running a meta-analysis with no deposited data/code or no stated protocol
66- Pooling incommensurable findings (qualitative, theoretical) into a single effect size
67- Documenting only the quantitative search and silently dropping the qualitative/theoretical sweep
6869## Output format
7071```text
72【Coverage account】databases + dates + terms + inclusion/exclusion + saturation + counts documented? Y/N
73【Mode coverage】qual / computational / demographic / theoretical search documented? Y/N
74【PRISMA】near-PRISMA narrative (or formal flow) prepared; format confirmed? Y/N · 待核实
75【Own analysis】meta-analysis/bibliometrics deposited with DOI + protocol? Y/N · n/a
76【Coding reproducibility】codebook lets a second coder re-derive codes? Y/N · n/a
77【Pre-empt】coverage account answers "why omit X?" before review? Y/N
78【Next step】→ arsoc-editor-strategy (scope + volume timeline) → arsoc-submission
79```
8081---
8283**Source:** [`brycewang-stanford/Awesome-Journal-Skills`](https://github.com/brycewang-stanford/Awesome-Journal-Skills) → `Annual-Review-of-Sociology-Skills/skills/arsoc-transparency-and-reproducibility/SKILL.md`
Run npx skillmds add thedixitjain/arsoc-transparency-and-reproducibility in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.
Use when documenting the coverage account of an Annual Review of Sociology (ARSoc) review and the transparency obligations of any systematic-review search or meta-analysis the review itself contains. Builds the search/selection record and the reproducibility plan; it does not gather the literature (arsoc-literature-synthesis) or appraise individual studies' designs (arsoc-comprehensiveness-and-balance). It is listed under Research & Search on SkillMD.
This skill has not completed SkillMD's automated safety review yet. Capability flags: makes network calls. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.
This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.
Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.
thedixitjain (@thedixitjain) published this skill. Their other Agent Skills are listed on their SkillMD profile.