Skip to content
Back to skills

Io Conversion

ASecurity

"Open, convert, export, and validate local and optional remote

  • 247 stars
  • 0 votes
  • 0 copies
  • 3 views
  • Added September 9, 2026
toolsrustexpressapi

Works with

  • cli
  • api

Security analysis

A100/100

Pro scans all 7 files and shows the line behind each finding

Scanned September 9, 2026

npx -y skills add VectorSpaceLab/AREX-Skill --skill io-conversion --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Io Conversion?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Io Conversion
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/vectorspacelab-io-conversion/badge)](https://www.skillsdirectory.com/skills/vectorspacelab-io-conversion)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: io-conversion
description: "Open, convert, export, and validate local and optional remote
  tabular data with Vaex."
disable-model-invocation: true
metadata:
  disco-role: operating
license: MIT
---

# IO Conversion

Use this sub-skill when the task is about getting tabular data into or out of
Vaex: opening local files, converting CSV/Arrow/Parquet/Feather/HDF5, exporting
DataFrames, checking roundtrips, or diagnosing format-specific failures.

## Route first

- For generic DataFrame construction, lazy DataFrame semantics, virtual columns,
  selections, and basic inspection, route to `../dataframe-core/SKILL.md`.
- For overall `vaex` command discovery, settings, aliases, environment variables,
  and non-conversion CLI commands, route to `../cli-settings/SKILL.md`.
- For expression syntax, filters used in conversion, groupby/binby/aggregation,
  joins, and analytic validation, route to `../expressions-analytics/SKILL.md`.
- Stay here for `vaex.open`, `open_many`, `from_csv`, `from_csv_arrow`,
  `from_pandas`, `from_arrow_table`, `df.export*`, `df.to_arrow_table`, local
  astro file openers, cloud path caveats, and `vaex convert` data semantics.

## Read order

1. `references/io-workflows.md` for actionable open/convert/export recipes,
   API signatures, `vaex convert` options, and roundtrip checks.
2. `references/data-formats.md` for format selection, memory-mapping behavior,
   schema caveats, and Pandas/Arrow/HDF5 handoff details.
3. `references/astro-and-cloud-io.md` for optional local astro formats and
   remote/cloud/TAP skip conditions. Do not run network or credentialed checks
   unless the user explicitly authorizes them.
4. `references/troubleshooting.md` when `vaex.open` fails, a plugin is missing,
   a CSV conversion is memory-heavy, conversion cleanup is surprising, or a file
   opens in Pandas but not in Vaex.

## Safe bundled helpers

- `scripts/io_roundtrip_smoke.py` creates tiny local data, exercises Vaex export
  and open roundtrips, and validates Pandas/Arrow table handoffs. It never uses
  network paths.
- `scripts/convert_csv_hdf5.py` converts a local CSV to Vaex HDF5 with optional
  column selection, filtering, sorting, fractioning, chunk size, listing, dry
  run, and safe partial-output handling. It rejects remote paths.

Run both helpers with `--help` first. They are safe from arbitrary working
directories and use installed public Vaex APIs rather than source-checkout files.

## Operating rules

- Prefer memory-mappable Vaex HDF5 or Arrow-family files for repeated large-data
  work; treat CSV as an ingestion/interchange format and convert when the same
  data will be queried repeatedly.
- Use `vaex.open(path)` for lazy file-backed access when the format is supported;
  use `vaex.open(path, convert="data.hdf5")` or the bundled conversion helper for
  large CSVs that need a faster local binary representation.
- Validate every conversion with at least: row count, column names, a small sample
  or checksum-like aggregate, and the exact group or file pattern used.
- Treat cloud storage, TAP, and credentialed URLs as optional trust-boundary work.
  Document the plan and skip by default in automated scripts.
- Never assume a Pandas-created HDF5 file is Vaex-readable. Convert through
  `vaex.from_pandas(...).export_hdf5(...)` when the source HDF5 layout is row
  oriented or otherwise Pandas-specific.

Files in this skill

  • SKILL.md3.3 KB
  • references/astro-and-cloud-io.md5.7 KB
  • references/data-formats.md8.4 KB
  • references/io-workflows.md12.2 KB
  • references/troubleshooting.md7.8 KB
  • scripts/convert_csv_hdf5.py11.2 KB
  • scripts/io_roundtrip_smoke.py6.7 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.