Data Availability
Overview
Use this skill to turn manuscript-supporting data into a submission-ready availability package: statement text, repository plan, source-data mapping, and unresolved-risk flags.
This skill is narrower than submission-audit and more operational than scientific-writing. Use it when the bottleneck is no longer the paper's story, but whether the data-sharing package is specific, durable, and journal-ready.
When To Use
Use this skill when:
- the manuscript needs a
Data Availability statement
- accession numbers, DOIs, repository records, or source-data files are missing or unstable
- the paper mixes generated data, reused public data, and restricted data
- "available upon request" wording needs to be tightened or replaced
- a submission or revision needs data-sharing text that editors can audit quickly
Do not use this skill for:
- generic section rewriting unrelated to data sharing
- full manuscript restructuring
- bibliography cleanup that does not affect dataset availability
Workflow
- Identify the target journal and article type.
- Inventory the datasets that support the main and supplementary claims:
- raw data
- processed data
- figure source data
- reused public datasets
- code-adjacent outputs that are necessary to inspect the results
- Assign each dataset one access route only:
- public repository
- controlled-access repository
- within paper or supplement
- reused public source
- third-party restricted
- justified request route
- Choose repository and identifier strategy before drafting the statement.
- Draft explicit dataset-to-location wording.
- Check that the statement covers both newly generated and reused data.
- Flag unresolved fields rather than inventing repository names, accession IDs, DOIs, or access rules.
Working Rules
- Prefer public, discipline-specific repositories when possible.
- Treat
available upon request as weak unless a real legal, ethical, commercial, or third-party restriction exists.
- If data cannot be public, state:
- why access is restricted
- who controls access
- how requests are reviewed
- what metadata, source data, or derived data remain public
- Do not merge data, code, protocols, and materials into one vague availability sentence unless the journal explicitly wants that.
- Do not invent accession numbers, DOIs, repository names, reviewer links, or embargo terms.
Related Files
Open these only when needed:
references/statement-patterns.md
Use when drafting or repairing the actual statement text.
references/repository-routing.md
Use when deciding where each dataset should live and what identifier type is needed.
references/source-data-checks.md
Use when checking whether figures, tables, and supplements expose enough underlying data.
references/fair-metadata-checklist.md
Use when the journal expects FAIR or DataCite-style dataset metadata, or a formal dataset citation.
references/chinese-author-alignment.md
Use when aligning a Chinese-language data-availability draft to English submission wording.
Output Standard
When using this skill, return:
- ready-to-paste
Data Availability text
- repository and identifier actions still required
- missing information or blocking risks
- a short note on whether the current package is:
ready_to_submit
draft_with_placeholders
needs_author_input
blocked
1---2name: data-availability3description: Use when drafting, auditing, or revising Data Availability statements, repository plans, accession-number placement, source-data coverage, or restricted-data wording for journal submission or resubmission.4metadata:5 source: https://skillmd.com/skills/boom5426/data-availability6---78# Data Availability910## Overview1112Use this skill to turn manuscript-supporting data into a submission-ready availability package: statement text, repository plan, source-data mapping, and unresolved-risk flags.1314This skill is narrower than `submission-audit` and more operational than `scientific-writing`. Use it when the bottleneck is no longer the paper's story, but whether the data-sharing package is specific, durable, and journal-ready.1516## When To Use1718Use this skill when:19- the manuscript needs a `Data Availability` statement20- accession numbers, DOIs, repository records, or source-data files are missing or unstable21- the paper mixes generated data, reused public data, and restricted data22- "available upon request" wording needs to be tightened or replaced23- a submission or revision needs data-sharing text that editors can audit quickly2425Do not use this skill for:26- generic section rewriting unrelated to data sharing27- full manuscript restructuring28- bibliography cleanup that does not affect dataset availability2930## Workflow31321. Identify the target journal and article type.332. Inventory the datasets that support the main and supplementary claims:34 - raw data35 - processed data36 - figure source data37 - reused public datasets38 - code-adjacent outputs that are necessary to inspect the results393. Assign each dataset one access route only:40 - public repository41 - controlled-access repository42 - within paper or supplement43 - reused public source44 - third-party restricted45 - justified request route464. Choose repository and identifier strategy before drafting the statement.475. Draft explicit dataset-to-location wording.486. Check that the statement covers both newly generated and reused data.497. Flag unresolved fields rather than inventing repository names, accession IDs, DOIs, or access rules.5051## Working Rules5253- Prefer public, discipline-specific repositories when possible.54- Treat `available upon request` as weak unless a real legal, ethical, commercial, or third-party restriction exists.55- If data cannot be public, state:56 - why access is restricted57 - who controls access58 - how requests are reviewed59 - what metadata, source data, or derived data remain public60- Do not merge data, code, protocols, and materials into one vague availability sentence unless the journal explicitly wants that.61- Do not invent accession numbers, DOIs, repository names, reviewer links, or embargo terms.6263## Related Files6465Open these only when needed:6667- `references/statement-patterns.md`68 Use when drafting or repairing the actual statement text.69- `references/repository-routing.md`70 Use when deciding where each dataset should live and what identifier type is needed.71- `references/source-data-checks.md`72 Use when checking whether figures, tables, and supplements expose enough underlying data.73- `references/fair-metadata-checklist.md`74 Use when the journal expects FAIR or DataCite-style dataset metadata, or a formal dataset citation.75- `references/chinese-author-alignment.md`76 Use when aligning a Chinese-language data-availability draft to English submission wording.7778## Output Standard7980When using this skill, return:81- ready-to-paste `Data Availability` text82- repository and identifier actions still required83- missing information or blocking risks84- a short note on whether the current package is:85 - `ready_to_submit`86 - `draft_with_placeholders`87 - `needs_author_input`88 - `blocked`