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

@vincemakes/kiso-skills-ext

v0.45.3

Published

kiso official skills extension — two-tier progressive skills, kernel untouched

Readme

kiso-skills-ext

The kiso official skills extension: two-tier progressive skills, the kernel untouched.

How it is loaded

Since 0.1.45 this extension ships built-in with the kiso CLI — a fresh install starts with it registered (the startup banner lists it), with zero disk setup. The same artifact can also be installed as a user-level extension: copy dist/kiso-skills.mjs into ~/.kiso/extensions/ — the user-layer loader accepts exactly this shape.

Configuration

Skill directories: ~/.kiso/skills/<name>/SKILL.md (or the project-level .kiso/skills/ after the trust gate). No configuration file — the extension scans the skills dir at startup.

A name found twice resolves to its first occurrence (root order, then directory-name order within each root); the later one is reported with the broken skills, never listed.

A host passes options instead: createSkillsExtension({ roots, include }). roots replaces the default scan with the host's directories, in order. include(entry) decides which skills are active, and the model's index, read_skill, the catalog and the count are all built from that one filtered list, so a skill the host turned off cannot be loaded on request either.

Invoking a skill yourself

/skill <name> [args] sends a skill as your turn: its SKILL.md body, then your args after a blank line. /<name> [args] does the same when no built-in command has that name — a built-in always wins. /skills lists what is installed, where each skill lives, and any that cannot load with the reason.

The frontmatter keys read are name, description and user-invocable. Values may be plain, quoted ("…" or '…'), or YAML block scalars (> or |, with the text on the following indented lines); the index shows the description on one line. A > or | with nothing under it is reported as a skill that cannot load.

A skill whose frontmatter says user-invocable: false stays in the model's index and out of your reach. Only the literal false counts; a skill without the key is invocable.

The body is sent as written — there is no placeholder substitution; your args follow it. A body over 32,768 characters is refused, not cut.

Versioning

The version counter is this package's own. It is pinned exactly by the kiso CLI it ships with; an extension release reaches CLI users through the next CLI release.