Every agent runtime invented its own skill format. USB defines one portable format and installs it natively into each runtime, so you write a skill once instead of once per tool.
Quickstart
npm install -g @peepsick/usb-cli
usb install
USB detects every AI runtime installed on your machine and installs natively where it can —
SKILL.md skills for Claude Code, an .mdc rule for Cursor. If it
finds more than one, it asks which.
usb search postgres # find a skill
usb install intent-router # install just one
usb install web-dev --target=claude # install a preset into a specific runtimeWhat you get
- One format, many targets — a skill written once installs into 16 runtime targets.
- Native install, not a wrapper — files land where the runtime already looks for them.
- Verified installers — every installer is sha256-checked before it runs.
- A real catalog — 529 skills, searchable from the CLI.
- Portable pack — skills are kept in
~/.ai-skills/alongside the target-specific files.
Packages
@peepsick/usb-cli— the command line tool.@peepsick/usb-sdk— the SDK for building on top of USB.- github.com/PeepSick/usb — source and issues.
Questions
What problem does USB solve?
Every agent runtime has its own skill format — SKILL.md for Claude Code, .mdc rules for Cursor, and so on. USB defines one portable format and installs it natively into each runtime, so a skill is written once instead of once per tool.
How do I install USB?
Install the CLI globally with npm install -g @peepsick/usb-cli, then run usb install. USB detects the AI runtimes present on the machine and asks which target to install into when it finds more than one.
How many runtimes and skills are supported?
16 provider targets and 529 skills in the catalog. Installers are sha256-verified.
Is USB free?
Yes. USB is free and open source, published on npm as @peepsick/usb-cli and @peepsick/usb-sdk, with the source on GitHub.