Apache Feather/Arrow IPC format reference. V1 vs V2 format differences, pyarrow.feather read/write with compression, R arrow package integration, Arrow type system, Feather vs Parquet benchmarks, pandas DataFrame caching, LZ4/ZSTD compression options, and pipeline best practices.
Scanned 9/7/2026
Install to Claude Code
Skills Directorynpx -y skills add bytesagain/ai-skills --skill feather --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Feather?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/bytesagain-feather)More formats (shields.io, HTML) on the badges page.
---
name: "feather"
version: "1.0.0"
description: "Apache Feather/Arrow IPC format reference. V1 vs V2 format differences, pyarrow.feather read/write with compression, R arrow package integration, Arrow type system, Feather vs Parquet benchmarks, pandas DataFrame caching, LZ4/ZSTD compression options, and pipeline best practices."
author: "BytesAgain"
homepage: "https://bytesagain.com"
source: "https://github.com/bytesagain/ai-skills"
tags: [feather, arrow, ipc, columnar, pandas, dataframe, data]
category: "data"
---
# Feather
Apache Feather/Arrow IPC format reference — fast columnar DataFrame I/O.
## Commands
| Command | Description |
|---------|-------------|
| `intro` | Feather overview, V1 vs V2, key properties |
| `python` | pyarrow.feather read/write, benchmarks |
| `r-lang` | R arrow package, Python↔R interop |
| `schema` | Arrow types, nested types, metadata |
| `vs-parquet` | Speed vs compression tradeoffs |
| `pandas` | pd.read_feather, caching patterns |
| `compression` | LZ4/ZSTD options, when to use each |
| `best-practices` | Pipeline patterns, file size guidelines |
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Ultra-compressed commit message generator. Cuts noise from commit messages while preserving intent and reasoning. Conventional Commits format. Subject ≤50 chars, body only when "why" isn't obvious. Use when user says "write a commit", "commit message", "generate commit", "/commit", or invokes /caveman-commit. Auto-triggers when staging changes.
