zenodo-skilllisted

# Zenodo Skill Interact with the [Zenodo REST API](https://developers.zenodo.org) to deposit, publish, version, and search research artifacts. Zenodo issues a citable DOI for every published record. ## When to use - User wants to upload a dataset, code release, paper, poster, or other artifact to Zenodo - User wants a DOI for a research output - User wants to update an existing deposit or publish a new version - User wants to search Zenodo for records ## Setup Two environments — pick one and stick with it during a session: | Env | Base URL | Token page | |---|---|---| | Production | `https://zenodo.org/api` | https://zenodo.org/account/settings/applications/tokens/new/ | | Sandbox (testing) | `https://sandbox.zenodo.org/api` | https://sandbox.zenodo.org/account/settings/applications/tokens/new/ | Sandbox accounts/tokens are **separate** from production. Always test new workflows in sandbox first — published production records cannot be deleted. Required token scopes: `deposit:write` and `deposit:actions`. Export the token before running commands: ```bash export ZENODO_TOKEN=... # never inline the token in commands you show the user export ZENODO_BASE=https://sandbox.zenodo.org/api # or https://zenodo.org/api ``` If `ZENODO_TOKEN` is unset, ask the user for it (and which environment) before proceeding. ## Core workflow: deposit a new artifact The deposit lifecycle is **create → upload files → set metadata → publish**. Each step is a separate API call; do t