skillm

Fetch AI-agent skills from git repos or local paths and install them into the folders your agents read — Claude, Codex, Cursor, Amp, Gemini CLI, and more. One canonical .agents/skills copy per scope, symlinked into every other agent. ~/.skillm holds only skillm's config and registry; the installs themselves are the skill's only copies.

Install

macOS / Linux

curl -fsSL https://raw.githubusercontent.com/ultrakorne/skillm/master/install.sh | sh

Windows (PowerShell — requires Developer Mode for symlinks)

irm https://raw.githubusercontent.com/ultrakorne/skillm/master/install.ps1 | iex

Go

go install github.com/ultrakorne/skillm@latest

Quickstart

skillm agent                                                    # pick which agents get skills
skillm install https://github.com/ultrakorne/skill-collection --global   # fetch + pick + install, one step
skillm install railwayapp/railway-skills --global                # same, via GitHub owner/repo shorthand
skillm install grill-with-docs --local                          # add a scope: committable project install (.agents/skills + lockfile)
skillm import                                                   # adopt a repo's skills-lock.json (skillm's or `npx skills`')
skillm check                                                    # see what has updates
skillm update                                                   # pull the updates in, everywhere on this machine
skillm update --force                                           # also take over agent-folder copies skillm didn't create
skillm uninstall grill-with-docs --local                        # remove only this project's install
skillm uninstall grill-with-docs --project /path/to/project      # remove only another project's install

A global install writes a real copy into the canonical ~/.agents/skills folder — the cross-agent store read natively by Codex, Cursor, Amp, Gemini CLI, and more — and symlinks every other enabled agent's user-level folder to it (the seeded claude entry links ~/.claude/skills/<id>).

A local install works the same way inside a project: a real copy in the canonical .agents/skills folder, a relative in-repo symlink for every other enabled agent (e.g. .claude/skills/<id>), and an entry in skills-lock.json — all committable, so teammates get working skills on clone with no tooling. The layout and lockfile are the same ones vercel's npx skills CLI uses, so either tool can manage the same repo: skillm import adopts entries a teammate added, and skillm update re-syncs every tracked project on the machine (auto-adopting new lockfile entries as it goes) — the one-command whole-machine update per-repo tools can't do.

Commands

Command	Description
install [<url|owner/repo|path>] [id...] [--all] [--as <name>] [--ref <ref>] [--global|--local]	Install into every enabled agent — straight from a repo URL, a GitHub owner/repo shorthand, or a path (fetch + pick + install in one step), or by the id of an already-installed skill to add another scope/project. Local scope writes the committable project install; interactive pickers if no id.
import [dir]	Adopt a project's skills-lock.json into skillm's tracking: fetch the sources and write any missing copies/links.
uninstall [id...] [--all] [--global|--local|--project <dir>]	Remove copies, agent links and lock entries everywhere, or only globally / in one project. Keep the registry entry while another install remains; interactive skill picker if no id.
list	Show every installed skill and where it is installed (global or the project path).
check	Report which git skills have upstream updates.
update [id]	Pull updates for outdated git skills (all, or one), writing the new content into every install — the global copy and every tracked project's copies and lock entries — and adopt teammate-added lockfile entries.
agent	Enable/disable agents, reconciling their links right away (skills stay installed).
upgrade [--check]	Upgrade skillm itself to the latest release: downloads this platform's archive, verifies its SHA256 against the release's checksums.txt, and swaps the binary in place. --check only reports.

A skill installed globally is globally active — installing is what fetches and activates it; there is no separate "fetch without activating" step. Uninstalling a skill's last install removes it entirely.

Note the split: skillm update pulls new revisions of your installed skills; skillm upgrade replaces the skillm binary itself. A binary built from source (go build, or an unstamped version) matches no published release, so upgrade reports that and leaves it alone.

When another tool already installed a skill in an agent folder, skillm keeps that directory and warns that the agent still uses its existing copy. Retry the command with --force to replace it with a link to the shared copy. Canonical-copy conflicts retain their overwrite prompt.

Global flags: --force / --yes (--yes approves canonical overwrites and uninstall; agent path takeovers require --force), --home <path> (override Home, default ~/.skillm).

License

MIT