@kheif/quiver 1.2.0 → 1.3.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/README.md +18 -11
  2. package/package.json +7 -7
package/README.md CHANGED
@@ -88,6 +88,7 @@ Run `quiver help <command>` for the details and examples of each.
88
88
  | `quiver new <name>` | Create a local skill and assign it to this project (`--global`: every folder, `--none`: nowhere). |
89
89
  | `quiver edit <id>` | Open a local skill in your editor, then check and commit it. |
90
90
  | `quiver delete <id>` | Delete a local skill from the library. An assigned skill needs `--force`. |
91
+ | `quiver fork <source/skill>` | Copy a source skill into your own skills to change it; `--as` names the copy. The copy takes the original's place wherever it is assigned, and `quiver update` no longer changes it. |
91
92
  | `quiver import` | Move the skills in this project's `.claude/skills` into the library (`--deep`: every folder of the project). Originals committed in git are kept; `--keep` keeps all. |
92
93
  | `quiver import <folder>` | Move every skill in a folder and its subfolders into the library. Files that are not valid skills are listed at the end. |
93
94
  | `quiver import <skill>` | Move one skill: its `SKILL.md`, its folder or a markdown file with frontmatter. `--name` renames it. |
@@ -101,11 +102,13 @@ Run `quiver help <command>` for the details and examples of each.
101
102
  | `quiver source add <repo>` | Clone a skill repository: `owner/repo` (GitHub), a git URL or a local path. |
102
103
  | `quiver source list` | List sources with their skill count and commit. |
103
104
  | `quiver source remove <name>` | Delete a source. Refuses while its skills are assigned, unless `--force`. |
104
- | `quiver update [<name>...]` | Pull the latest skills of all or some sources, and list what changed. |
105
+ | `quiver update [<name>...]` | Download the latest skills of all or some sources and show what would change: the changed files of each assigned skill, with scripts marked "needs review". Asks before it applies changes to assigned skills (`--yes` does not ask, `--diff` shows the whole change). Pinned skills stay at their commit. |
106
+ | `quiver pin <source/skill> [<commit>]` | Keep a source skill at its current commit, or the one given, so `quiver update` leaves it alone. `quiver unpin` goes back to the source's current version. |
107
+ | `quiver sync init <git-remote>` | Keep the Quiver home in a git remote, so your other machines get the same skills, sources and assignments. Run it on each machine; then `quiver sync` commits, pulls and pushes, merges assignment changes from both machines and clones sources added elsewhere. |
105
108
  | `quiver projects` | List projects (`--json`); `rename`, `forget` and `split` manage them. |
106
109
  | `quiver doctor` | Check the library, the assignments, copies of served skills in Claude Code and its setup (`--fix` applies the safe fixes). |
107
- | `quiver mcp install` | Register the MCP server with every installed assistant: Claude Code and Cursor (`--for <assistant>` for one, such as `claude-desktop`). |
108
- | `quiver mcp uninstall` | Remove it from them (`--for <assistant>` for one). |
110
+ | `quiver mcp install [assistant...]` | Register the MCP server with every supported assistant that is installed, or only with the assistants named. See [MCP server](#mcp-server). |
111
+ | `quiver mcp uninstall [assistant...]` | Remove it from them, or only from the assistants named. |
109
112
  | `quiver mcp config` | Print the MCP config entry for any other assistant. |
110
113
  | `quiver mcp` | Run the MCP server. Assistants start this. |
111
114
  | `quiver completion <shell>` | Print the completion script for `bash`, `zsh`, `fish` or `powershell`. |
@@ -120,17 +123,19 @@ quiver completion zsh > "${fpath[1]}/_quiver"
120
123
 
121
124
  ## MCP server
122
125
 
123
- `quiver mcp install` sets up Claude Code and Cursor when it finds them, or only the assistant named with `--for`:
126
+ `quiver mcp install` sets up every supported assistant that is installed. Name assistants to set up only those, such as `quiver mcp install codex cursor`. The supported assistants:
124
127
 
125
- | Assistant | `--for` | What it changes |
128
+ | Assistant | Name | What it changes |
126
129
  |---|---|---|
127
130
  | Claude Code | `claude-code` | Runs `claude mcp add --scope user quiver -- <path to quiver> mcp`. |
131
+ | Codex | `codex` | Runs `codex mcp add quiver -- <path to quiver> mcp`, which writes `~/.codex/config.toml` (or `$CODEX_HOME`). The Codex CLI and app share it. |
128
132
  | Cursor | `cursor` | Adds `quiver` to `mcpServers` in `~/.cursor/mcp.json`. |
129
- | Claude Desktop | `claude-desktop` | Adds `quiver` to `mcpServers` in `~/Library/Application Support/Claude/claude_desktop_config.json` (macOS) or `%APPDATA%\Claude\claude_desktop_config.json` (Windows). Only with `--for claude-desktop`. |
133
+ | Claude Desktop | `claude-desktop` | Adds `quiver` to `mcpServers` in `~/Library/Application Support/Claude/claude_desktop_config.json` (macOS) or `%APPDATA%\Claude\claude_desktop_config.json` (Windows). |
134
+ | Antigravity | `antigravity` | Adds `quiver` to `mcpServers` in `~/.gemini/config/mcp_config.json`, which the Antigravity CLI (`agy`) reads. |
130
135
 
131
- An assistant counts as installed when the `claude` command is on `PATH`, or when its config folder exists. In the JSON files, every other key stays as it is, including an `env` of the `quiver` entry, and the old file is saved next to it as `<file>.quiver-backup`. A file that is not valid JSON is reported and never overwritten. Restart Cursor or Claude Desktop afterwards. `quiver doctor` checks the entry of each installed assistant (of Claude Desktop only when it has one). Cursor and Claude Desktop get the path of the binary itself, never the npm launcher, because desktop apps do not see your shell's `PATH` and so cannot find `node`. Cursor passes the skill list to the model and starts the server in the workspace folder, so project skills work there.
136
+ An assistant counts as installed when its command (`claude`, `codex`) is on `PATH`, or when its config folder exists (`~/.gemini/antigravity-cli` for Antigravity). In the JSON files, every other key stays as it is, including an `env` of the `quiver` entry, and the old file is saved next to it as `<file>.quiver-backup`. A file that is not valid JSON is reported and never overwritten. When Codex already has a `quiver` entry, its `env` is kept too. Restart the assistant afterwards. `quiver doctor` checks the entry of each installed assistant. Every assistant but Claude Code gets the path of the binary itself, never the npm launcher, because desktop apps do not see your shell's `PATH` and so cannot find `node`. Cursor passes the skill list to the model and starts the server in the workspace folder, so project skills work there.
132
137
 
133
- **Claude Desktop** runs Quiver's tools but does not pass the server's instructions to the model, so it never sees the skill list or the always-on skills. A skill is used only when you ask for Quiver's skills in the prompt, such as "check the quiver skills for this". That is why `quiver mcp install` sets it up only with `--for claude-desktop`. See [docs/spike-mcp-clients.md](docs/spike-mcp-clients.md).
138
+ **Codex, Claude Desktop and Antigravity** use Quiver's skills only when you ask for them in the prompt, such as "check the quiver skills for this"; `quiver mcp install` says so. Codex loads an MCP server's tools, and with them its instructions, only when the model searches for them. Antigravity puts the instructions in a file the model rarely reads. Claude Desktop drops them. Once asked, Codex and Antigravity also follow the always-on skills; Claude Desktop does not. Codex and Antigravity start the server in the project folder, so project skills work there. See [docs/spike-mcp-clients.md](docs/spike-mcp-clients.md).
134
139
 
135
140
  For any other assistant, `quiver mcp config` prints the entry:
136
141
 
@@ -152,6 +157,8 @@ Claude Code starts the server in the project folder. Other assistants may start
152
157
  | `get_skill` | `id` | The skill's instructions, its extra files and its folder. |
153
158
  | `get_skill_file` | `id`, `path` | One extra file of a skill, such as `references/checklist.md`. Large and binary files return their path instead. |
154
159
  | `create_skill` | `name`, `description`, `body`, `scope` (`project` or `global`), optional `files` | Creates a local skill, commits it and assigns it. In a folder that is not a project yet, `project` scope registers it. |
160
+ | `update_skill` | `id`, any of `description`, `body`, `files` (an empty content deletes the file) | Changes a local skill and commits it as `update <name> (via MCP)`. Other frontmatter fields are kept. Source skills are read-only. |
161
+ | `search_skills` | `query` | Searches the whole library, also skills not assigned here, and marks each match as assigned here (`global` or `project`) or not. The assistant may suggest an unassigned skill, but asks before using it. |
155
162
 
156
163
  **Prompts.** Every served skill is also an MCP prompt. In Claude Code it appears as `/quiver:<id>`; text after the command is passed to the skill as the task.
157
164
 
@@ -168,9 +175,9 @@ Claude Code starts the server in the project folder. Other assistants may start
168
175
  Skills give instructions to your assistant, and a skill can include scripts the assistant may run. A skill from a source is code you run on your own machine.
169
176
 
170
177
  - Add only sources you trust, and read their skills before you assign them.
171
- - `quiver update` prints the old and new commit of each source, and the skills that were added, changed or removed. To read the changes of a source you do not control: `git -C ~/.quiver/sources/<name> diff <old> <new>`.
172
- - Source skills are read-only in Quiver. To change one, copy it into your own skills.
173
- - `create_skill` lets the assistant write skills into your library. A global skill's description reaches the assistant in every folder, so review new global skills with `quiver list` and `quiver edit`.
178
+ - `quiver update` downloads new commits before it applies them, lists the changed files of every assigned skill, marks scripts and executable files "needs review", and asks before it applies the changes. Read them with `quiver update --diff`; answering no leaves the source as it was. To review changes to a skill before it reaches your sessions, pin it with `quiver pin` and move the pin when you have read them.
179
+ - Source skills are read-only in Quiver. To change one, fork it into your own skills with `quiver fork`.
180
+ - `create_skill` and `update_skill` let the assistant write skills into your library. A global skill's description reaches the assistant in every folder, so review new global skills with `quiver list` and `quiver edit`. Every change is a commit in `~/.quiver/local` (in `~/.quiver` once you use `quiver sync`), so `git -C ~/.quiver/local log -p` shows it and `git revert` undoes it.
174
181
 
175
182
  To report a vulnerability in Quiver itself, see [SECURITY.md](SECURITY.md).
176
183
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@kheif/quiver",
3
- "version": "1.2.0",
3
+ "version": "1.3.0",
4
4
  "description": "Central skill manager for AI assistants, delivered as an MCP server.",
5
5
  "license": "Apache-2.0",
6
6
  "keywords": [
@@ -26,11 +26,11 @@
26
26
  "node": ">=18"
27
27
  },
28
28
  "optionalDependencies": {
29
- "@kheif/quiver-darwin-arm64": "1.2.0",
30
- "@kheif/quiver-darwin-x64": "1.2.0",
31
- "@kheif/quiver-linux-arm64": "1.2.0",
32
- "@kheif/quiver-linux-x64": "1.2.0",
33
- "@kheif/quiver-win32-arm64": "1.2.0",
34
- "@kheif/quiver-win32-x64": "1.2.0"
29
+ "@kheif/quiver-darwin-arm64": "1.3.0",
30
+ "@kheif/quiver-darwin-x64": "1.3.0",
31
+ "@kheif/quiver-linux-arm64": "1.3.0",
32
+ "@kheif/quiver-linux-x64": "1.3.0",
33
+ "@kheif/quiver-win32-arm64": "1.3.0",
34
+ "@kheif/quiver-win32-x64": "1.3.0"
35
35
  }
36
36
  }