rseng-open-science-practices

Solid

Covers the researcher-facing open science workflow: setting up OSF projects that link materials, data, code and registrations, preregistering studies and analysis plans, depositing preprints and linking them to published versions, participating in open peer review, and choosing openness levels honestly. Use when the user mentions open science, OSF, preregistration, registered reports or preprints, wants their research process (not just the software) open, asks where to preregister or preprint, or when a project's openness claims should become verifiable practice.

AI & Automation 14 stars 2 forks Updated 4 days ago MIT

Install

View on GitHub

Quality Score: 83/100

Stars 20%
39
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# Open science practices Open science extends what this pack does for software to the whole research workflow: materials, data, analysis plans, manuscripts and reviews, open by default and closed only with reasons. For an agent the job is concrete plumbing, not advocacy: set up the platforms, wire the links between artifacts, and make each openness claim verifiable. The payoff structure is worth stating when relevant: preregistration protects claims from hindsight, preprints establish priority and speed feedback, open materials earn reuse and citations - openness is self-interest aligned with integrity. ## The OSF project as the hub The Open Science Framework (osf.io, run by the Center for Open Science) is the general-purpose spine for open projects: - Structure: one OSF project per study, with components for materials, data, analysis code and preregistration; connect the code repository rather than copying it (OSF links forges; the repository stays the working home - rseng-version-control-review). - Every component gets a persistent identifier and citation; wire these into the paper and the repository README so artifacts reference each other both ways (the same both-ways discipline as rseng-archiving). - Access control is per-component: public materials next to embargoed data next to private drafts is a normal shape - "as open as possible, as closed as necessary", with reasons stated (rseng-regulatory-compliance governs the closed parts). - OSF has a ...

Details

Author
fdiblen
Repository
fdiblen/rseng-agent-skills
Created
4 days ago
Last Updated
4 days ago
Language
Python
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Solid

rseng-fair-software

Covers how to apply the FAIR principles - findable, accessible, interoperable, reusable - to research software, and how to assess a project's FAIRness. Use when the user asks how to make software FAIR, wants help with findability, discoverability, or software reuse, mentions metadata, persistent identifiers, DOIs, registries, or software citation in a FAIR context, or asks to run a FAIR self-assessment or checklist on a repository. (Automated FAIR4RS scoring, compliance levels and CI gates with the FAIRGuard tool are rseng-fairguard; FAIR for ML models and datasets is rseng-fair-ml; finding existing software to reuse is rseng-software-reuse.)

14 Updated 4 days ago
fdiblen
AI & Automation Solid

rseng-community-governance

Covers building and governing a community around research software: CONTRIBUTING guides, codes of conduct, governance models and decision-making, contributor recognition policy, issue and discussion hygiene, and handing over or sharing maintainership. Use when a project wants external contributors, when the user asks for a CONTRIBUTING.md, code of conduct or governance document, when maintainer burnout or bus-factor risks come up, or when a project is moving from single-author to team or community ownership. The contributor funnel and good-first-issue curation live in rseng-contributor-onboarding; health measurement in rseng-community-metrics; support operations in rseng-user-support.

14 Updated 4 days ago
fdiblen
AI & Automation Listed

pre-registration-writing

Write pre-analysis plans and preregistrations. Use for PAP structure, registry requirements, estimands, analysis strategy, exclusions, and deviation planning.

55 Updated yesterday
scdenney