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

sk-loadout

v1.0.0

Published

Terminal skills manager for AI coding assistants.

Downloads

94

Readme

⚡️ A preset captures your model and skills for one work mode.

🎯 Switch presets and your Agent reconfigures instantly — no manual editing of settings files or symlinks.

✨ Features

  • Hot-swap presets — change AI model + skills in a single command
  • Multi-platform — supports Claude Code, OpenCode, and Codex
  • Symlink-based — skills are mounted without copying files

[!IMPORTANT] sk-loadout is a manager, not an installer. It organizes skills you already have — it does not download, generate, or distribute them.

📦 Installation

npm install -g sk-loadout

Or run once with npx:

npx sk-loadout claude init

🚀 Quick Start

sk claude init                         # bootstrap
sk claude save frontend --desc "UI"    # snapshot current model + skills
sk claude skill                        # toggle skills interactively
sk claude use frontend                 # switch preset
sk claude ls                           # inspect state

[!TIP] After one platform is initialized, sk auto-detects it — omit the platform name and just run sk ls, sk use frontend, or sk save backend --desc "API work".

⌨️ CLI Commands

| Command | Description | | --------- | ---------------------------------------------------------- | | init | Bootstrap or rebuild the sk-loadout environment | | skill | Open the interactive skill picker (toggle skills visually) | | ls | Show active preset, mounted skills, and all presets | | save | Save current model + mounted skills as a preset | | use | Switch to a preset — applies model config and syncs skills | | add | Mount stored skills to the current preset | | rm | Remove skills, or delete a preset (-p) | | restore | Uninstall for one platform and restore managed skills |

add only mounts skills that already exist in the store — it does not import files from arbitrary paths. New skills are collected from the platform skills directory by init, ls, save, use, and skill.

See CLI Reference for full options and examples.

🤖 Agent Commands

init generates slash-command helpers so AI agents can manage presets and skills directly in a conversation:

| Command | Equivalent | | ---------- | ---------------- | | /sk-ls | sk claude ls | | /sk-use | sk claude use | | /sk-save | sk claude save | | /sk-add | sk claude add | | /sk-rm | sk claude rm |

These work inside Claude Code, OpenCode, and Codex.

[!NOTE] Commands are regenerated on each init. Save customizations before re-initializing.

🧩 Supported Agents

| Agent | Prefix | | ----------- | ------------- | | Claude Code | sk claude | | OpenCode | sk opencode | | Codex | sk codex |

📖 Example Walkthrough

Start with a fresh Claude Code setup. You have a few skills in ~/.claude/skills/ — some you wrote, some from a third-party repo:

# Bootstrap — adopts existing skills, creates a default "base" preset
sk claude init

# See what was collected
sk claude ls

# The model from settings.json was captured automatically.
# Save it as a named preset with the skills you want:
sk claude skill              # toggle to pick skills for frontend work
sk claude save frontend --desc "Vue + Tailwind + a11y"

# Switch to it — model config and skill symlinks update instantly
sk claude use frontend

# Add another skill from the store (must already exist there)
sk claude add git-push

# Tweak skills and update current preset
sk claude rm git-push

# Create another preset for a different workflow
sk claude use base            # start from clean state
sk claude skill               # pick backend-focused skills
sk claude save backend --desc "API + database + testing"

# Switch preset as needed
sk claude use

# Clean up a preset you no longer need
sk claude rm -p frontend

# Machine-readable output for scripts
sk claude ls --json

# Preview what uninstall would do before committing
sk claude restore --dry-run

🔧 Scripting & CI

Use direct commands with --yes to skip prompts:

sk claude use review-mode
sk claude add vue-helper.md
sk claude rm -p old-preset --yes
sk claude restore --yes
sk claude ls --json

[!NOTE] skill and use require a TTY. Use add / rm / use <name> for automation.

🏗 Architecture

CLI → Commands → Core managers → Platform adapters → Assistant config + skill directories

Preset state lives in ~/.sk-loadout. Skills are mounted via symlinks (junctions on Windows). Model config is written through platform-specific adapters.

📚 Documentation