Skill Detail

Build TypeScript spreadsheet import and export workflows with hucre

Use hucre when a coding agent needs to add zero-dependency XLSX, CSV, ODS, JSON, NDJSON, or XML spreadsheet parsing and writing to TypeScript or edge-runtime projects.

Data Extraction & TransformationMulti-Framework
Data Extraction & Transformation Multi-Framework Security Reviewed
⭐ 2.2k GitHub stars ⬇ 106.4k/wk npm
COPY SKILL INSTRUCTIONS (OPTIONAL)
npx skills add agentskillexchange/skills --skill build-typescript-spreadsheet-import-and-export-workflows-with-hucre 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
Node.js or a TypeScript-compatible runtime and the hucre npm package
Install & setup
Install with npm install hucre, then import only the needed modules such as hucre/xlsx, hucre/csv, or hucre/ods and wire the read/write functions into the spreadsheet ingestion or export path.
Author
productdevbook
Publisher
Individual
Last updated
Sep 19, 2026
Quick brief

Use hucre when an agent is implementing spreadsheet ingestion, validation, conversion, or export inside a TypeScript codebase, especially where edge runtime compatibility, tree shaking, or zero dependencies matter. Invoke it instead of opening a spreadsheet product or shelling out to office software when the workflow output should be application code that reads and writes structured spreadsheet formats repeatably. The scope boundary is programmatic spreadsheet file parsing and serialization in TypeScript; it is not a general office suite, data-cleaning product, or broad document automation framework.

How it works

What this skill actually does

Inputs and prerequisites: Node.js or a TypeScript-compatible runtime and the hucre npm package.

Setup notes: Install with npm install hucre , then import only the needed modules such as hucre/xlsx , hucre/csv , or hucre/ods and wire the read/write functions into the spreadsheet ingestion or export path.

Source and verification boundary: use https://hucre.productdevbook.com 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.