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

@season179/pi-skills-status

v26.5.2

Published

Shows the skills used in the current Pi session.

Readme

@season179/pi-skills-status

Show the skills used in the current Pi session.

The extension adds a compact skills: footer item to Pi after a skill is used. It updates when you invoke a skill explicitly or when Pi reads a loaded SKILL.md file, so you can see which skill context is active without digging through the transcript.

What It Does

  • Tracks explicit /skill:name invocations.
  • Tracks loaded skill files read by Pi during the session.
  • Shows up to three recent skills in Pi's status area.
  • Adds a /skills-status command that reports all tracked skills.

This is best-effort session visibility, not a full audit log. It tracks skill blocks and SKILL.md reads that Pi exposes through extension events. If Pi changes how skills are loaded, or if skill context enters the session without those events, it may not appear in the footer.

Installation

pi install npm:@season179/pi-skills-status

Usage

Start Pi normally. The status area stays quiet until a skill is detected.

After skills are used, it shows something like:

skills: code-reviewer, simplify

You can also run:

/skills-status

inside Pi to show the skills used in the current session.

Included Resources

  • Pi extension: dist/extensions/skills-status.js

Local Development

npm install
npm run build --workspace @season179/pi-skills-status

Test without publishing:

pi -e ./packages/pi-skills-status

Smoke-test package loading without your global extensions:

pi --no-extensions -e ./packages/pi-skills-status --help

Because this package publishes compiled JavaScript, build before using pi -e from the package directory.

Tarball Validation

npm pack --workspace @season179/pi-skills-status
tar -tf season179-pi-skills-status-26.5.2.tgz
pi install ./season179-pi-skills-status-26.5.2.tgz

The tarball should include:

package/package.json
package/README.md
package/LICENSE
package/dist/extensions/skills-status.js

Publishing

npm login
npm publish --access public

Scoped public packages require --access public.

Compatibility

Tested with:

  • Pi: 0.74.0
  • Node.js: >=22

Security

Pi extensions execute with your user permissions. This extension observes Pi session events and tool results to infer skill usage, but it does not modify files or run shell commands. Review the source before installing.

Troubleshooting

  • If the status never appears after using a skill, make sure the extension is installed and Pi has loaded it.
  • If package resources are not found during local testing, build the package first.
  • If the command is unavailable, reinstall the package with pi install npm:@season179/pi-skills-status.