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

@a-canary/pi-upskill

v1.0.0

Published

Learn from failures, reduce token waste, improve automatically

Readme

pi-upskill

Learn from failures. Reduce token waste. Improve automatically.

Overview

pi-upskill tracks corrections (failures → fixes) and generates skills/rules to prevent future mistakes.

Core flow:

  1. Log corrections during conversation (upskill-log tool)
  2. Backfill from past sessions (/upskill-backfill)
  3. At threshold, analyze and generate ONE high-impact edit (/upskill-analyze)

Installation

# From git (recommended)
pi install git:github.com/a-canary/pi-upskill

# Or from npm after publishing
pi install npm:pi-upskill

# Try without installing
pi -e git:github.com/a-canary/pi-upskill

After install, reload: /reload

Usage

During conversation: log corrections

The agent uses the upskill-log tool:

Agent: [uses upskill-log tool]
  failure: "Committed without running tests"
  correction: "Always run tests before commit"
  strength: "strong"
  tokens_wasted: 3000

Result: Logged correction #5 to .pi/corrections.jsonl
        Progress: 5/20 corrections

Strength levels:

  • strong — User said "always/never/remember" → single occurrence = skill
  • pattern — Self-correction or repeated issue → needs 3x occurrences

One-time: scan past sessions

/upskill-backfill

Scans session files from pi, claude, opencode, codex. Extracts corrections for review.

At threshold: analyze and improve

/upskill-analyze

When 20+ corrections logged, triggers background analysis:

  1. LLM reviews all corrections
  2. Selects ONE edit for maximum token impact
  3. Applies surgical edit (skill/AGENTS.md/MEMORY.md)
  4. Removes addressed corrections

Check progress

/upskill-status

Shows: count, threshold, strong vs pattern, total tokens wasted.

Data Format

.pi/corrections.jsonl — one JSON object per line:

{"timestamp":"2025-03-13T01:30:00Z","failure":"Committed without tests","correction":"Always run tests first","context":"User reminder after broken CI","tokens_wasted":3000,"source":"user","strength":"strong"}

Required fields (max 30 words each):

  • timestamp — ISO 8601
  • failure — What went wrong
  • correction — How to fix / what to do instead
  • source — "user" or "self"
  • strength — "strong" or "pattern"

Optional:

  • context — Relevant context
  • tokens_wasted — Estimated tokens

Configuration

.pi/settings.json:

{
  "upskill": {
    "threshold": 20,
    "autoAnalyze": false,
    "lookbackDays": 7
  }
}

Architecture

~/pi-upskill/
├── CHOICES.md           # Decision record
├── PLAN.md              # Implementation phases
├── README.md            # This file
├── extension/
│   └── index.ts         # upskill-log tool, commands
└── skills/
    ├── analyze/SKILL.md # Pattern analysis workflow
    └── backfill/SKILL.md # Historical scan workflow

Hybrid interface:

  • Extension provides upskill-log tool (inline during conversation)
  • Skills provide /upskill-backfill and /upskill-analyze commands

Key Decisions

See CHOICES.md for full decision record.

| ID | Decision | |----|----------| | UX-0001 | User corrections with "always/never/remember" → immediate skill | | UX-0002 | Self-corrections → need 3x pattern before skill | | F-0003 | At 20 corrections → background analysis, ONE edit for max impact | | D-0003 | Processed corrections removed after edit applied |

Inspiration