Skill Detail

Inspect and export Excel workbooks from the terminal with xleak

Use xleak when an agent needs to inspect, search, verify formulas, and export Excel, ODS, CSV, or TSV files from a terminal without opening a desktop spreadsheet app.

Data Extraction & TransformationMulti-Framework
Data Extraction & Transformation Multi-Framework Security Reviewed
โญ 1.5k GitHub stars
COPY SKILL INSTRUCTIONS (OPTIONAL)
npx skills add agentskillexchange/skills --skill inspect-and-export-excel-workbooks-from-the-terminal-with-xleak Copy
Uses the third-party skills CLI, not an ASE-owned installer. Check your agent’s compatibility. This copies instructions; complete the upstream tool setup below separately.
At a glance
Tools required
xleak CLI, terminal access, spreadsheet files such as .xlsx, .xls, .ods, .csv, or .tsv
Install & setup
Install with Homebrew (brew install bgreenwell/tap/xleak), Cargo (cargo install xleak), Nix, Debian/Ubuntu rust-xleak where available, Scoop or WinGet on Windows, or platform binaries from the latest GitHub release.
Author
bgreenwell
Publisher
Individual
Last updated
Sep 18, 2026
Quick brief

Use xleak to open spreadsheet files in a terminal, navigate sheets, search cell contents, inspect formulas, copy rows or cells, and export workbook data to CSV, JSON, or plain text before downstream cleanup or transformation. Invoke this when an agent is working over SSH, in CI, or in a headless workspace and needs concrete evidence from an Excel workbook rather than asking the user to open Excel manually. The scope boundary is read-oriented spreadsheet triage and export through a CLI/TUI; it is not a spreadsheet editor, BI platform, or generic data-processing framework.

How it works

What this skill actually does

Inputs and prerequisites: xleak CLI, terminal access, spreadsheet files such as .xlsx, .xls, .ods, .csv, or .tsv.

Setup notes: Install with Homebrew (brew install bgreenwell/tap/xleak), Cargo (cargo install xleak), Nix, Debian/Ubuntu rust-xleak where available, Scoop or WinGet on Windows, or platform binaries from the latest GitHub release.

Source and verification boundary: use https://github.com/bgreenwell/xleak as the canonical reference before running the workflow; keep commands, API calls, CLI usage, and generated outputs reviewable against that upstream source.

Framework fit: publish this as a Multi-Framework workflow only when the operator can invoke the documented toolchain directly, rather than treating the upstream project as a generic product listing.