Agent skill · Data & Analytics

cogpsych-open-science-and-transparency

Use when meeting Cognitive Psychology (Elsevier) open-science expectations — sharing data, model code, analysis scripts, and materials so the modeling is reproducible, depositing in repositories with persistent identifiers, completing the Elsevier research-data and competing-interest declarations, and preregistering where applicable. Prepares compliance; it does not waive requirements. Verify current wording on the official guide for authors.

brycew6m878★ · +32/wk · 1 repos on radarProfile →
claude-codeMIT
Install
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill cogpsych-open-science-and-transparency --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 7 KB
Bundled scripts: none
Path: Cognitive-Psychology-Skills/skills/cogpsych-open-science-and-transparency/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 909 · +31 this week
Language: Stata
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Open Science & Transparency (cogpsych-open-science-and-transparency) Because the contribution is a **model fit to data**, reproducibility here means more than open data: it means the **model code and analysis scripts regenerate every reported fit**. Authors are strongly encouraged to share data, model code, and materials. This skill prepares the deposits and the Elsevier declarations early, so the modeling is reproducible at submission rather than promised at acceptance. Confirm the current policy wording on the journal's guide for authors (检索于 2026-06;以官网为准). ## When to trigger - Building the data, model-code, and materials deposits - Completing Elsevier's research-data statement and competing-interest declaration - Deciding whether (and how) to claim a restriction on sharing sensitive/third-party data - Linking a preregistration and reporting its status - A reviewer or editor flagged transparency or reproducibility ## What to prepare (verify current wording on the official page) 1. **Open data.** Deposit trial-level data with a **codebook/data dictionary** in a repository that mints a **persistent identifier (DOI)** (OSF, Mendeley Data, Dataverse, Zenodo). State availability in

What's inside
Steps it walks through
  1. When to trigger
  2. What to prepare (verify current wording on the official page)
  3. Build-it-right checklist
  4. Restrictions (handle honestly)
  5. Reproducibility statement — worked draft (illustrative)
  6. Transparency-readiness decision table
  7. Reviewer / editor pushback and the venue fix
  8. Anti-patterns
  9. Output format
  10. Supplementary resources
More from Awesome-Journal-Skills
All skills →
About this skill
What does the cogpsych-open-science-and-transparency skill do?

Use when meeting Cognitive Psychology (Elsevier) open-science expectations — sharing data, model code, analysis scripts, and materials so the modeling is reproducible, depositing in repositories with persistent identifiers, completing the Elsevier research-data and competing-interest declarations, and preregistering where applicable. Prepares compliance; it does not waive requirements. Verify current wording on the official guide for authors.

How do I install it?

Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill cogpsych-open-science-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.

Keep going