quiver
Skill manager for AI coding assistants: one library of agent skills, served over MCP to Claude Code, Codex, Cursor and others, in layers, with always-on skills in every session.
Install / Use
claude mcp add kheif -- npx -y github:kheif/quiverIf the server publishes to npm under a different name, use that package instead — check the repo README.
MCP Server
Model Context Protocol server
Quality Score
Category
Development & EngineeringSupported Platforms
Our assessment of quiver
quiver scores 83/100 on our quality scale, 2989th of 4,706 Development & Engineering skills we index.
Its MCP Server is 22 KB long, well organised into 15 sections with 9 code examples: a thorough specification that gives an agent plenty to work with.
It has 3 GitHub stars, so there is little community track record yet; judge it on its content.
Maintenance, license and trust
- The repository was last updated 7 days ago, so quiver is actively maintained.
- It is released under the Apache-2.0 license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 92/100, with 1 caution from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
quiver compared with similar skills
All 4 of these similar skills score higher than quiver; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| quiver (this skill)by kheif | 83 | 3 | 7d ago | MCP Server |
| taste-skillby Leonxlnx | 100 | 117.6k | 9d ago | CLAUDE.md |
| Agent-Reachby Panniantong | 100 | 112.7k | 10d ago | CLAUDE.md |
| rufloby ruvnet | 100 | 82.0k | today | CLAUDE.md |
| headroomby headroomlabs-ai | 100 | 79.9k | today | CLAUDE.md |
Frequently asked questions
- How do I install quiver?
- Run
claude mcp add kheif -- npx -y github:kheif/quiver. The install tabs above show the steps for each supported agent. - Which AI agents does quiver work with?
- It is written for Claude Code, Claude Desktop, Cursor and OpenAI Codex, as a MCP Server file. Other agents that read the same format can often use it too.
- Is quiver safe to use?
- It is Apache-2.0-licensed and scores 92/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is quiver still maintained?
- The repository was last updated 7 days ago, so quiver is actively maintained.
Skill content
View source on GitHubQuiver
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:
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 QUIVER_VERSION=v1.0.0 for a given release, or QUIVER_INSTALL_DIR for another folder. Run it again to update.
Windows (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. QUIVER_VERSION and QUIVER_INSTALL_DIR work the same way, set with $env:QUIVER_INSTALL_DIR = '...' before the line.
npm (macOS, Linux and Windows):
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:
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 QUIVER_NO_UPDATE_CHECK=1 to turn the check off.
Quickstart
# 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.
Then start Claude Code in ~/code/app and ask for the task, such as "write the release notes for this version". The assistant sees release-notes in Quiver's skill list and loads it. You can also run it yourself as /quiver:release-notes.
quiver status shows what the assistant gets in the current folder. quiver alone sums it up in three lines, with a next step, before the command list.
The interactive panel
In a terminal, quiver without arguments opens a panel for everything above, with no command to remember. ? lists the keys of the current section.
| Section | What it does |
|---|---|
| 1 Skills | Your skills in four views (available here, the project's, global, all), grouped by source. Assign a skill to the project and to every folder independently, each as On demand or Always on. n creates a skill, i imports, e edits, f forks a source skill, d deletes, p pins. / searches. |
| 2 Projects | The registered projects. Choose one to manage it from anywhere, rename it, forget it, or split a copied folder. |
| 3 Sources | The skill repositories. a adds one, u checks for updates and shows what would change (d shows the patches) before it applies them, x removes one. |
| 4 Health | The checks of quiver doctor and how always-on skills reach each assistant. i sets up the MCP server and hooks, f applies the safe fixes. Without a Quiver home, the panel offers to set it up. |
Every change goes through the same code as the matching command. quiver sync and the --json outputs stay on the command line.
Concepts
- Library.
~/.quiver/local/holds your own skills, in a git repository Quiver commits to.~/.quiver/sources/holds cloned skill repositories. SetQUIVER_HOMEto use another folder. - Skill files. A skill is a folder with a
SKILL.md. Quiver also imports a skill written as one markdown file of any name, such asreview.md, when its frontmatter has adescription. - Skill IDs. A local skill's ID is its folder name, such as
release-notes. A skill from a source is<source>/<skill>, such asanthropic/pdf. - Assignments.
registry.jsonstores which skills are global and which projects get which skills. A folder that is not a project gets only the global skills. - Assignments are yours. They live in your
~/.quiver, not in the project. A teammate who clones the project gets its.quiver.json, but not your skills or assignments. To share skills, put them in a git repository that everyone adds withquiver source add. - Projects. A project is the folder with
.quiver.json, found by walking up from the current folder. It is created the first time you assign a skill there; in a terminal,add,newandimportfirst askRegister <folder> as a project?(--yesskips the question). The ID survives moves and renames. Git worktrees of one repository share the committed.quiver.json, so they are one project with the same skills. If a folder is copied, both copies have the same ID;quiver statuswarns, andquiver projects splitgives the copy its own. - One copy of each skill. A skill that Quiver serves and that Claude Code also loads by itself, from
~/.claude/skills, the project's.claude/skillsor an enabled plugin, may be loaded twice.quiver importtherefore deletes the originals it copied, except those committed in a project's git, which teammates may still need (--keepkeeps every original).quiver statusandquiver doctorreport the copies they find, by name or by content, andquiver doctor --fixdeletes those not committed in git and not in a plugin. - Always-on skills. A skill added with
--alwaysis loaded before the assistant's first reply, for style or rules that apply to every answer. See the limits below.
Commands
Run quiver help <command> for the details and examples of each.
| Command | What it does |
|---|---|
| quiver | Show the project here, how many skills it is served and a next step, then the command list. |
| quiver init | Create the Quiver home and anything missing in it; in a terminal, then offer to register the MCP server and import existing skills (--yes: only create the home). |
| quiver new <name> | Create a local skill and assign it to this project (--global: every folder, --none: nowhere). |
| quiver edit <id> | Open a local skill in your editor, then check and commit it. |
| quiver delete <id> | Delete a local skill from the library. An assigned skill needs --force. |
| quiver fork <source/skill> | Copy a source skill into your own skills to change it; --as names the copy. The copy takes the original's place wherever it is assigned, and quiver update no longer changes it. |
| quiver import | Move the skills in this project's .claude/skills into the library (--deep: every folder of the project). Originals committed in git are kept; --keep keeps all. |
| quiver import <folder> | Move every skill in a folder and its subfolders into the library. Files that are not valid skills are listed at the end. |
| quiver import <skill> | Move one skill: its SKILL.md, its folder or a markdown file with frontmatter. --name renames it. |
| quiver add <id>... | Assign skills to this project, or to every folder with --global. --always makes them always-on. |
| quiver remove <id>... | Unassign skills. They stay in the library. |
| quiver list | List the library's skills and where each is assigned (--source, --unassigned, --json). |
| quiver show <id> | Show a skill: where it comes from, where it is assigned, its files and its SKILL.md (--json). |
| quiver search <text> | Search the IDs, names and descriptions of every library skill, also unassigned ones, and show whether each is served here (--json). |
| quiver status | Show the project in this folder and the skills served here, with a warning for each copy Claude Code also loads (--json). |
| quiver where <id> | Show where one skill is assigned (--json). |
| quiver source add <repo> | Clone a skill repository: owner/repo (GitHub), a git URL or a local path. |
| quiver source list | List sources with their skill count and commit. |
| quiver source remove <name> | Delete a source. Refuses while its skills are assigned, unless --force. |
| quiver update [<name>...] | Download the latest skills of all or some sources and show what would change: the changed files of each assigned skill, with scripts marked "needs review". Asks before it applies changes to assigned skills (--yes does not ask, --diff shows the whole change). Pinned skills stay at their commit. |
| quiver pin <source/skill> [<commit>] | Keep a source skill at its current commit, or the one given, so quiver update leaves it alone. quiver unpin goes back to the source's current version. |
| quiver sync init <git-remote> | Keep the Quiver home in a git remote, so your other machines get the same skills, sources and assignments. Run it on each machine; then quiver sync commits, pulls and pushes, merges assignment changes from both machines and clones sources added elsewhere. Before it pulls changes that make a skill always-on, change an always-on skill's files or add a source, it lists them and asks (--yes takes them). |
| quiver projects | List projects (--json); rename, forget and split manage them. |
| quiver doctor | Check the library, the assignments, copies of served skills in Claude Code and its setup (--fix applies the safe fixes). |
| quiver install [assistant...] | Register the MCP server and add the session-start hook where the assistant has one, in every supported assistant that is installed, or only in the assistants named. See MCP server. |
| quiver uninstall [assistant...] | Remove it from them, or only from the assistants named. |
| quiver mcp config | Print the MCP config entry for any other assistant. |
| quiver mcp | Run the MCP server. Assistants start this. |
| quiver completion <shell> | Print the completion script for bash, zsh, fish or powershell. |
Shell completion suggests real skill IDs, sources and projects. For zsh, for example:
quiver completion zsh > "${fpath[1]}/_quiver"
quiver help completion shows the setup for each shell.
MCP server
quiver install sets up every supported assistant that
Truncated for display — read the full file on GitHub.
Related Skills
taste-skill
117.6kAgent skills that give coding agents taste: art direction, reference images and a browser check instead of generic AI pages
Agent-Reach
112.7kGive your AI agent eyes to see the entire internet. Read & search Twitter, Reddit, YouTube, GitHub, Bilibili, XiaoHongShu — one CLI, zero API fees.
ruflo
82.0k🌊 The original agent harness. Deploy intelligent multi-player swarms, coordinate autonomous workflows, and build conversational AI systems. Features adaptive memory, self-learning intelligence, federation, vector RAG integration, and native Claude Code / Codex / Hermes and many more Integrated
headroom
79.9kCompress tool outputs, logs, files, and RAG chunks before they reach the LLM. 20% fewer tokens for coding agents, 60-95% fewer tokens for JSON, same answers. Library, proxy, MCP server.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
