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

@graview/skills

v0.1.28

Published

Skills that teach an assistant the authoring moves, each ending in a real graview check verdict.

Readme

@graview/skills

Skills that teach an assistant how to build with Graview — and, more usefully, how to find out whether it worked.

npx graview skills install .    # into .claude/skills and .agents/skills
npx graview skills list

The command line is the graview package; this one ships the skills and the move, and graview skills dispatches here.

Why this framework is worth having skills for

Most skills end in a claim: "you have added a node kind." That is worth very little, because the assistant writing it is the same one that just decided it was done.

Graview can answer the question itself. graview check reads the declaration and reports an edge to a kind nobody wrote, an invariant scoped to a kind that does not exist, a repair naming a mutation nobody registered, a lens role bound to a missing field, a mutation with no title, a palette pair that fails WCAG AA, a role that may do nothing. So every skill here ends in a check and reports the real verdict — including when the verdict is bad.

A skill that cannot verify its own outcome says so. That is the rule, and the skills say which parts of their work the checker cannot see.

The skills

| Skill | The move it teaches | |---|---| | graview-node-kind | Add a node kind: fields, edges, plural, roles, and what renders for free | | graview-invariant | Write a rule that names the mutations that would repair it | | graview-lens | Build a lens that binds roles rather than field names, so another domain can reuse it | | graview-agent-seat | Wire an agent seat that shares the interface's actions rather than shadowing them | | graview-permissions | Declare who may do what, once, and let the strip and the seat narrow themselves | | graview-brand | Put someone's name on an installation without forking a package | | graview-new-app | Start a product on Graview in its own repository, with the CI that keeps it honest | | graview-pages | The routed face: derived pages, one page in the app's words, a product design over every surface, and the embed | | graview-port-app | Port an existing application onto Graview, deciding what is a node and what is a field | | graview-studio | Open the declaration as a graph, change it with acts, check before applying, migrate, and write it back as the scaffold's files |

The worked examples live in apps/ in the framework repository. The skills point at them rather than restating them — a skill that copies an example goes stale the moment the example changes.