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

@meir-labs/skill-prep

v0.1.2

Published

Prep a ticket: the agent reads it, works out the fix, and writes the plan, risk, effort and priority back onto the ticket without building anything. npx installs it into .claude/skills.

Downloads

524

Readme

@meir-labs/skill-prep

Type /prep LAB-123 and your coding agent turns a vague ticket into one that someone else can build from. It reads the whole ticket, finds the cause or the shape of the work in the code, picks one fix, and writes it back onto the ticket. It never builds the fix.

The ticket ends up with this description:

## What          the problem, as the user sees it
## Why           who it affects and what it costs to leave
## Where         product area, repo and main files
## Cause         bugs only, marked confirmed or suspected
## Proposed fix  numbered steps a builder can follow
## Risk          Low / Medium / High, what could break, how to roll back
## Done when     checkable acceptance criteria
## Source        who asked, original wording, links

It also sets the effort estimate on the team's own scale and a priority, fixes a vague title, and re-reads the ticket to check the changes saved. Status and assignee are left alone. It comments only when it changed a field or has a question for the owner.

Effort stays on the team's relative scale. The skill does not add estimates in hours, days or weeks, or promise a completion date.

Risk reflects the planned work, not its topic. Isolated verification can be Low risk even for permissions or payments; any riskier repair is called out separately with the finding that would trigger it.

Works with Linear (through an MCP server or the API) and with GitHub issues through gh.

Install

# into the current project (./.claude/skills/prep)
npx @meir-labs/skill-prep

# into every project (~/.claude/skills/prep)
npx @meir-labs/skill-prep --global

Pass --force to overwrite an existing copy. It's plain markdown, so it works in Claude Code, Codex and any other agent that reads a SKILL.md. Link the same folder into ~/.codex/skills/prep to share one copy.

Read it before you run it: files/. Full page: meirlabs.com/skills/prep.