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

@knowledgeassemble/engine-skills

v0.1.2

Published

Authoring skills for the OpenEdu Interactive engines, packaged for consumers.

Readme

@knowledgeassemble/engine-skills

Authoring skills for the OpenEdu Interactive engines, packaged for consumers.

Source of truth

Everything under skills/ is a generated/committed projection. Never hand-edit it.

  • The authorable copy lives in-repo: docs/engines/<engine>/skills/<skill>/SKILL.md (prose, may reference in-repo docs) and docs/fixtures/<engine>/skill-example.json (machine input). Engine schemas and docs/schemas/composition.schema.json complete the inputs.
  • Edit those, run pnpm generate, and commit both sides. The freshness guard (scripts/check-engine-skills-fresh.mjs) fails if regeneration produces a diff.
  • Generated artifacts must contain zero packages/ or docs/ path fragments; the generator fails loudly otherwise. Composition's embedded-spec line says validateEnvelope(spec) from @knowledgeassemble/interactive-engine — ./schema.json is the lesson schema, not the envelope.

Layout

Each skill is a folder under skills/ containing:

  • SKILL.md — instructions for a course authoring agent (what the interactive means, content shape, acceptance criteria).
  • schema.json — the full envelope JSON Schema (draft 2020-12) for that engine.
  • skill-example.json — a valid, self-contained example spec.

manifest.json maps each engine to its skill folder, example, schema, and the validationContract (package / symbol / method) used to validate specs at runtime.

Consuming

import { getEngineEntry, loadSkillExample, validateSkillExample, validateSpec } from '@knowledgeassemble/engine-skills';

const contract = getEngineEntry('visual')!.validationContract; // { package, symbol, method }
validateSkillExample('visual');                   // { valid: true, errors: [] }
validateSpec('visual', mySpec);                   // validates any candidate spec

Development

| Task | Command | |------|---------| | regenerate skills/schema/manifest from source docs | pnpm generate | | typecheck | pnpm typecheck | | lint | pnpm lint | | tests | pnpm test |

Generated artifacts are committed; regeneration must produce a byte-identical tree, enforced by node scripts/check-engine-skills-fresh.mjs (repo root).