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

@markusazer/sklint

v0.1.3

Published

A static analyzer for agent skills

Readme

sklint

A static analyzer for agent skills. It reads every SKILL.md in a folder and reports the ones that break skill-authoring best practices.

Install

# npm (any Node project). Downloads a prebuilt binary. Command is `sklint`.
pnpm add -D @markusazer/sklint
# or
npm i -D @markusazer/sklint

# from source (Rust)
cargo install sklint

Prebuilt binaries cover Linux x64/arm64, macOS x64/arm64, and Windows x64.

Usage

sklint path/to/skills
✓ good-skill
✗ big-skill
    error  budget        body is 812 lines, over 500
    warn   desc-when     description may not say when to use it

2 skills · 1 error · 1 warn · exit 1

How it works

Each skill is parsed once into its frontmatter, body, and bundled files. Every rule reads those parts and reports findings at one of three levels: error, warn, or off. The exit code follows the worst finding, so it fits into CI or a pre-commit hook.

Checks

| rule | catches | |------|---------| | name | missing name, not kebab-case, or not matching the folder | | desc-length | description over 1024 characters | | desc-when | description that never says when to use the skill | | budget | body over 500 lines (a warning if a references/ folder exists) | | dead-link | a referenced path that does not exist | | orphan | a scripts/ or references/ file the body never mentions | | script-intent | a script named with no run or read verb nearby | | mush | generic filler phrases |

Configure

Add an optional sklint.toml next to the skills. It tunes thresholds and per-rule severity.

[thresholds]
body_max_lines = 300

[rules]
mush = "off"          # off | warn | error
desc-when = "error"

Every key is optional. Anything you leave out keeps its default, and no file means all defaults.

Exit codes

  • 0 all skills clean
  • 1 at least one error-level finding
  • 2 could not run: no SKILL.md found, or a file could not be read

License

MIT.