nature-data

Drafts and audits Nature-ready Data Availability statements from bilingual notes.

Updated May 21, 2026
One-click install
npx skills add https://github.com/Liangxianguang/helpfulskills --skill nature-data-liangxianguang
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nature-data
Source: https://github.com/Liangxianguang/helpfulskills/tree/main/nature-skills/skills/nature-data
Command: npx skills add https://github.com/Liangxianguang/helpfulskills --skill nature-data-liangxianguang

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Nature-family submissions often require precise, submission-ready Data Availability statements and dataset citations, but authors may have only informal Chinese notes or incomplete/weak wording. This skill helps convert that input into a Nature-ready English package while auditing for missing identifiers, repositories, licenses, and access routes.

Core Features & Use Cases

  • Manuscript-ready Data Availability drafting: Produces ready-to-paste Data Availability text and a repository/data mapping aligned with Nature Portfolio expectations.
  • FAIR and DataCite-style metadata auditing: Flags weak, missing, or inconsistent metadata fields (e.g., accession/DOI, licensing, provenance, embargo/access conditions).
  • Bilingual-aware Chinese author mode: Converts Chinese “data availability intent” into precise English wording, and outputs a short Chinese confirmation checklist for unresolved fields.
  • Dataset citation preparation: Helps generate repository and dataset citation actions, ensuring the statement can be backed by stable records.

Quick Start

Draft and audit a Nature-ready Data Availability statement from my Chinese data-sharing notes, including English text plus a Chinese checklist of what I still need to confirm.

Frequently Asked Questions about nature-data

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write a Nature-ready data availability statement for my manuscript submission?

To write a Nature-ready data availability statement, you map manuscript data notes to specific availability routes, assign datasets to repositories, and generate submission-ready text with risk flags for missing identifiers or access terms.

Can I convert informal Chinese data sharing notes into a FAIR metadata checklist?

Yes, you can convert Chinese data sharing notes into a FAIR metadata checklist by auditing author intent, translating it into precise English statements, and outputting a Chinese confirmation checklist for unresolved fields like accession numbers and licenses.

What is the best way to handle restricted data and controlled-access datasets for journal submissions?

The best way to handle restricted data for journal submissions is to explicitly define controlled-access routes, avoid fabricating access terms, and replace weak phrasing like available on request with precise DataCite-aligned metadata and repository conditions.

How do I map accession numbers and DOIs when preparing dataset citations?

You map accession numbers and DOIs by auditing supporting datasets against repository records, ensuring stable identifiers are linked to specific availability routes, and generating ready-to-paste citations backed by FAIR metadata.

Why does my data availability statement get flagged for missing identifiers during repository selection?

Your data availability statement gets flagged for missing identifiers when the audit detects incomplete provenance, absent DOIs, or undefined licenses. It assigns missing-information risk flags to ensure compliance before submission.