Configuration and file layout
Quiver writes to two places: the Quiver home, ~/.quiver (or $QUIVER_HOME), and one .quiver.json per project. It changes assistant config files when you run quiver install or quiver uninstall. A command that changes skills also adjusts the number of hook commands in the hooks that already run this quiver, and says so on stderr when it does.
The Quiver home
Section titled “The Quiver home”Directory~/.quiver/
- config.json sources and settings
- registry.json global skills, projects and their skills
Directorystate/ machine-local
- projects.json the folders where each project was seen
- version-check.json the latest release, checked once a day
Directorylogs/
- mcp.log the MCP server's log
- hook.log what each session-start hook run passed, with a hash of the text
Directorycache/hook/ the parts of a session-start text, shared by its hook commands
- …
Directorylocal/ your own skills, a git repository
Directoryrelease-notes/
- SKILL.md
Directoryk8s-debug/
- SKILL.md
Directoryreferences/
- checklist.md
Directorysources/ cloned skill repositories
Directoryanthropic/
- …
Directory.pins/ checked-out commits of pinned skills
- …
Edit these files through quiver commands, not by hand. quiver doctor checks them.
config.json
Section titled “config.json”The sources, with their repository and the folder of each skill ID:
{ "version": 1, "sources": { "anthropic": { "repo": "https://github.com/anthropics/skills.git", "ids": { "pdf": "skills/pdf", "docx": "skills/docx" } } }}registry.json
Section titled “registry.json”The assignments: global skills, always-on skills, and each project's skills by project ID.
{ "version": 2, "global": ["anthropic/pdf"], "alwaysOn": [], "projects": { "app-6ts23a": { "name": "app", "skills": ["release-notes"] } }}Project folders are not in registry.json. They are machine-local, in state/projects.json, so quiver sync can share the registry between machines.
In a project
Section titled “In a project”{ "id": "app-6ts23a" }The project's ID, and nothing else. Commit it. See Projects.
In assistant configs
Section titled “In assistant configs”| Assistant | File | Entry |
|---|---|---|
| Claude Code | managed by claude mcp | quiver, user scope |
| Codex | managed by codex mcp, in ~/.codex/config.toml | mcp_servers.quiver |
| Cursor | ~/.cursor/mcp.json | mcpServers.quiver |
| Claude Desktop | ~/Library/Application Support/Claude/claude_desktop_config.json (macOS), %APPDATA%\Claude\claude_desktop_config.json (Windows) | mcpServers.quiver |
| Antigravity | ~/.gemini/config/mcp_config.json | mcpServers.quiver |
Before Quiver changes a JSON file, it saves the old one as <file>.quiver-backup.
Skill files
Section titled “Skill files”---name: release-notesdescription: Write release notes from the commits since the last tag.---
Instructions for the assistant.| Field | Required | Rules |
|---|---|---|
name | Yes | Lowercase letters, digits and dashes, starting with a letter or digit. Up to 64 characters. |
description | Yes | When the assistant should use the skill. Up to 1024 characters. |
forkedFrom | No | Written by quiver fork: <id>@<commit>. |
Other fields are kept as they are.