Exploratory Data Analysis
spacering-net/codeg
Perform comprehensive exploratory data analysis on scientific data files across 200+ file formats.
Release one or more datasets by adding them to a topical collection, bumping coverage.start, and verifying.
Install Release Datasets
$ npx skills add opensanctions/opensanctions --skill release-datasets -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install opensanctions/opensanctions release-datasets --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/opensanctions/opensanctions.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/release-datasets .claude/skills/release-datasets && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "release-datasets" agent skill from https://github.com/opensanctions/opensanctions/tree/main/.claude/skills/release-datasets into .claude/skills/release-datasets/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-datasets", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/opensanctions/opensanctions/tree/main/.claude/skills/release-datasetsType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add opensanctions/opensanctions --skill release-datasets -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install opensanctions/opensanctions release-datasets --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/opensanctions/opensanctions.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/release-datasets .agents/skills/release-datasets && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "release-datasets" agent skill from https://github.com/opensanctions/opensanctions/tree/main/.claude/skills/release-datasets into .agents/skills/release-datasets/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-datasets", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add opensanctions/opensanctions --skill release-datasets -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install opensanctions/opensanctions release-datasets --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/opensanctions/opensanctions.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/release-datasets .cursor/skills/release-datasets && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "release-datasets" agent skill from https://github.com/opensanctions/opensanctions/tree/main/.claude/skills/release-datasets into .cursor/skills/release-datasets/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-datasets", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/opensanctions/opensanctions.git --path .claude/skills/release-datasets--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add opensanctions/opensanctions --skill release-datasets -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install opensanctions/opensanctions release-datasets --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/opensanctions/opensanctions.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/release-datasets .gemini/skills/release-datasets && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "release-datasets" agent skill from https://github.com/opensanctions/opensanctions/tree/main/.claude/skills/release-datasets into .gemini/skills/release-datasets/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-datasets", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install opensanctions/opensanctions release-datasetsInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add opensanctions/opensanctions --skill release-datasets -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/opensanctions/opensanctions.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/release-datasets .github/skills/release-datasets && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "release-datasets" agent skill from https://github.com/opensanctions/opensanctions/tree/main/.claude/skills/release-datasets into .github/skills/release-datasets/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-datasets", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add opensanctions/opensanctions --skill release-datasets -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install opensanctions/opensanctions release-datasets --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/opensanctions/opensanctions.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/release-datasets .opencode/skills/release-datasets && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "release-datasets" agent skill from https://github.com/opensanctions/opensanctions/tree/main/.claude/skills/release-datasets into .opencode/skills/release-datasets/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-datasets", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
release-datasets- GitHub stars
- 832
- Token cost
- ~566 tokens
- SKILL.md length
- 244 words
- Files
- 1
- Skills in repo
- 11
- Repo updated
- First seen
- Licence
- MIT
At a glance
Release one or more datasets by adding them to a topical collection, bumping coverage.start, and verifying.
- Works in 2 steps: Only release the datasets the user… → Determine the target collection for each…
- The user wants to release/publish specific crawled datasets into the OpenSanctions product
- SKILL.md covers Before following the doc, When editing and Commit
- Calls python
What it does
Release Datasets is an agent skill from opensanctions/opensanctions. Release one or more datasets by adding them to a topical collection, bumping coverage.start, and verifying. Use when the user wants to release/publish specific crawled datasets into the OpenSanctions product.
Its SKILL.md is about 570 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Data & Analytics. The repository describes itself as: An open database of international sanctions data, persons of interest and politically exposed persons. The licence is MIT.
When your agent uses it
- The user wants to release/publish specific crawled datasets into the OpenSanctions product
Example prompts
- “/release-datasets”
Requirements
- Python 3
Workflow steps
2 steps, taken from the first numbered list in SKILL.md.
- Only release the datasets the user explicitly lists. Never release every
- Determine the target collection for each dataset.
What it can do on your machine
Read from SKILL.md and the folder at commit ce59ef9. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
python
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Release Datasets loads about 566 tokens when it runs. Until then it costs about 56 tokens; SKILL.md has 244 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from opensanctions/opensanctions at commit ce59ef9, republished under its MIT licence (© opensanctions). 244 words, ~566 tokens.
Download SKILL.mdSave it as
.claude/skills/release-datasets/SKILL.md (or your agent's skills folder).- name
- release-datasets
- description
- Release one or more datasets by adding them to a topical collection, bumping coverage.start, and verifying. Use when the user wants to release/publish specific crawled datasets into the OpenSanctions product.
Release Datasets
Release the datasets the user names into the OpenSanctions product. The datasets to release: $ARGUMENTS
The full release process — how collections work, choosing a collection, the
edit steps, and verification — is documented in
zavod/docs/best_practices/release.md.
Read that doc and follow it. This skill only covers how to drive it.
Before following the doc
Only release the datasets the user explicitly lists. Never release every unreleased dataset in the pipeline — most are work in progress or test scratch and are unreleased on purpose. If the user gave no list, ask which datasets they want to release before doing anything.
Determine the target collection for each dataset.
- If the user specified one, use it.
- If not, suggest one from the dataset's topic — inspect its
.ymltags:(e.g.list.pep),summary/description, and the entities it emits, then match against the collection table inrelease.md. Confirm the suggestion with the user before editing; don't guess silently.
When editing
- Follow the steps in
release.md: add the dataset to the collection'schildren:(alphabetically sorted), bumpcoverage.startto today, and verify withpython contrib/check_hierarchy.py datasets. - Preserve each dataset file's existing date quoting style when bumping
coverage.start(some files quote the date, some don't). - After editing a collection, sanity-check it stays sorted and dupe-free:
python -c "import yaml; c=yaml.safe_load(open('datasets/_collections/<collection>.yml'))['children']; assert c==sorted(c) and len(c)==len(set(c)); print('ok', len(c))"
Commit
Group the collection edit and the coverage bumps together. Use the house
[dataset_name] commit-title prefix (one dataset → [xx_foo] Release into peps;
several → describe the batch). Do not push during an in-flight session without
explicit confirmation.
© opensanctions, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .claude/skills/release-datasets of opensanctions/opensanctions.
Open the folder on GitHubat commit ce59ef9
Compare with similar skills
Release Datasets next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Release Datasets this skillopensanctions/opensanctions | 832 | — | ~566 | Automated safety check: Pass | MIT | |
| Exploratory Data Analysisspacering-net/codeg | 3.8k | 15 repos | ~3.6k | Automated safety check: Pass | MIT | |
| MatplotlibzLanqing/codex-claude-academic-skills | 4.6k | 18 repos | ~2.9k | Automated safety check: Pass | MIT | |
| Scikit LearnzLanqing/codex-claude-academic-skills | 4.6k | 17 repos | ~3.9k | Automated safety check: Pass | BSD-3-Clause | |
| Chart Visualizationbytedance/deer-flow | 83k | 2 repos | ~840 | Automated safety check: Pass | MIT | |
| TimesFM Forecastinggoogle-research/timesfm | 34k | — | ~4.7k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Matplotlib
zLanqing/codex-claude-academic-skills
Low-level plotting library for full customization. An agent skill from zLanqing/codex-claude-academic-skills.
Scikit Learn
zLanqing/codex-claude-academic-skills
Machine learning in Python with scikit-learn. An agent skill from zLanqing/codex-claude-academic-skills.
Chart Visualization
bytedance/deer-flow
Picks a suitable chart type from 26 options for your data, maps the data to that chart's parameters and generates a chart image through a JavaScript script.
TimesFM Forecasting
google-research/timesfm
Forecasts any univariate time series zero-shot with Google's TimesFM model, returning point forecasts and calibrated prediction intervals without training.
- Official
Sandbox Bench
vercel/next.js
Benchmark React or Next.js changes on Vercel Sandbox VMs with paired A/B statistics: react PR/commit vs base, or Next.js PR/commit vs base, measured end-to-end through the bench/render-pipeline app…
More from opensanctions/opensanctions
All 11 skills in this repoCrawler Pep
opensanctions/opensanctions
Scaffold a new PEP (Politically Exposed Persons) crawler — members of a parliament, legislature, senate, chamber of deputies, cabinet, judiciary, or an asset-declaration register — from a source URL…
Crawler Constants To Yml
opensanctions/opensanctions
Move hardcoded lookup/config constants (gender maps, header dicts, value translations, column-label maps, date formats) out of a crawler and into the dataset .yml — as datapatch lookups wherever…
Dataset Metadata
opensanctions/opensanctions
Bring a dataset .yml's metadata in line with house conventions (title, summary, description, coverage, publisher, maintainer comments).
Legislature Metadata
opensanctions/opensanctions
Refactor the title, description and coverage frequency of a legislature/parliament PEP dataset .yml into the house style.
Name Framework Migration First Step
opensanctions/opensanctions
Migrate ad-hoc name cleaning in a crawler to h.reviewnames (Step 1 of the name framework migration).
Refactor Crawler
opensanctions/opensanctions
Rewrite messy or AI-generated crawler code into clean, production-ready style that follows the zavod best practices.
Related
Categories
Questions about Release Datasets
What does Release Datasets do?
Release one or more datasets by adding them to a topical collection, bumping coverage.start, and verifying. Release Datasets is an agent skill from opensanctions/opensanctions.start, and verifying.
When should I use Release Datasets?
Release Datasets fits situations like: the user wants to release/publish specific crawled datasets into the OpenSanctions product.
How do I install Release Datasets in Claude Code?
Run `npx skills add opensanctions/opensanctions --skill release-datasets -a claude-code`. Or copy the skill folder (.claude/skills/release-datasets in opensanctions/opensanctions) into .claude/skills/release-datasets in your project. Claude Code loads it when a task matches its description.
How do I install Release Datasets in Codex?
Run `npx skills add opensanctions/opensanctions --skill release-datasets -a codex`. Or copy the skill folder (.claude/skills/release-datasets in opensanctions/opensanctions) into .agents/skills/release-datasets in your project. Codex loads it when a task matches its description.
Can I use Release Datasets in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add opensanctions/opensanctions --skill release-datasets -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/release-datasets, .gemini/skills/release-datasets, .github/skills/release-datasets and .opencode/skills/release-datasets in your project.
What does Release Datasets need to run?
Going by SKILL.md and its folder, Release Datasets needs the command-line tools its instructions call (python). Our summary lists: Python 3.
Does Release Datasets access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Release Datasets safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Release Datasets use?
Release Datasets is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Release Datasets use?
About 566 tokens (SKILL.md is roughly 2.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Release Datasets?
Skills that share tags, products or a category with Release Datasets: Exploratory Data Analysis (spacering-net/codeg, 3.8k stars), Matplotlib (zLanqing/codex-claude-academic-skills, 4.6k stars), Scikit Learn (zLanqing/codex-claude-academic-skills, 4.6k stars) and Chart Visualization (bytedance/deer-flow, 83k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Release Datasets?
opensanctions (a GitHub organization) maintains it in opensanctions/opensanctions, which has 832 GitHub stars. The repository holds 11 skills in this directory. The repository was last updated on October 8, 2026.
Source: opensanctions/opensanctions on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.