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

@egradman/prowess

v0.1.0

Published

Run agent sessions with temporary skills

Downloads

11

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

egradmanegradman

Keywords

Readme

prowess

Run AI coding agents with temporary skills. No permanent installation — skills are cached locally and loaded via a temp plugin directory that's cleaned up on exit.

npx prowess claude vercel-labs/agent-skills -s web-design-guidelines

How it works

  1. Parses your skill source (GitHub repo, GitLab, local path, direct URL)
  2. Clones it (or uses a cached copy from ~/.prowess/cache/)
  3. Discovers all SKILL.md files in the repo
  4. Copies selected skills into a temp plugin directory
  5. Launches the agent with the skills available
  6. Cleans up the temp directory on exit

Usage

prowess <agent> <source> [-s/--skill <name>...]

Source formats

| Format | Example | |---|---| | owner/repo | vercel-labs/agent-skills | | GitHub URL | https://github.com/someone/skills | | GitHub URL with ref + subpath | https://github.com/someone/skills/tree/main/advanced | | GitLab URL | https://gitlab.com/someone/skills | | Direct SKILL.md URL | https://raw.githubusercontent.com/.../SKILL.md | | Local path | ./my-skills | | Any git URL | [email protected]:someone/skills.git |

Examples

# Load all skills from a repo
npx prowess claude vercel-labs/agent-skills

# Pick specific skills
npx prowess claude vercel-labs/agent-skills -s web-design-guidelines -s react-best-practices

# From a local directory
npx prowess claude ./my-custom-skills

# From a GitHub URL with a subpath
npx prowess claude https://github.com/someone/repo/tree/main/skills/advanced

Caching

Cloned repos are cached in ~/.prowess/cache/. On subsequent runs, prowess does a git pull to refresh the cache instead of re-cloning. To force a fresh clone, delete the cache directory:

rm -rf ~/.prowess/cache/

Supported agents

Adding an agent

Each agent is a single file in agents/ that exports a launch(tempPluginDir) function. For example, agents/claude.js is ~8 lines. If your agent supports a --plugin-dir flag or similar mechanism, adding support is straightforward.

PRs welcome for: Cursor, Codex, Windsurf, Amp, Cline, Roo, or anything else that can load skills.

License

MIT