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

@openskeleton/cli

v2.10.1

Published

Reference CLI for the SKEL format: validate, convert (YAML/JSON), and inspect .skel documents.

Readme

skel — Reference CLI

The reference implementation of the external validator contract (Validator conformance class, skel-spec §9.1), plus YAML⇄JSON conversion and a quick project inspector.

# from the repo
node reference/cli/skel.mjs validate spec/example.skel

# as a package
npx @openskeleton/cli validate story.skel

Commands

skel validate <file>

Validates a .skel (YAML) or .skel.json document: JSON Schema for the selected lifecycle, referential integrity, asset-reference resolution, BONE inheritance (defaults → metadata → act → scene → shot), token declarations, and the consistency lints — with the normative codes from spec/errors.md and RFC 6901 paths.

| Flag | Effect | |---|---| | --lifecycle draft\|production\|export | Override metadata.lifecycle for this run | | --json | Machine-readable SKELValidationResult output | | --with-sidecars | Also validate video-map.json / audio-map.json / canvas/layout.json found next to the document | | --studio <studio.json> | Resolve asset references against a studio registry (validated first) |

Exit codes: 0 valid · 1 validation errors · 2 file unreadable or unparseable.

Required-field semantics: metadata/act/scene BONE entries are default providers. required: true fields are enforced where data is consumed — on shots (chain-resolved) and on characters/environments (self + definition defaults).

skel convert <in> <out>

Converts between native YAML and the JSON export form, by output extension. YAML output follows the authoring profile (skel-spec §11): no anchors/aliases, stable key order as parsed.

skel inspect <file>

One screen of truth: title, version, lifecycle, series code, structure counts, cast, plot-critical props, BONE prompt coverage, status rollups, delivery facts.

As a library

import { loadDocument, validateDocument } from "@openskeleton/cli/lib/validate.mjs";
const result = validateDocument(loadDocument("story.skel"), { lifecycle: "production" });

The conformance runner (scripts/run-conformance.mjs) drives this same library across tests/conformance/ — if your own validator matches the corpus, it matches this one.