Quiver for teams
Planned. One library of agent skills for the whole company, delivered to the assistants your developers use, with the always-on skills every session must start with.
- Company
- Team
- You
- Project
Four layers, from company to project
Every folder gets the skills of its layers, and each layer adds to the ones above it, so nobody copies skills between projects or teams. Your own layer and the project layer work today; Quiver for teams adds the company and team layers.
- Company
- Set once for every developer, such as a security review or the incident runbook.
- Team
- Skills for one team, such as UI or backend, that the other teams never see.
- You
- Each developer still keeps their own skills and style, in every folder.
- Project
- Skills for one codebase, for everyone who works on it.
What a team gets
One library
The company's skills live in one library and change through review, like code.
Each team sees its own
A team gets its own skills and the company's, and nothing from the teams next door.
- design-tokensUI team · always on
- a11y-checkUI team
- security-reviewcompany · always on
- api-conventionsbackend team · not in this catalog
Always-on rules
The always-on skills you choose are in every developer's sessions from the start. A skill is guidance for the assistant, not a hard block: what must never happen still needs the assistant's own permission settings.
Every assistant you use
Claude Code, Codex, Cursor and other MCP clients get the same skills from the same library. How much loads on its own differs by assistant.
Where skills reached
Which skills were loaded, in which sessions, recorded by your own Quiver server.
Run it yourself
- Free and open source under Apache-2.0, like the rest of Quiver.
- Runs on your own servers. Hosting by us is coming soon, for teams that would rather not run it.
- Skills stay plain
SKILL.mdfiles in git, so nothing locks you in.
Where it stands
Planned. Quiver for one developer comes first, then a test phase on more assistants and on Windows, then teams. Follow the releases on GitHub.
What a team can do today
Keep the team's skills in one git repository. Each developer adds it to Quiver as a source and assigns its skills to their projects, and changes arrive with an update each developer reviews first. There is no team layer yet, so every developer sets this up once.
Share skills through a sourceReleasesHow layers work today
Planning a rollout for your company?
A UI developer's session in ~/code/checkout-web
Before the first message
- security-reviewcompany
- design-tokensUI team
- reply-styleyou
Loaded when a task fits
- a11y-checkUI team
- incident-runbookcompany
- release-notesproject