npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@sttronn/pi-sheets

v0.1.2

Published

Spreadsheet-editing skill for agentic coding hosts (Claude Code, Codex, Pi). openpyxl + formualizer + a unified CLI; works as a portable skill bundle or as a pi extension.

Readme

pi-sheets

A spreadsheet-editing skill for agentic coding hosts — orient → edit via openpyxl → save via xlsx_kit → validate, preserving formulas and structure. Works in Pi coding-agent, Claude Code, and OpenAI Codex.

Wraps two libraries:

Install

Pi coding-agent

# 1. Install the extension
pi install npm:@sttronn/pi-sheets

# 2. One-shot setup — creates a venv at ~/.local/share/pi-sheets/.venv
#    and installs python deps. Idempotent; safe to re-run.
python3 $(find ~/.nvm ~/.pi/agent -name xlsx.py -path '*pi-sheets*' 2>/dev/null | head -1) doctor --install

Don't have python ≥3.10? Install one with uv:

curl -LsSf https://astral.sh/uv/install.sh | sh && uv python install 3.13

Pi runs the tiny extension in src/index.ts, which contributes skills/ via resources_discover. The agent automatically loads SKILL.md and follows the workflow.

Claude Code

git clone https://github.com/StTronn/pi-sheets ~/code/pi-sheets

mkdir -p ~/.claude/skills
ln -s ~/code/pi-sheets/skills/xlsx ~/.claude/skills/xlsx

pip install -r ~/code/pi-sheets/skills/xlsx/requirements.txt

For project-local: symlink to <your-project>/.claude/skills/xlsx.

OpenAI Codex

git clone https://github.com/StTronn/pi-sheets ~/code/pi-sheets

mkdir -p ~/.codex/skills
ln -s ~/code/pi-sheets/skills/xlsx ~/.codex/skills/xlsx

pip install -r ~/code/pi-sheets/skills/xlsx/requirements.txt

For project-local: symlink to <your-project>/.codex/skills/xlsx.

Manual / development install (any host)

git clone https://github.com/StTronn/pi-sheets ~/code/pi-sheets
cd ~/code/pi-sheets && npm install            # only needed for typechecking src/
pip install -r skills/xlsx/requirements.txt

Symlink skills/xlsx/ into the host's skill discovery dir as shown above.

Repo layout

pi-sheets/
├── skills/
│   └── xlsx/     ← host-agnostic skill bundle (Pi, Claude Code, Codex all use this)
│       ├── SKILL.md
│       ├── scripts/
│       └── requirements.txt
└── src/          ← 16-LOC pi-extension shim (skill registration only)
    └── index.ts

The skills/xlsx/ directory is the canonical artifact. src/index.ts is a tiny pi extension whose only job is to register skills/ as a skill path when the package is installed via pi install. Claude Code and Codex ignore it and consume skills/xlsx/ directly via symlinks.

Why skills/xlsx/ (not bare skill/)? Pi enforces the Agent Skills spec: a skill's SKILL.md frontmatter name: must match its parent directory name. Our name: xlsx therefore lives in xlsx/, contained in skills/ (the registered skill-path).

Usage

Once the skill is on the host's skill path, any prompt like "edit this xlsx" or "create a budget spreadsheet" will trigger the workflow:

  1. python3 <skill>/scripts/xlsx.py inspect <file> — orient (sheets, dims, formulas)
  2. Edit via openpyxl in a bash heredoc
  3. Save via xlsx_kit.save(wb, path) (writes xlsx + Univer JSON + emits a snapshot event)
  4. python3 <skill>/scripts/xlsx.py validate <file> — audit + recalc in one pass

Each operation is also importable as a python function:

import sys
sys.path.insert(0, '<skill-dir>/scripts')
from inspect_xlsx import inspect
from validate_xlsx import validate

info = inspect("wb.xlsx")
report = validate("wb.xlsx")

See skills/xlsx/SKILL.md for the full agent-facing workflow and skills/xlsx/scripts/EVENTS.md for the optional event wire contract.

Optional: event wire

The skill emits structured events (workbook_snapshot, script_event) when XLSX_EVENTS_PATH=<file> is exported. Off by default. Export the env var before launching the host:

export XLSX_EVENTS_PATH=/tmp/xlsx-events.ndjson
claude   # or: codex / pi

# in another terminal:
tail -F /tmp/xlsx-events.ndjson | jq .

Useful for live workbook viewers, progress dashboards, or post-hoc inspection. Full schema: skills/xlsx/scripts/EVENTS.md.

What the skill itself ships

skills/xlsx/
├── SKILL.md
├── README.md
├── requirements.txt
└── scripts/
    ├── xlsx.py                # unified CLI
    ├── inspect_xlsx.py        # pure function + per-script CLI
    ├── audit_xlsx.py
    ├── recalc_xlsx.py
    ├── validate_xlsx.py
    ├── extend_formula.py
    ├── doctor.py
    ├── event_emit.py
    ├── EVENTS.md
    └── xlsx_kit/__init__.py

Each operation script exposes a pure function plus a CLI shim, so the agent can either invoke subprocesses (python3 xlsx.py validate ...) or compose operations in a single python heredoc — both flow through bash from the agent's perspective and work identically in all three hosts.

Requirements

  • Python 3.10+
  • openpyxl >= 3.1, formualizer >= 0.5.8 (in skills/xlsx/requirements.txt)
  • For pi install use: @earendil-works/pi-coding-agent ≥ 0.74.0 (peer dependency, host-provided)

Troubleshooting

If a script fails with ModuleNotFoundError:

python3 skills/xlsx/scripts/xlsx.py doctor

Prints the exact python interpreter the host picked up plus a copy-pasteable pip install command for any missing deps. Most issues come from the host launching from a shell whose PATH doesn't include the venv that has the deps installed.

python3 itself is broken

If python3 -m venv fails — usually a packaging issue with whichever python is first on your PATH — install a known-good python and re-run doctor --install:

curl -LsSf https://astral.sh/uv/install.sh | sh
uv python install --default --force

uv ships standalone python builds that bundle their own stdlib dependencies, avoiding most distro-packaging issues.

License

MIT — see LICENSE.