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

load-skills

v0.3.0

Published

Load and validate agent skills from configurable paths.

Readme

load-skills

load-skills loads skill content from configurable locations and validates skill spec constraints.

Install

bun add load-skills

Usage

import { loadSkills } from "load-skills";

const { skills, report } = await loadSkills({
  paths: ["./.agents/skills"],
  recursive: false,
});

config is optional. Calling loadSkills() uses:

  • paths: ["./.agents/skills"]
  • recursive: false

skills includes loaded skill payloads:

  • shape: Record<string, Skill> (keyed by skill name)
  • meta: typed frontmatter object with required name and description
  • content: SKILL.md content without frontmatter
  • references: absolute file paths from references/
  • scripts: script descriptors from scripts/ as { path, type }

report includes one entry per configured path:

  • paths: one entry per configured path:
    • inputPath: raw path from config
    • resolvedPath: absolute resolved path
    • count: number of included skills from that path
    • skillNames: included skill names from that path
    • error (optional): path_not_found or path_not_directory
  • ignoredDuplicates: map of skipped duplicate skills (first-find-wins), keyed by kept skill name
  • invalidSkills: invalid skill entries moved out of skills; each item includes warnings

Path Priority

paths is also a priority list. If the same meta.name appears in multiple paths, the first one found is included and later ones are ignored.

Warning codes

These warnings appear on report.invalidSkills[*].warnings.

  • missing_frontmatter: SKILL.md is missing a valid --- ... --- frontmatter block.
  • invalid_yaml_frontmatter: Frontmatter exists but YAML parsing failed or did not produce an object.
  • missing_required_meta_name: Frontmatter is missing required name.
  • missing_required_meta_description: Frontmatter is missing required description.
  • invalid_meta_name: name is present but not a non-empty string.
  • invalid_meta_description: description is present but not a non-empty string.
  • skill_md_content_size_limit_exceeded: SKILL.md body exceeds 500 lines.
  • resource_read_error: A resource file or directory could not be read during scanning.