sf-data-and-transparency
Use when preparing the data, code, and transparency materials for a Social Forces (SF) manuscript. SF requires a data availability statement on every published paper and encourages deposit in a public repository where ethically feasible. Covers quantitative and qualitative transparency and restricted-data paths; it does not waive requirements.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill sf-data-and-transparency --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.
# Data & Transparency (sf-data-and-transparency) Social Forces makes one transparency requirement explicit: **"The inclusion of a data availability statement is a requirement for papers published in the Journal."** Unlike journals that run an editor-verified pre-publication replication, SF asks for a clear **statement** plus deposit **where ethically feasible**. Treat the statement as a real deliverable and build the materials as you go so it is honest and complete. ## When to trigger - Drafting the **data availability statement** (required for publication) - Deciding where and how to deposit data and code - Data cannot be fully shared (privacy, ethics, legal/provider restrictions) and you need the right wording - Documenting qualitative or restricted sources to support the claims ## What SF requires (verify current wording on the policy page) 1. **Data availability statement.** Every published paper carries one. It should describe whether and how the data underlying the results are available — repository name, persistent identifier or accession number, or the access process for restricted data. 2. **Deposit where ethically feasible.** Authors are encouraged to deposit data (and id
- When to trigger
- What SF requires (verify current wording on the policy page)
- When data cannot be shared (restricted-data path)
- Qualitative / restricted transparency
- Build-as-you-go checklist
- Anti-patterns
- Choosing the right data-availability path
- Worked vignette (illustrative)
- Output format
- Supplementary resources
What does the sf-data-and-transparency skill do?
Use when preparing the data, code, and transparency materials for a Social Forces (SF) manuscript. SF requires a data availability statement on every published paper and encourages deposit in a public repository where ethically feasible. Covers quantitative and qualitative transparency and restricted-data paths; it does not waive requirements.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill sf-data-and-transparency --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.