convert-file
Convert any data file to another format—CSV, Parquet, JSON, Excel, GeoJSON, and more—in a single DuckDB command. Handles both local and remote files, with support for partitioning and compression options when needed.
convert-file transforms data files between formats like CSV, Parquet, JSON, and Excel using DuckDB.
AI-generated summary based on this skill's SKILL.md
Decision gist · record as of 2026-04-23
convert-file transforms data files between formats like CSV, Parquet, JSON, and Excel using DuckDB. Convert any data file to another format—CSV, Parquet, JSON, Excel, GeoJSON, and more—in a single DuckDB command. Handles both local and remote files, with support for partitioning and compression options when needed.
Use it when
- convert-file supports CSV, Parquet, JSON, Excel, GeoJSON, JSONL, NDJSON, TSV, and spatial formats like Shapefiles and GeoPackage.
- Yes, convert-file handles remote data files from S3, GCS, and HTTP sources.
Verify before relying
Read SKILL.md below before installing (1 file). Open directory: indexed for reading, not audited.
Similar skills
Install
duckdb/duckdb-skills/convert-file · repository language: Shell
Open directory. Skills are indexed for reading, not audited. Review a skill's body before installing it.
Frequently asked questions
AI-generated answers based on this skill's SKILL.md and metadata
How do I turn a CSV into Parquet with convert-file?
convert-file transforms CSV to Parquet in a single DuckDB command. Simply specify your CSV source and choose Parquet as the output format; the skill handles the conversion automatically, including optional compression and partitioning if you need them.
What formats does convert-file support for conversion?
convert-file supports CSV, Parquet, JSON, Excel, GeoJSON, JSONL, NDJSON, TSV, and spatial formats like Shapefiles and GeoPackage. You can convert between any of these formats—whether exporting data as JSON, transforming xlsx to CSV, or writing data as GeoJSON.
Can convert-file handle remote data files?
Yes, convert-file handles remote data files from S3, GCS, and HTTP sources. You can point to a remote file location and convert it to your desired format without downloading it locally first.
Does convert-file support compression and partitioning?
convert-file supports compression and partitioning options during format conversion. When converting large datasets, you can apply these optimizations to reduce file size and improve query performance on the output.
How does convert-file handle geospatial data conversion?
convert-file can transform geospatial data to GeoJSON or other spatial formats. It supports converting Shapefiles, GeoPackage files, and other spatial sources, making it easy to work with location-based datasets across different formats.
What license does convert-file use?
convert-file is released under the MIT license, allowing free use, modification, and distribution in both open-source and commercial projects.
SKILL.md
Rendered from the published skill. Quoted content, verbatim.
You are helping the user convert a data file from one format to another using DuckDB.
Input file: $0
Output file: ${1:-}
Step 1 — Resolve input and output
Input: $0. If it's a bare filename (no /), resolve to a full path with find "$PWD" -name "$0" -not -path '*/.git/*' 2>/dev/null | head -1.
Output: If $1 is provided, use it as the output path. If not, default to the same stem as the input with a .parquet extension (e.g., data.csv → data.parquet).
Infer the output format from the output file extension:
| Extension | Format clause |
|---|---|
.parquet, .pq |
(default, no clause needed) |
.csv |
(FORMAT csv, HEADER) |
.tsv |
`(FORMAT |
(truncated - see the full file via the links below)
File tree — 1 file
skills/convert-file/SKILL.md
Let your AI agent find skills like this
Example. Real query, live index.
You found this page by searching. An agent finds it by wishing: SkillFed indexes 56,283 agent skills by what they can do, searchable in plain language.
wish › “Convert data file between formats (CSV, Parquet, JSON, Excel, etc.)”
Give your agent the search over MCP, or paste the wish link into any chat. No install? Search from any chat →
Related skills
read-file uses DuckDB to load and analyze data files across multiple formats—CSV, JSON, Parquet, Avro, Excel, spatial, and SQLite—from local paths or remote sources like S3 and HTTPS. It automatically detects file type, retrieves schema and row counts, and displays sample rows to help you understand your dataset at a glance.
Spatial handles geographic questions by combining DuckDB's spatial functions with Overture Maps, a free global dataset accessible via S3. Ask about nearby places, distances between points, or analyze your own GeoJSON, Shapefile, or GPX files—the skill manages spatial joins, containment checks, and format conversions.
Data Analysis lets you query uploaded Excel and CSV files using SQL, supporting multi-sheet workbooks, aggregation, filtering, and cross-file joins. Run statistical summaries, inspect schemas, and export results in multiple formats. Built on DuckDB for efficient columnar analysis.
Interact with Google Drive files you've explicitly selected, created, or shared with the app using the Drive v3 REST API. The skill supports reading, downloading, exporting, renaming, moving, and deleting files through curl and jq, with optional upload support via Google's Workspace CLI. Note that the connector operates under the drive.file scope and cannot browse or search your entire Drive.
This guide breaks down how SQLite organizes data on disk, from the 100-byte header through page types, B-tree layouts, and cell formats. It covers record encoding with serial types, overflow page chains for large payloads, and freelist structures for space reuse. Includes Turso implementation details and debugging commands.
axiom-data equips AI coding assistants with production-grade database expertise for Apple ecosystem development. Navigate persistence patterns, framework selection, and data architecture decisions with confidence—avoiding common pitfalls that lead to performance issues and data integrity problems. Built for Swift 6, SwiftUI, and modern Apple Intelligence workflows.