本文へ移動
cccskills
無料GitHub で公開

rseng-open-science-practices

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.

日本語の概要は準備中です。原文の説明を表示しています。

fdiblen/rseng-agent-skillsスター 24(GitHub 24 + cccskills 0)

実行スコア 未検証

インストール方法を見る

含まれるファイル(2)

  • SKILL.md6.1 KB
  • references.md422 B

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

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 REST API; bulk setup and link auditing are scriptable when a lab runs many projects.

Preregistration

A preregistration is a frozen, timestamped analysis plan filed BEFORE the data is seen - the strongest cheap defense against hindsight bias, and increasingly expected in several fields:

  • File it on OSF's registration system (or a domain registry); once registered it is immutable - that is the point.
  • The plan should be code-shaped where possible: hypotheses, exact variables, exclusion rules, models and inference criteria
    • ideally with the analysis script itself attached, run on simulated or pilot data (rseng-reproducibility's discipline applied before data collection; power-analysis code belongs here too).
  • Deviations happen legitimately: the practice is to REPORT them as deviations with reasons, not to hide them - preregistration separates confirmatory from exploratory, it does not forbid exploration.
  • Registered Reports go further: peer review of the plan before results exist, with in-principle acceptance - suggest the format when the field's journals offer it.

Preprints

  • Deposit at submission time (arXiv-class or domain servers; ASAPbio documents the landscape and journal policies) - a DOI'd preprint establishes priority and makes the work citable months or years early.
  • Check the target journal's preprint policy first (most allow it; a few constrain versions) and use the journal's own checking where unsure.
  • Link the chain: preprint to published version (servers support the link; OpenAlex tracks it - rseng-citation-hygiene uses this when verifying references), and both to the OSF project, data and code DOIs. The linked cluster IS the open research object.
  • Versioned preprints are normal; update after major revisions so readers land on current claims.

Open peer review and open participation

  • When venues offer open review, the practices from rseng-software-peer-review transfer: constructive, specific, evidence-based - with a name on it.
  • Review artifacts too: data and code review during peer review (CODECHECK-style execution) is open science applied to the evidence layer (rseng-software-peer-review, rseng-research-integrity).
  • Community review of preprints (public comments, review platforms) counts as scholarly contribution; encourage recording it (ORCID records review activity).

Keeping openness claims honest

Before submission or reporting, audit the claims: "data available at X" resolves and matches (rseng-archiving's verify step), "preregistered" links to the actual registration and deviations are reported, "code available" points at a tagged, licensed, citable release (rseng-publishing-releasing, rseng-licensing, rseng-citation-metadata). The open-science story is the sum of verifiable links - and AI contributions to any of it are declared in aidecl.yaml (rseng-ai-declaration).

Working with this skill

This skill is source-independent: its authority is the OSF and Center for Open Science documentation and ASAPbio resources linked below. It is the researcher-workflow face of what rseng-fair-software, rseng-reproducibility and rseng-archiving provide at the artifact level.

Learn more (verified):

<!-- related-skills:begin -->

Related skills

Check whether any of these applies before moving on:

  • rseng-archiving - both-ways artifact linking discipline
  • rseng-citation-hygiene - preprint-to-published version drift
  • rseng-publishing-releasing - citable code release behind claims
  • rseng-regulatory-compliance - governs the closed components
  • rseng-research-integrity - preregistration deviations reported honestly
  • rseng-software-peer-review - open review practices transfer
<!-- related-skills:end -->

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

コメント

ログインなしで書き込めます。使ってみた感想、質問、動かなかった環境などを気軽にどうぞ。

まだコメントはありません。最初のコメントを書いてみませんか。

送信するとすぐに公開されます。メールアドレスや電話番号などの個人情報は書かないでください。URL は 2 つまでです。

0 / 1000 文字

このフォームは reCAPTCHA で保護されており、Google のプライバシーポリシーと利用規約が適用されます。

同じリポジトリのスキル

Covers operating AI coding agents securely: auditing whether the agent runs sandboxed, permission and dangerous-command configuration, containerized environments, secrets kept out of context, network egress and token privileges, prompt-injection risk, and the privacy of agent use itself. Use PROACTIVELY when permission gating is broadly disabled (skip-permissions modes), when secrets are visible to the agent's shell, or when the agent processes untrusted code, issues or web content; when a project holds personal or confidential data while a cloud agent is active (what leaves the machine, retention, training use), or when the user asks how to run coding agents safely or privately. (Supply-chain security: rseng-security; disclosing agent contributions: rseng-ai-declaration.)

日本語の概要は準備中です。原文の説明を表示しています。

fdiblen/rseng-agent-skills242026年9月23日 更新

Covers declaring AI involvement with the AI Declaration Format (https://ai-declaration.org): creating and maintaining an aidecl.yaml that records which AI tools and agents were used, what each contributed, when and how much, plus the README disclosure footnote, JSON/JSON-LD export and CI validation. Machine-readable disclosure is the practice; this format is one implementation. Use PROACTIVELY when an AI assistant or agent creates or modifies a project's content - generate aidecl.yaml if missing, update it after AI-assisted changes. Also use when the user asks about AI transparency, provenance, disclosure or EU AI Act disclosure, wants to state that NO AI was used, or mentions aidecl. For concealment requests see rseng-honesty; for the human review duty see rseng-human-verification.

日本語の概要は準備中です。原文の説明を表示しています。

fdiblen/rseng-agent-skills242026年9月23日 更新

Covers long-term archiving of research software and data: Software Heritage save requests and SWHID persistent identifiers, Zenodo deposits with versioned DOIs and forge integration, choosing domain and institutional repositories, deciding what to archive (code, data, environments, documentation) and when, and archiving at project retirement. Use when the user wants software or data preserved beyond the life of a forge account, grant or lab, mentions Software Heritage, SWHIDs, Zenodo deposits or archiving, retires or hands over a project, prepares artifacts that must stay resolvable for a paper, or when funder policy requires long-term preservation. (Cutting the release itself is rseng-publishing-releasing; day-to-day data storage and repository choice is rseng-data-management.)

日本語の概要は準備中です。原文の説明を表示しています。

fdiblen/rseng-agent-skills242026年9月23日 更新

Covers processing research data that outgrows one machine's memory: out-of-core and chunked computation, Dask for scaling the scientific Python stack, Spark for distributed tabular pipelines, lazy evaluation, partitioning strategies, idempotent and restartable batch jobs, and knowing when NOT to distribute. Use when datasets no longer fit in memory, when the user mentions Dask, Spark, out-of-core or larger-than-memory data, when a pandas/NumPy workflow hits memory limits, or when designing batch pipelines over many files. (Cluster job submission and job arrays are rseng-hpc-computing; pipeline orchestration engines are rseng-workflows; profile first with rseng-performance-profiling.)

日本語の概要は準備中です。原文の説明を表示しています。

fdiblen/rseng-agent-skills242026年9月23日 更新

Covers continuous integration and delivery for research software: CI/CD concepts, automating builds and tests with GitHub Actions and GitLab CI/CD, and wiring an organization's GitLab CI infrastructure to a GitHub-hosted project. Use when the user asks to set up CI, write a pipeline or workflow file (.github/workflows, .gitlab-ci.yml), add automated builds/tests on push or pull request, publish a package or deploy docs when a tag or release is cut, cache dependencies to speed up CI runs, choose between GitHub Actions and GitLab CI, use self-hosted or GPU runners, mirror a repo, or report external CI status back to GitHub. For what to test and shrinking a test matrix see rseng-testing; for linter and pre-commit policy see rseng-code-quality.

日本語の概要は準備中です。原文の説明を表示しています。

fdiblen/rseng-agent-skills242026年9月23日 更新

Covers verifying that every citation is real, correct and current: checking references in manuscripts, READMEs, references files and code metadata against Crossref and OpenAlex, screening cited DOIs against the Retraction Watch database, catching fabricated or mis-attributed citations (a documented AI failure mode), and keeping bibliographies and CITATION.cff files resolvable. Use PROACTIVELY before any bibliography, reference list or citation metadata is finalized or published, whenever the agent itself has produced citations, and when the user asks to check references, mentions broken DOIs, retracted papers or citation verification, or prepares a manuscript, README or software paper with references. (Making your own software citable is rseng-citation-metadata.)

日本語の概要は準備中です。原文の説明を表示しています。

fdiblen/rseng-agent-skills242026年9月23日 更新

fdiblen のスキルをすべて見る

このスキルの問題を報告する