Assignments
A skill in the library is served nowhere until you assign it. An assignment says where the MCP server serves a skill.
| Assignment | Served in | Set with |
|---|---|---|
| Project | The folders of one project | quiver add <id> in the project |
| Global | Every folder | quiver add <id> --global |
| Always-on | Where it is assigned, and loaded before the first reply | quiver add <id> --always |
A folder that is not a project gets only the global skills.
Project skills
Section titled “Project skills”cd ~/code/appquiver add release-notes anthropic/docxThe skills are served in this project only. If the folder is not a project yet, it becomes one: in a terminal, Quiver first asks Register <folder> as a project? (--yes skips the question). See Projects.
--project <folder> assigns to another project without changing directory:
quiver add tdd --project ~/code/apiGlobal skills
Section titled “Global skills”quiver add commit-style --globalA global skill is served in every folder, projects included. Its description reaches the assistant in every session, so keep global skills few and their descriptions precise.
Always-on skills
Section titled “Always-on skills”Most skills are loaded when a task needs them; the assistant decides. Some must apply from the first message without that decision, such as a communication style or house rules. Mark them always-on:
quiver add caveman --global --alwaysAn always-on skill is in the conversation before the first reply. In Claude Code, Codex, Cursor, Antigravity and VS Code, a session-start hook adds its full text. Changes take effect in the next session; see Always-on skills.
An assistant cannot change an always-on skill through update_skill. Change it yourself with quiver edit.
Removing assignments
Section titled “Removing assignments”quiver remove release-notes # from this projectquiver remove caveman --global # from every folderquiver remove caveman --global --always # keep it global, drop only the always-on markThe skills stay in the library. To delete a local skill, use quiver delete.
Assignments are yours
Section titled “Assignments are yours”Assignments are stored in ~/.quiver/registry.json, not in the project. A teammate who clones a project gets its .quiver.json, but not your skills or your assignments.
To share skills with a team, put them in a git repository that everyone adds with quiver source add. Each person then assigns the skills they want.
Where a skill is assigned
Section titled “Where a skill is assigned”quiver where release-notes # global, and each project with its foldersquiver status # every skill served in this folderRunning assistant sessions see assignment changes through list_skills and the prompts right away. The text the session-start hook adds, the always-on skills and the list of other skills, changes from the next session.