paper-data-availability

name	paper-data-availability
description	Use when drafting, auditing, or improving data availability statements, code availability statements, FAIR metadata, dataset access routes, repository choices, restrictions, identifiers, and result-to-data traceability.

Paper Data Availability

Use this skill when a paper needs data/code availability statements or when results must be mapped to accessible evidence.

Inputs

• Manuscript results, figures, tables, or supplementary claims.
• Dataset names and source locations.
• Code repository or analysis scripts if available.
• Access restrictions, privacy constraints, or licensing constraints.

Workflow

1. List every dataset or code artifact supporting a result.
2. Map each artifact to figures, tables, or claims.
3. Identify access route: public repository, controlled access, request to authors, proprietary, or unavailable.
4. Record identifiers: DOI, accession, commit hash, archive URL, or planned persistent ID.
5. Check README, data dictionary, licence, and reuse conditions.
6. Draft a data/code availability statement.
7. Flag missing author actions.

Data Gate

• Every result-supporting dataset has an access route.
• Restrictions are explained, not hidden.
• Public data includes identifier and repository.
• Code availability includes commit, release, or archive plan.
• Reuse conditions are stated when known.

When To Read References

• For statement patterns, read references/availability-patterns.md.