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

@skills-house/build

v0.0.2

Published

Compile skills-house source skills to spec-compliant dist — npx @skills-house/build <skill-dir>

Readme

@skills-house/build

Compile a source skill package into a spec-compliant Agent Skills layout under skills-dist/.

Use this when you author skills in a skills-house project: expand @include fragments, resolve file and script links, copy assets, and emit a single SKILL.md that agents can load.

Quick start

# From a skill directory (needs SKILL.md)
npx @skills-house/build ./skills/my-skill

# Typical workflow in a scaffolded project
pnpm build

Output defaults to <repo-root>/skills-dist/<skill-name>/.

CLI

npx @skills-house/build <skill-dir> [options]

| Option | Description | |--------|-------------| | <skill-dir> | Path to the source skill package (must contain SKILL.md) | | --out <dir> | Output directory (default: <repo-root>/skills-dist/<name>) | | --repo-root <path> | Monorepo root (default: nearest ancestor with pnpm-workspace.yaml) | | --help | Show help |

Examples

# Build one skill
npx @skills-house/build skills/skill-auditor

# Custom output path
npx @skills-house/build skills/my-skill --out ./dist/my-skill

# Explicit repo root (useful in CI or non-standard layouts)
npx @skills-house/build ./skills/my-skill --repo-root .

Project integration

In a skills-house project, each skill under skills/<name>/ wires the CLI through package.json:

{
  "scripts": {
    "build": "build ."
  },
  "devDependencies": {
    "@skills-house/build": "^0.0.1"
  }
}

The root package.json usually runs all skills:

{
  "scripts": {
    "build": "pnpm --filter \"./skills/*\" build"
  }
}

What the compiler does

Given a source SKILL.md like:

---
name: my-skill
description: What it does and when to use it.
---

@include /sections/workflow.md

See [the guide](/references/guide.md).
Run [helper](fixture-helper/hello).

The build step:

  1. Expands @include /path/to/fragment.md recursively (cycles are rejected).
  2. Copies linked files (/references/…, /scripts/…, /assets/…) into the output tree.
  3. Rewrites package links ([label](other-skill)) when skills depend on each other in the same repo.
  4. Writes skills-dist/my-skill/SKILL.md with inlined body and updated frontmatter.

Authoring rules: skill-md-authoring spec.

Programmatic API

import { buildSkill } from "@skills-house/build";

await buildSkill({
  skillDir: "/path/to/skills/my-skill",
  outDir: "/path/to/skills-dist/my-skill",
  repoRoot: "/path/to/repo",
});

Also exported: parseSkillMd, findIncludes, findLinks, classifyHref, getRepoSlug.

Requirements

  • Node.js ≥ 20

Related packages

| Package | Role | |---------|------| | @skills-house/create | Scaffold a new skills-house project | | @skills-house/install | Install built skills into agent directories |

After building, install locally:

npx @skills-house/install add my-skill --from ./skills-dist --scope project

Consumers install published skills from GitHub:

npx skills add owner/repo --skill my-skill -a cursor -y

Monorepo development

pnpm --filter @skills-house/build build
pnpm --filter @skills-house/build test

Publish tag format: v<semver>-build.

git tag v0.0.1-build
git push origin v0.0.1-build

Learn more