Skip to content

Managing sources

A source is a git repository of skills. Quiver clones it into ~/.quiver/sources/<name> and serves its skills as <name>/<skill>.

Terminal window
quiver source add anthropics/skills --name anthropic

The repository can be:

  • owner/repo on GitHub, or host/owner/repo,
  • any git URL, such as git@github.com:acme/skills.git,
  • a local path, such as ~/code/team-skills.

The source name defaults to the repository owner; --name sets another one. Quiver lists the skills it found:

Cloning https://github.com/anthropics/skills.git as source "anthropic"...
Added source "anthropic" with 19 skills:
anthropic/docx
anthropic/pdf
…
Note: skills give instructions to your assistant and may contain scripts. Review them before you assign them.

Nothing is assigned yet. Read a skill, then assign it:

Terminal window
quiver show anthropic/pdf
quiver add anthropic/pdf --global
  • If the repository has .claude-plugin/marketplace.json, a Claude Code plugin marketplace, Quiver reads the skills of its plugins from it.
  • Otherwise it collects every folder with a SKILL.md.
Terminal window
quiver source list # name, skill count, commit in use and its date, repository
quiver source remove acme # refuses while its skills are assigned
quiver source remove acme --force # unassigns its skills first

quiver update downloads new commits, shows what changes in your assigned skills, and asks before it applies them. See Updating and pinning.

~/.quiver/local is a git repository. Push it to GitHub, and others can add it as a source:

Terminal window
git -C ~/.quiver/local remote add origin git@github.com:me/skills.git
git -C ~/.quiver/local push -u origin HEAD
Terminal window
# on a teammate's machine
quiver source add me/skills

For a team, keep shared skills in one repository that everyone adds as a source. Each person assigns the skills they want; assignments are not shared.

To keep your own library the same on several machines, use quiver sync instead.