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

understanding-prime-env

v0.2.1

Published

Generate a rich, self-contained HTML report explaining any Prime Intellect verifiers environment.

Readme

understanding-prime-env

npm version npm downloads

A skill that generates a rich, self-contained HTML report explaining any Prime Intellect verifiers environment.

Run it from inside any environment folder and get an instant visual breakdown of:

  • Dataset & task examples — what prompts the model sees, with sample rows
  • Reward functions — every reward/metric, its weight, scoring range, and plain-English description
  • Rollout logic — the full scoring pipeline from prompt → response → final score
  • Configuration reference — every parameter with type, default, and description
  • Quick-start commands — install and run the environment immediately

Output is a single environment_overview.html file styled to match the Prime Intellect platform.


Installation

One-line install (recommended)

npx understanding-prime-env

Running the command with no arguments launches an interactive prompt that lets you choose your editor/CLI and install scope.

Non-interactive flags

# Claude Code — global (available in every project)
npx understanding-prime-env --claude --global

# Claude Code — local (this project only)
npx understanding-prime-env --claude

# Cursor
npx understanding-prime-env --cursor

# Windsurf
npx understanding-prime-env --windsurf

# GitHub Copilot
npx understanding-prime-env --copilot

# Zed
npx understanding-prime-env --zed

# All supported tools at once
npx understanding-prime-env --all

Manual install (Claude Code legacy)

claude plugin marketplace add Vidit-Ostwal/understanding-prime-env
claude plugin install understand-environment@understanding-prime-env

Supported tools

| Tool | What gets installed | |---|---| | Claude Code | ~/.claude/skills/understand-environment/SKILL.md (global) or .claude/skills/… (local) | | Cursor | .cursor/rules/understand-environment.mdc | | Windsurf | appended to .windsurfrules | | GitHub Copilot | appended to .github/copilot-instructions.md | | Zed | custom_instructions field in .zed/settings.json |


Usage

Navigate into any verifiers environment folder and ask your AI assistant:

"explain this environment"
"what does this env do?"
"generate an HTML overview"
"understand this environment"

The assistant will read the Python source files and write environment_overview.html to the current directory.

cd environments/ifeval_goblin
# ask your assistant to "explain this environment"
open environment_overview.html

Requirements

  • Node.js ≥ 16 (for the installer)
  • A verifiers environment directory to analyze

Links