kheif/quiver

A central skill manager for AI assistants, delivered as an MCP server.
Quiver keeps all your skills in one library, ~/.quiver: your own skills and skills from git repositories. You decide which skills are global (served in every folder) and which belong to a project. The assistant starts Quiver's MCP server, sees the skills of the folder it works in, and loads the ones a task needs.
Skills are never copied into projects. A project only gets a small .quiver.json with its ID.
Skills use the standard Agent Skills format: a folder with a SKILL.md (YAML frontmatter with name and description) and any extra files. Existing skills and skill repositories work as they are.
## Install
Quiver is a single binary. It needs git on your PATH.
macOS and Linux:
sh
curl -fsSL https://raw.githubusercontent.com/kheif/quiver/main/install.sh | sh
The script downloads the latest release for your system, checks its checksum and installs quiver into ~/.local/bin. Set QUIVERVERSION=v1.0.0 for a given release, or QUIVERINSTALLDIR for another folder. Run it again to update.
Windows (PowerShell):
powershell
irm https://raw.githubusercontent.com/kheif/quiver/main/install.ps1 | iex
The same steps for Windows: it installs quiver.exe into %LOCALAPPDATA%\Programs\quiver and adds that folder to your user PATH, without admin rights; open a new terminal afterwards. QUIVERVERSION and QUIVERINSTALLDIR work the same way, set with $env:QUIVERINSTALLDIR = '...' before the line.
npm (macOS, Linux and Windows):
sh
npm install -g @kheif/quiver
npm installs the binary for your platform; no install script runs. If you switch Node versions with nvm, fnm or volta, run quiver install again afterwards, because the path of quiver changes with the Node version.
Go:
sh
go install github.com/kheif/quiver/cmd/quiver@latest
The archives for every platform are also on the releases page. To build from a clone: make build, which writes bin/quiver.
New versions. Once a day, a command run in a terminal asks GitHub for the latest release, while it runs, and remembers the answer in ~/.quiver/state/version-check.json. When a newer version is out, the command ends with one line on stderr, with the install command that matches how you installed Quiver. Nothing is shown for quiver mcp, with --json, outside a terminal or for development builds, and a failed check is silent. quiver doctor shows the latest version. Set QUIVERNOUPDATECHECK=1 to turn the check off.
## Quickstart
sh
# 1. Create the library in ~/.quiver, register the MCP server with your
# assistants and import the skills you already have
quiver init
# 2. In a project folder, write a skill for that project
cd ~/code/app
quiver new release-notes
In a terminal, quiver init asks before each step: registering the MCP server (quiver install), importing the skills in ~/.claude/skills for every folder, and importing those in the current project's .claude/skills. Any step can be skipped and run later. quiver init --yes, or a run outside a terminal, only creates ~/.quiver; any other command creates it too.
quiver new opens the new SKILL.md in $VISUAL or $EDITOR. Write one sentence in description on when the assistant should use the skill, and the instructions below the frontmatter. Quiver commits the skill in ~/.quiver/local and creates ~/code/app/.quiver.json. Commit that file, so the project keeps its ID in every clone.