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

skillx

v0.1.7

Published

CLI runner for skill scripts across .agent/.agents/.claude/.codex skill directories.

Readme

skillx

skillx makes scripts in a skill's scripts/ directory executable by convention:

  • scripts/main.{ts,js,py,sh} -> skillx <skill> ...
  • scripts/<command>.{ts,js,py,sh} -> skillx <skill> <command> ...

If scripts/<command>.* is missing, skillx falls back to scripts/main.* and passes <command> as the first argument.

Install

npm i -g skillx
pnpm i -g skillx
bun i -g skillx

Usage

skillx <skill> [args...]
skillx <skill> <script-name> [args...]
skillx --list
skillx --add-path <skill> <path>
skillx --add-root <path>

Examples:

skillx my-skill --dry-run
skillx my-skill do --dry-run
skillx --list
skillx --add-path my-skill ~/Code/my-skill
skillx --add-root ~/Code/my-skills

skillx --list prints available skill names that have executable scripts.

Resolution order

When you run skillx <skill> ..., skill directories are checked in this order:

  1. Custom skill path from config (~/.skillx/config.json, or $SKILLX_CONFIG)
  2. Custom skills roots from config (skillRoots list)
  3. <git-repo-root>/.agents/skill/<skill>
  4. <git-repo-root>/.agent/skills/<skill>
  5. <git-repo-root>/.agents/skills/<skill>
  6. <git-repo-root>/.claude/skills/<skill>
  7. <git-repo-root>/.codex/skills/<skill>
  8. <git-repo-root>/skills/<skill> (OpenClaw workspace skills)
  9. ~/.agents/skills/<skill> (or $SCRIPT_SKILLS_HOME/<skill> if set)
  10. ~/.agent/skills/<skill>
  11. ~/.claude/skills/<skill> (or $SCRIPT_CLAUDE_SKILLS_HOME/<skill> if set)
  12. ~/.openclaw/skills/<skill> (or $SCRIPT_OPENCLAW_SKILLS_HOME/<skill> if set, using $OPENCLAW_STATE_DIR or $OPENCLAW_HOME when present)
  13. $CODEX_HOME/skills/<skill> (fallback ~/.codex/skills/<skill>)

Custom skill path config

Set a custom location for a specific skill:

skillx --add-path <skill> <path>

Add an entire skills folder (containing many <skill>/scripts/... directories):

skillx --add-root <path>

By default, mappings are saved to ~/.skillx/config.json:

{
  "skillPaths": {
    "my-skill": "/absolute/path/to/my-skill"
  },
  "skillRoots": [
    "/absolute/path/to/my-skills"
  ]
}

Use $SKILLX_CONFIG to store this config file elsewhere.

Script dispatch behavior

Within a matched skill directory:

  • skillx <skill> <name> ... tries scripts/<name>.* first.
  • If scripts/<name>.* is missing, it falls back to scripts/main.* and passes <name> through as the first argument.
  • skillx <skill> ... runs scripts/main.*.
  • If main is missing but named scripts exist, skillx shows available commands and exits with code 2.

Supported script targets

  • .js, .mjs, .cjs -> node
  • .ts, .mts, .cts -> bun (preferred), then node (native TS support), tsx, ts-node, deno
  • .py -> uv run (preferred), fallback python3
  • .sh -> bash
  • executable files with a shebang (#!...) -> executed directly

Node native TypeScript execution is used when Node supports it (v22.18+, v23+, or v24.3+).

All args are forwarded unchanged.