skillwharf
One manifest and lockfile for the agent skills your team shares.
npm i -g skillwharfskillwharf on npmNode 22.12 or later, on macOS and LinuxVersion 0.2.0Release notes

At a glance
- Requires
- Node 22.12 or later
- Tested on
- macOS and Linux, with Node 22 and 24
- Licence
- MIT, free to use
- Works with
- Claude Code, Codex and Cursor
- Network
- Fetches skills with git, from GitHub, GitLab, Bitbucket or a server you run, when you add, sync or update them; reads each registry’s index when you search
- Telemetry
- None, and no account
skillwharf is a command-line tool for agent skills: folders with a SKILL.md
that teach a coding agent a task, such as filling in PDFs, building an MCP
server, or your team’s release checklist. They are easy to write and easy to
lose track of. The same skill ends up copied into every agent’s folder and onto
every teammate’s machine, and the copies drift. Nothing pins them, so a fresh
clone of your project can get a different skill from the one you tested with,
or none at all. And nobody knows which ones are actually used.
skillwharf treats skills the way a package manager treats dependencies.
skillwharf.json says which skills a project wants, and skillwharf.lock.json
pins each one to a full commit sha and a content hash. One copy lives in
.skillwharf/skills, and each agent’s folder gets a link to it: by default
.claude/skills for Claude Code and .agents/skills, which Codex and Cursor
read.
What it does
addinstalls a skill from GitHub, GitLab, Bitbucket, any git server you run, or a local path, and pins it. Give it a name instead, and it looks the skill up in your registries.sync, run after agit clone, gives a teammate exactly the same skills. It installs the pinned commit and refuses content whose hash differs from the lockfile.doctorreports broken links, drift from the lockfile, folders skillwharf did not create, and skills nobody has used lately.usagereads Claude Code’s local session logs to show which skills actually fire.updatere-fetches from source, refreshes the lockfile and reports what changed.registryadds, removes and lists the registries a project searches, so a team can keep its own list of skills next to the public one.
Who it’s for
One developer: skillwharf -g keeps your personal skills in ~/.skillwharf
and links them into the agents’ global folders, so every project on your
machine sees the same versions. A small team: commit the two files next to your
code, and everyone who clones the repository runs skillwharf sync. A company
with several teams: keep shared skills in repositories of your own, on GitHub,
GitLab, Bitbucket or a server you run, private ones too as long as each
person’s git can already clone them. Each team pins the versions it uses, and
a registry of your own, one index.json in a repository, makes them easy to
find.
What goes over the network
There is no telemetry and no account. Skills are fetched with git, over https
or ssh only, using the credentials your git already has; skillwharf never asks
for or stores any. search reads the index.json of each registry the project
lists; the default one is
mujieha/skillwharf-registry,
a starter list that is schema-checked, not reviewed. usage reads Claude
Code’s logs on your machine, and nothing from them leaves it.
What it does not do
It does not review a skill’s content. Coding agents read skills as
instructions, so installing one is like installing a dependency: read a
SKILL.md before installing it, as you would a shell script. A compromised
upstream at the ref you asked for is faithfully installed, so read what
skillwharf update reports before trusting the result.
Usage tracking covers Claude Code only; Codex and Cursor do not write
comparable local logs. On Windows without Developer Mode, symlinks fall back to
copies, and doctor flags them.
How it keeps what lands there exact
skillwharf checks every path component before using it, including values read
back from the manifest and lockfile, and never writes through a symlink inside
the project. In a fetched repository, a link that stays inside it is copied as
the file it points to and a link that leaves it is dropped. Git runs without
hooks, filters or redirects, does not prompt for passwords unless you allow it,
and has a time limit. skillwharf never
replaces files it did not create unless you pass --force, and treats
registries as untrusted data: plain http:// registries are refused and
redirects are not followed. The
security policy
has the full threat model.
Install
npm i -g skillwharf
skillwharf init
skillwharf add github:anthropics/skills/skills/mcp-builder
It needs Node 22.12 or newer. After a fresh git clone of a project that uses
it, run skillwharf sync.
Source code: github.com/mujieha/skillwharf