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

woodshed

v0.1.1

Published

Minimal runner and eval framework for Claude Skills

Downloads

11

Readme

woodshed

Run, rate, and iterate on your Claude Skills.

⚠️ WARNING ⚠️

This is alpha software written for personal use.

  • It runs Claude in yolo mode which can and will wipe your data.
  • It can also burn through a ton of tokens if your Skills aren't lean.
  • It is 100% vibecoded, and this time I have not read the code.

If you end up burning all your tokens only to brick your computer, I'm not responsible.

Usage

Create a new workspace:

npx woodshed create my-idea

That gives you a place work on your Skills:

cd my-idea

Time to shed:

npx woodshed

By default, the entire matrix runs 10 times.

Shed is idempotent so by default re-running it will instantly "skip over" past results as if they happened instantly.

Pass npx woodshed --reset to force re-runs. This will delete each re-run's data in results/ before attempting it. You can also delete the results/ yourself if you want.

Take a close look at the results/ folder after your first successful run. It contains the log from the main agent with your fixture's prompt.md, the log from the evaluating agent with your fixture's eval.md, the workspace folder in which they both run, and probably some other junk.

Folder Conventions

my-idea/
  skills/
    # Skills you want to create or refine
    my-skill/
      # Each Skill can have one or more variants
      baseline/SKILL.md
      experiment/SKILL.md
      silly/SKILL.md
  fixtures/
    # Fixtures that test your Skill(s)
    my-fixture/
      prompt.md
      eval.md
  assets/
    # Data shared by fixtures
    words.txt
  results/
    # Outputs and past runs appear here

Workflow

I recommend running another Claude instance and to talk with it about the /results.

Then you can use insights from that convo to refine your eval.md and SKILL.md.

Tip: If you're iterating on a skill, ask Claude to write down each experiment in a doc so you can see what works and what doesn't.

Options

--runs <n>      Number of runs per variant (default: 10)
--reset         Delete old results and start fresh
--reeval        Re-run evaluation on existing workspaces
--cache-only    Show cached results only

License

MIT