Science Data Code

Science Data and Code

Use this skill to connect the manuscript's claims to inspectable data, code, materials, and metadata. Treat availability as part of the evidence chain.

Default stance

• Do not invent DOIs, accession numbers, repository records, licenses, embargoes, ethics

approvals, access committees, or code status.

• Prefer public, stable, discipline-appropriate repositories.
• Separate data, code, materials, protocols, models, and third-party resources.
• Flag available upon reasonable request as weak unless there is a clear legal, ethical,

commercial, privacy, or third-party restriction.

• Verify current target-journal policy before final submission wording.

Open extra files

| File | Open when | |---|---| | [references/availability-patterns.md](references/availability-patterns.md) | Need ready-to-adapt data/code/materials statement patterns | | [references/repository-checklist.md](references/repository-checklist.md) | Need repository, identifier, license, metadata, or FAIR checks | | [references/source-basis.md](references/source-basis.md) | Need source hierarchy or policy-vs-advice boundaries |

Workflow

1. Identify target journal and article type.
2. Inventory every asset needed to support the main and supplementary claims:

raw data, processed data, figure source data, code, scripts, models, protocols, materials, third-party datasets, and restricted data.

1. Map each asset to one access route:

public repository, controlled access, within paper/supplement, reused public source, third-party restricted, available on justified request, or not yet provided.

1. Choose a repository and identifier strategy before drafting.
2. Draft data/code/materials availability text with asset-to-location mapping.
3. Add missing-information flags.
4. Run the FAIR/reproducibility checklist.

Output format

Data and code availability
[ready-to-paste statement]

Asset map
| Asset | Supports claim/figure | Location | Identifier | Access conditions | Missing info |

Repository actions
- [specific actions]

Risk flags
- [specific flags or "None"]

For Chinese author notes, provide the submission-ready English statement first, then a short Chinese checklist of author actions.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

• Author: shikaijieskj
• Source: shikaijieskj/science-skills
• License: MIT

Install and usage instructions live in the source repository linked above.