# Write Nature-Ready Data Availability Statements

Researchers preparing Nature submissions struggle to produce compliant Data Availability statements. This skill provides structured guidance for repository selection, FAIR metadata, and bilingual wording.

## Install

```bash
npx skillstore add yuan1z skill, refactored into static/dynamic layers/yuan1z0825-nature-data
```

## Metadata

- - Slug: yuan1z0825-nature-data
- - Version: 2.0.0
- - Author: Yuan1z skill, refactored into static/dynamic layers
- - GitHub username: Yuan1z0825
- - License: MIT
- - Repository: https://github.com/Yuan1z0825/nature-skills/tree/main/skills/nature-data
- - Ref: main
- - Supported tools: Claude, Codex, Claude Code
- - Risk level: safe
- - Quality score: 81
- - Quality tier: silver
- - Public page: https://skillstore.pages.dev/skills/yuan1z0825-nature-data
- - Manifest: https://skillstore.pages.dev/api/skills/yuan1z0825-nature-data/manifest

## Capabilities

- Draft Data Availability statements matching Nature journal requirements
- Classify datasets into access routes \(public, controlled, within paper, third-party\)
- Recommend appropriate repositories and identifier strategies \(DOI, accession numbers\)
- Generate FAIR metadata checklists for dataset submissions
- Convert Chinese-language data notes into publication-ready English statements
- Provide ready-to-adapt statement patterns for common data scenarios

## Use Cases

- Prepare a Nature submission: Draft complete Data Availability statements and repository plans for a Nature-family manuscript submission.
- FAIR metadata audit: Review and improve dataset metadata to meet FAIR \(Findable, Accessible, Interoperable, Reusable\) standards.
- Chinese-English bilingual drafting: Convert Chinese-language research notes and data descriptions into Nature-compliant English availability statements.

## Prompt Templates

### Draft a basic Data Availability statement

```
Help me write a Data Availability statement for my Nature submission. My study generated RNA-seq data from 24 samples and uses a previously published reference dataset.
```

### Repository and identifier selection

```
I have three datasets: human genomic data (controlled access required), environmental metagenomics (public), and a custom analysis pipeline (code only). Recommend repositories and identifier types for each.
```

### FAIR metadata checklist review

```
Audit my dataset metadata against FAIR principles. Here are my current README contents and DataCite fields. Identify gaps and suggest improvements.
```

### Bilingual Chinese-English conversion

```
Convert this Chinese data availability note into a Nature-compliant English statement. The Chinese text describes our single-cell sequencing data deposited in GSA with restricted access for ethical reasons.
```

## Limitations

- Cannot verify or validate actual DOIs, accession numbers, or repository availability
- Does not check journal-specific requirements beyond Nature family guidelines
- Cannot access external repositories or fetch live metadata
- Provides templates and guidance, not legal or ethical compliance certification

## Best Practices

- Always classify each dataset into a specific access route before drafting the statement
- Include formal dataset citations with DOIs or accession numbers, not just repository names
- Flag 'available upon request' as a weak statement unless a specific restriction applies
- Verify repository suitability for your data type before recommending it

## Anti Patterns

- Inventing DOIs, accession numbers, or repository names that do not exist
- Using 'data are available upon reasonable request' without justification for the restriction
- Omitting dataset citations when datasets have been deposited in public repositories
- Applying generic statements without classifying individual dataset access requirements

## Security Audit

- - Safe to publish: true
- - Audited at: 2026-06-24T05:58:01.016\+00:00
- - Summary: This is a pure documentation and writing-assistance skill with no executable code. All 125 static findings are false positives triggered by markdown syntax: backticks in prose \(misread as shell execution\), mentions of data 'hash' or 'SHA' in FAIR metadata context \(misread as weak crypto\), and links to legitimate academic repositories like DataCite \(misread as hardcoded network endpoints\). No actual code execution, network calls, file system access, or cryptographic operations exist in this skill.

## Stats

- - Views: 0
- - Downloads: 0
- - Favorites: 0
- - Popularity score: 0