Agent skills, managed in layers
Quiver keeps one library of agent skills for Claude Code, Codex, Cursor and other assistants, and gives each folder the skills it needs, in layers: you and the project today, your team and your company next.
npm install -g @kheif/quiverWhat the assistant gets here
~/code/checkout-webalways on: in the conversation before your first message
3 always on, loaded at session start. 3 more when a task needs them. Company and team layers come with Quiver for teams.
- always on: security-reviewcompany · planned
- always on: design-tokensUI team · planned
- always on: reply-styleyou
- a11y-checkUI team · planned
- anthropic/pdfyou
- release-notescheckout-web
Your skills are scattered across assistants
Agent skills are instruction files that teach an assistant how your work is done: how you review a migration, write release notes or debug a crashing pod.
Today Claude Code keeps them in .claude/skills, Cursor in its rules, Codex in .codex/skills and AGENTS.md. They are copied from project to project, drift apart, and leave with the project.
Quiver keeps one copy, in a git repository on your machine, and serves it to every assistant in the folders that need it.
Today
~/code/app/.claude/skills/release-notes/the original~/code/api/.cursor/rules/release-notes.mdccopied, then edited~/code/site/AGENTS.mdpasted in, out of date~/archive/old-tool/.claude/skills/k8s-debug/gone with the project
With Quiver
~/.quiver/local/release-notes/SKILL.mdone copy, in git~/.quiver/local/k8s-debug/SKILL.mdkept, usable anywhere
served over MCP to Claude Code Codex Cursor
How it works
Keep every skill in one library
Write your own with quiver new, import the ones you have, or add any git repository of skills.
Put each skill on a layer
Your own skills apply in every folder, a project's only in that project. Team and company layers come with Quiver for teams. Mark a skill always on and the assistant has it from the start of the session.
Open any assistant
quiver install connects Claude Code, Codex and Cursor. Each session gets the skills of its folder.
~/.quiver, your library
local/ your skills, in git release-notes/SKILL.md reply-style/SKILL.md k8s-debug/SKILL.md sources/ cloned, read-only anthropic/ 19 skills acme/ 6 skills
Where each skill applies
always on: in the conversation from the start of the session
Connect once, then open a session in ~/code/checkout-web
$ quiver install Registered with Claude Code: quiver mcp Registered with Codex: quiver mcp Registered with Cursor: quiver mcp Before the first message security-review, reply-style Loaded when a task fits release-notes, anthropic/pdf
Try one session
Pick a folder and a team, and choose what is always on, to see what the assistant has before your first message.
Claude Code
~/code/checkout-web
<quiver-always-on> Always-on skills from Quiver. Follow each one for the whole conversation. ## security-review Before you change code, check it for secrets, injection and unsafe defaults. ## reply-style Answer first, then the reason. No filler. </quiver-always-on>
Loaded when a task fits: design-tokens, a11y-check, anthropic/pdf, release-notes
Folder
Team
Always on
security-reviewreply-styledesign-tokensTo do this on your own layer: quiver add reply-style --global --always. In Claude Code, Codex, Cursor, Antigravity and VS Code, a session-start hook puts this block in the conversation.
Quiver for teams
The same library, run for a whole company, with team and company layers managed in one place. Free and open source like the rest, to run on your own servers; hosting by us is coming soon.
On the roadmap, after a test phase on more assistants and on Windows.
- The company's skills live in one library and change through review, like code.
- Each team gets its own skills on top of the company's, and none from the teams next door.
- The always-on skills you choose load in every developer's sessions, and you can see which sessions they reached.
Works with your assistants
Any other MCP client: quiver mcp config prints the entry. What works where
Built in the open
Licensed under Apache-2.0. There is no account: your library is a folder of git repositories on your machine. The tasks and design decisions are in the repository too.
- Contributing guidebuild, test, pull requests
- Roadmapevery planned task, in the repository
- Issuesbugs and feature requests
- Security policyreport vulnerabilities privately
- v1.4.04 November 2026session-start hooks that deliver always-on skills in full, quiver install, VS Code Copilot
- v1.3.02 November 2026sync between machines, update preview, pin and fork, Codex and Antigravity
- v1.2.031 October 2026show and search, a guided first run, Cursor and Claude Desktop, a Windows installer
- v1.1.029 October 2026import one skill or a whole folder, skills written as a single markdown file
$ git clone https://github.com/kheif/quiver $ cd quiver && make build && make test
Install it with npm install -g @kheif/quiver
Then run quiver init: it creates your library and offers to connect your assistants. There is also an install script, for Windows too, and go install: installation guide.