@kheif/quiver 0.0.0-stage → 1.0.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.
- package/LICENSE +202 -0
- package/README.md +168 -2
- package/bin/quiver.js +43 -0
- package/package.json +34 -4
package/LICENSE
ADDED
|
@@ -0,0 +1,202 @@
|
|
|
1
|
+
Apache License
|
|
2
|
+
Version 2.0, January 2004
|
|
3
|
+
http://www.apache.org/licenses/
|
|
4
|
+
|
|
5
|
+
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
|
|
6
|
+
|
|
7
|
+
1. Definitions.
|
|
8
|
+
|
|
9
|
+
"License" shall mean the terms and conditions for use, reproduction,
|
|
10
|
+
and distribution as defined by Sections 1 through 9 of this document.
|
|
11
|
+
|
|
12
|
+
"Licensor" shall mean the copyright owner or entity authorized by
|
|
13
|
+
the copyright owner that is granting the License.
|
|
14
|
+
|
|
15
|
+
"Legal Entity" shall mean the union of the acting entity and all
|
|
16
|
+
other entities that control, are controlled by, or are under common
|
|
17
|
+
control with that entity. For the purposes of this definition,
|
|
18
|
+
"control" means (i) the power, direct or indirect, to cause the
|
|
19
|
+
direction or management of such entity, whether by contract or
|
|
20
|
+
otherwise, or (ii) ownership of fifty percent (50%) or more of the
|
|
21
|
+
outstanding shares, or (iii) beneficial ownership of such entity.
|
|
22
|
+
|
|
23
|
+
"You" (or "Your") shall mean an individual or Legal Entity
|
|
24
|
+
exercising permissions granted by this License.
|
|
25
|
+
|
|
26
|
+
"Source" form shall mean the preferred form for making modifications,
|
|
27
|
+
including but not limited to software source code, documentation
|
|
28
|
+
source, and configuration files.
|
|
29
|
+
|
|
30
|
+
"Object" form shall mean any form resulting from mechanical
|
|
31
|
+
transformation or translation of a Source form, including but
|
|
32
|
+
not limited to compiled object code, generated documentation,
|
|
33
|
+
and conversions to other media types.
|
|
34
|
+
|
|
35
|
+
"Work" shall mean the work of authorship, whether in Source or
|
|
36
|
+
Object form, made available under the License, as indicated by a
|
|
37
|
+
copyright notice that is included in or attached to the work
|
|
38
|
+
(an example is provided in the Appendix below).
|
|
39
|
+
|
|
40
|
+
"Derivative Works" shall mean any work, whether in Source or Object
|
|
41
|
+
form, that is based on (or derived from) the Work and for which the
|
|
42
|
+
editorial revisions, annotations, elaborations, or other modifications
|
|
43
|
+
represent, as a whole, an original work of authorship. For the purposes
|
|
44
|
+
of this License, Derivative Works shall not include works that remain
|
|
45
|
+
separable from, or merely link (or bind by name) to the interfaces of,
|
|
46
|
+
the Work and Derivative Works thereof.
|
|
47
|
+
|
|
48
|
+
"Contribution" shall mean any work of authorship, including
|
|
49
|
+
the original version of the Work and any modifications or additions
|
|
50
|
+
to that Work or Derivative Works thereof, that is intentionally
|
|
51
|
+
submitted to Licensor for inclusion in the Work by the copyright owner
|
|
52
|
+
or by an individual or Legal Entity authorized to submit on behalf of
|
|
53
|
+
the copyright owner. For the purposes of this definition, "submitted"
|
|
54
|
+
means any form of electronic, verbal, or written communication sent
|
|
55
|
+
to the Licensor or its representatives, including but not limited to
|
|
56
|
+
communication on electronic mailing lists, source code control systems,
|
|
57
|
+
and issue tracking systems that are managed by, or on behalf of, the
|
|
58
|
+
Licensor for the purpose of discussing and improving the Work, but
|
|
59
|
+
excluding communication that is conspicuously marked or otherwise
|
|
60
|
+
designated in writing by the copyright owner as "Not a Contribution."
|
|
61
|
+
|
|
62
|
+
"Contributor" shall mean Licensor and any individual or Legal Entity
|
|
63
|
+
on behalf of whom a Contribution has been received by Licensor and
|
|
64
|
+
subsequently incorporated within the Work.
|
|
65
|
+
|
|
66
|
+
2. Grant of Copyright License. Subject to the terms and conditions of
|
|
67
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
68
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
69
|
+
copyright license to reproduce, prepare Derivative Works of,
|
|
70
|
+
publicly display, publicly perform, sublicense, and distribute the
|
|
71
|
+
Work and such Derivative Works in Source or Object form.
|
|
72
|
+
|
|
73
|
+
3. Grant of Patent License. Subject to the terms and conditions of
|
|
74
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
75
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
76
|
+
(except as stated in this section) patent license to make, have made,
|
|
77
|
+
use, offer to sell, sell, import, and otherwise transfer the Work,
|
|
78
|
+
where such license applies only to those patent claims licensable
|
|
79
|
+
by such Contributor that are necessarily infringed by their
|
|
80
|
+
Contribution(s) alone or by combination of their Contribution(s)
|
|
81
|
+
with the Work to which such Contribution(s) was submitted. If You
|
|
82
|
+
institute patent litigation against any entity (including a
|
|
83
|
+
cross-claim or counterclaim in a lawsuit) alleging that the Work
|
|
84
|
+
or a Contribution incorporated within the Work constitutes direct
|
|
85
|
+
or contributory patent infringement, then any patent licenses
|
|
86
|
+
granted to You under this License for that Work shall terminate
|
|
87
|
+
as of the date such litigation is filed.
|
|
88
|
+
|
|
89
|
+
4. Redistribution. You may reproduce and distribute copies of the
|
|
90
|
+
Work or Derivative Works thereof in any medium, with or without
|
|
91
|
+
modifications, and in Source or Object form, provided that You
|
|
92
|
+
meet the following conditions:
|
|
93
|
+
|
|
94
|
+
(a) You must give any other recipients of the Work or
|
|
95
|
+
Derivative Works a copy of this License; and
|
|
96
|
+
|
|
97
|
+
(b) You must cause any modified files to carry prominent notices
|
|
98
|
+
stating that You changed the files; and
|
|
99
|
+
|
|
100
|
+
(c) You must retain, in the Source form of any Derivative Works
|
|
101
|
+
that You distribute, all copyright, patent, trademark, and
|
|
102
|
+
attribution notices from the Source form of the Work,
|
|
103
|
+
excluding those notices that do not pertain to any part of
|
|
104
|
+
the Derivative Works; and
|
|
105
|
+
|
|
106
|
+
(d) If the Work includes a "NOTICE" text file as part of its
|
|
107
|
+
distribution, then any Derivative Works that You distribute must
|
|
108
|
+
include a readable copy of the attribution notices contained
|
|
109
|
+
within such NOTICE file, excluding those notices that do not
|
|
110
|
+
pertain to any part of the Derivative Works, in at least one
|
|
111
|
+
of the following places: within a NOTICE text file distributed
|
|
112
|
+
as part of the Derivative Works; within the Source form or
|
|
113
|
+
documentation, if provided along with the Derivative Works; or,
|
|
114
|
+
within a display generated by the Derivative Works, if and
|
|
115
|
+
wherever such third-party notices normally appear. The contents
|
|
116
|
+
of the NOTICE file are for informational purposes only and
|
|
117
|
+
do not modify the License. You may add Your own attribution
|
|
118
|
+
notices within Derivative Works that You distribute, alongside
|
|
119
|
+
or as an addendum to the NOTICE text from the Work, provided
|
|
120
|
+
that such additional attribution notices cannot be construed
|
|
121
|
+
as modifying the License.
|
|
122
|
+
|
|
123
|
+
You may add Your own copyright statement to Your modifications and
|
|
124
|
+
may provide additional or different license terms and conditions
|
|
125
|
+
for use, reproduction, or distribution of Your modifications, or
|
|
126
|
+
for any such Derivative Works as a whole, provided Your use,
|
|
127
|
+
reproduction, and distribution of the Work otherwise complies with
|
|
128
|
+
the conditions stated in this License.
|
|
129
|
+
|
|
130
|
+
5. Submission of Contributions. Unless You explicitly state otherwise,
|
|
131
|
+
any Contribution intentionally submitted for inclusion in the Work
|
|
132
|
+
by You to the Licensor shall be under the terms and conditions of
|
|
133
|
+
this License, without any additional terms or conditions.
|
|
134
|
+
Notwithstanding the above, nothing herein shall supersede or modify
|
|
135
|
+
the terms of any separate license agreement you may have executed
|
|
136
|
+
with Licensor regarding such Contributions.
|
|
137
|
+
|
|
138
|
+
6. Trademarks. This License does not grant permission to use the trade
|
|
139
|
+
names, trademarks, service marks, or product names of the Licensor,
|
|
140
|
+
except as required for reasonable and customary use in describing the
|
|
141
|
+
origin of the Work and reproducing the content of the NOTICE file.
|
|
142
|
+
|
|
143
|
+
7. Disclaimer of Warranty. Unless required by applicable law or
|
|
144
|
+
agreed to in writing, Licensor provides the Work (and each
|
|
145
|
+
Contributor provides its Contributions) on an "AS IS" BASIS,
|
|
146
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
|
|
147
|
+
implied, including, without limitation, any warranties or conditions
|
|
148
|
+
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
|
|
149
|
+
PARTICULAR PURPOSE. You are solely responsible for determining the
|
|
150
|
+
appropriateness of using or redistributing the Work and assume any
|
|
151
|
+
risks associated with Your exercise of permissions under this License.
|
|
152
|
+
|
|
153
|
+
8. Limitation of Liability. In no event and under no legal theory,
|
|
154
|
+
whether in tort (including negligence), contract, or otherwise,
|
|
155
|
+
unless required by applicable law (such as deliberate and grossly
|
|
156
|
+
negligent acts) or agreed to in writing, shall any Contributor be
|
|
157
|
+
liable to You for damages, including any direct, indirect, special,
|
|
158
|
+
incidental, or consequential damages of any character arising as a
|
|
159
|
+
result of this License or out of the use or inability to use the
|
|
160
|
+
Work (including but not limited to damages for loss of goodwill,
|
|
161
|
+
work stoppage, computer failure or malfunction, or any and all
|
|
162
|
+
other commercial damages or losses), even if such Contributor
|
|
163
|
+
has been advised of the possibility of such damages.
|
|
164
|
+
|
|
165
|
+
9. Accepting Warranty or Additional Liability. While redistributing
|
|
166
|
+
the Work or Derivative Works thereof, You may choose to offer,
|
|
167
|
+
and charge a fee for, acceptance of support, warranty, indemnity,
|
|
168
|
+
or other liability obligations and/or rights consistent with this
|
|
169
|
+
License. However, in accepting such obligations, You may act only
|
|
170
|
+
on Your own behalf and on Your sole responsibility, not on behalf
|
|
171
|
+
of any other Contributor, and only if You agree to indemnify,
|
|
172
|
+
defend, and hold each Contributor harmless for any liability
|
|
173
|
+
incurred by, or claims asserted against, such Contributor by reason
|
|
174
|
+
of your accepting any such warranty or additional liability.
|
|
175
|
+
|
|
176
|
+
END OF TERMS AND CONDITIONS
|
|
177
|
+
|
|
178
|
+
APPENDIX: How to apply the Apache License to your work.
|
|
179
|
+
|
|
180
|
+
To apply the Apache License to your work, attach the following
|
|
181
|
+
boilerplate notice, with the fields enclosed by brackets "[]"
|
|
182
|
+
replaced with your own identifying information. (Don't include
|
|
183
|
+
the brackets!) The text should be enclosed in the appropriate
|
|
184
|
+
comment syntax for the file format. We also recommend that a
|
|
185
|
+
file or class name and description of purpose be included on the
|
|
186
|
+
same "printed page" as the copyright notice for easier
|
|
187
|
+
identification within third-party archives.
|
|
188
|
+
|
|
189
|
+
Copyright [yyyy] [name of copyright owner]
|
|
190
|
+
|
|
191
|
+
Licensed under the Apache License, Version 2.0 (the "License");
|
|
192
|
+
you may not use this file except in compliance with the License.
|
|
193
|
+
You may obtain a copy of the License at
|
|
194
|
+
|
|
195
|
+
http://www.apache.org/licenses/LICENSE-2.0
|
|
196
|
+
|
|
197
|
+
Unless required by applicable law or agreed to in writing, software
|
|
198
|
+
distributed under the License is distributed on an "AS IS" BASIS,
|
|
199
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
200
|
+
See the License for the specific language governing permissions and
|
|
201
|
+
limitations under the License.
|
|
202
|
+
|
package/README.md
CHANGED
|
@@ -1,3 +1,169 @@
|
|
|
1
|
-
#
|
|
1
|
+
# Quiver
|
|
2
2
|
|
|
3
|
-
|
|
3
|
+
A central skill manager for AI assistants, delivered as an MCP server.
|
|
4
|
+
|
|
5
|
+
Quiver keeps all your skills in one library, `~/.quiver`: your own skills and skills from git repositories. You decide which skills are **global** (served in every folder) and which belong to a **project**. The assistant starts Quiver's MCP server, sees the skills of the folder it works in, and loads the ones a task needs.
|
|
6
|
+
|
|
7
|
+
Skills are never copied into projects. A project only gets a small `.quiver.json` with its ID.
|
|
8
|
+
|
|
9
|
+
Skills use the standard Agent Skills format: a folder with a `SKILL.md` (YAML frontmatter with `name` and `description`) and any extra files. Existing skills and skill repositories work as they are.
|
|
10
|
+
|
|
11
|
+
## Install
|
|
12
|
+
|
|
13
|
+
Quiver is a single binary. It needs `git` on your `PATH`.
|
|
14
|
+
|
|
15
|
+
**macOS and Linux:**
|
|
16
|
+
|
|
17
|
+
```sh
|
|
18
|
+
curl -fsSL https://raw.githubusercontent.com/kheif/quiver/main/install.sh | sh
|
|
19
|
+
```
|
|
20
|
+
|
|
21
|
+
The script downloads the latest release for your system, checks its checksum and installs `quiver` into `~/.local/bin`. Set `QUIVER_VERSION=v1.0.0` for a given release, or `QUIVER_INSTALL_DIR` for another folder. Run it again to update.
|
|
22
|
+
|
|
23
|
+
**npm (macOS, Linux and Windows):**
|
|
24
|
+
|
|
25
|
+
```sh
|
|
26
|
+
npm install -g @kheif/quiver
|
|
27
|
+
```
|
|
28
|
+
|
|
29
|
+
npm installs the binary for your platform; no install script runs. If you switch Node versions with nvm, fnm or volta, run `quiver mcp install` again afterwards, because the path of `quiver` changes with the Node version.
|
|
30
|
+
|
|
31
|
+
**Go:**
|
|
32
|
+
|
|
33
|
+
```sh
|
|
34
|
+
go install github.com/kheif/quiver/cmd/quiver@latest
|
|
35
|
+
```
|
|
36
|
+
|
|
37
|
+
The archives for every platform are also on the [releases page](https://github.com/kheif/quiver/releases). To build from a clone: `make build`, which writes `bin/quiver`.
|
|
38
|
+
|
|
39
|
+
## Quickstart
|
|
40
|
+
|
|
41
|
+
```sh
|
|
42
|
+
# 1. Create the library in ~/.quiver (any other command does this too)
|
|
43
|
+
quiver init
|
|
44
|
+
|
|
45
|
+
# 2. Register the MCP server with Claude Code, once for all projects
|
|
46
|
+
quiver mcp install
|
|
47
|
+
|
|
48
|
+
# 3. In a project folder, write a skill for that project
|
|
49
|
+
cd ~/code/app
|
|
50
|
+
quiver new release-notes
|
|
51
|
+
```
|
|
52
|
+
|
|
53
|
+
`quiver new` opens the new `SKILL.md` in `$VISUAL` or `$EDITOR`. Write one sentence in `description` on when the assistant should use the skill, and the instructions below the frontmatter. Quiver commits the skill in `~/.quiver/local` and creates `~/code/app/.quiver.json`. Commit that file, so the project keeps its ID in every clone.
|
|
54
|
+
|
|
55
|
+
Then start Claude Code in `~/code/app` and ask for the task, such as "write the release notes for this version". The assistant sees `release-notes` in Quiver's skill list and loads it. You can also run it yourself as `/quiver:release-notes`.
|
|
56
|
+
|
|
57
|
+
`quiver status` shows what the assistant gets in the current folder.
|
|
58
|
+
|
|
59
|
+
## Concepts
|
|
60
|
+
|
|
61
|
+
- **Library.** `~/.quiver/local/` holds your own skills, in a git repository Quiver commits to. `~/.quiver/sources/` holds cloned skill repositories. Set `QUIVER_HOME` to use another folder.
|
|
62
|
+
- **Skill IDs.** A local skill's ID is its folder name, such as `release-notes`. A skill from a source is `<source>/<skill>`, such as `anthropic/pdf`.
|
|
63
|
+
- **Assignments.** `registry.json` stores which skills are global and which projects get which skills. A folder that is not a project gets only the global skills.
|
|
64
|
+
- **Assignments are yours.** They live in your `~/.quiver`, not in the project. A teammate who clones the project gets its `.quiver.json`, but not your skills or assignments. To share skills, put them in a git repository that everyone adds with `quiver source add`.
|
|
65
|
+
- **Projects.** A project is the folder with `.quiver.json`, found by walking up from the current folder. It is created the first time you assign a skill there. The ID survives moves and renames. Git worktrees of one repository share the committed `.quiver.json`, so they are one project with the same skills. If a folder is copied, both copies have the same ID; `quiver status` warns, and `quiver projects split` gives the copy its own.
|
|
66
|
+
- **Always-on skills.** A skill added with `--always` is loaded before the assistant's first reply, for style or rules that apply to every answer. See the limits below.
|
|
67
|
+
|
|
68
|
+
## Commands
|
|
69
|
+
|
|
70
|
+
Run `quiver help <command>` for the details and examples of each.
|
|
71
|
+
|
|
72
|
+
| Command | What it does |
|
|
73
|
+
|---|---|
|
|
74
|
+
| `quiver init` | Create the Quiver home and anything missing in it. |
|
|
75
|
+
| `quiver new <name>` | Create a local skill and assign it to this project (`--global`: every folder, `--none`: nowhere). |
|
|
76
|
+
| `quiver edit <id>` | Open a local skill in your editor, then check and commit it. |
|
|
77
|
+
| `quiver delete <id>` | Delete a local skill from the library. An assigned skill needs `--force`. |
|
|
78
|
+
| `quiver import [<dir>]` | Copy the skills in a project's `.claude/skills` into the library (`--deep`: every `SKILL.md`). |
|
|
79
|
+
| `quiver add <id>...` | Assign skills to this project, or to every folder with `--global`. `--always` makes them always-on. |
|
|
80
|
+
| `quiver remove <id>...` | Unassign skills. They stay in the library. |
|
|
81
|
+
| `quiver list` | List the library's skills and where each is assigned (`--source`, `--unassigned`, `--json`). |
|
|
82
|
+
| `quiver status` | Show the project in this folder and the skills served here. |
|
|
83
|
+
| `quiver where <id>` | Show where one skill is assigned. |
|
|
84
|
+
| `quiver source add <repo>` | Clone a skill repository: `owner/repo` (GitHub), a git URL or a local path. |
|
|
85
|
+
| `quiver source list` | List sources with their skill count and commit. |
|
|
86
|
+
| `quiver source remove <name>` | Delete a source. Refuses while its skills are assigned, unless `--force`. |
|
|
87
|
+
| `quiver update [<name>...]` | Pull the latest skills of all or some sources, and list what changed. |
|
|
88
|
+
| `quiver projects` | List projects; `rename`, `forget` and `split` manage them. |
|
|
89
|
+
| `quiver doctor` | Check the library, the assignments and the Claude Code setup (`--fix` applies the safe fixes). |
|
|
90
|
+
| `quiver mcp install` | Register the MCP server with Claude Code (`--print` shows the setup for other assistants). |
|
|
91
|
+
| `quiver mcp uninstall` | Remove it from Claude Code. |
|
|
92
|
+
| `quiver mcp` | Run the MCP server. Assistants start this. |
|
|
93
|
+
| `quiver completion <shell>` | Print the completion script for `bash`, `zsh`, `fish` or `powershell`. |
|
|
94
|
+
|
|
95
|
+
Shell completion suggests real skill IDs, sources and projects. For zsh, for example:
|
|
96
|
+
|
|
97
|
+
```sh
|
|
98
|
+
quiver completion zsh > "${fpath[1]}/_quiver"
|
|
99
|
+
```
|
|
100
|
+
|
|
101
|
+
`quiver help completion` shows the setup for each shell.
|
|
102
|
+
|
|
103
|
+
## MCP server
|
|
104
|
+
|
|
105
|
+
`quiver mcp install` runs `claude mcp add --scope user quiver -- <path to quiver> mcp`. For an assistant configured with JSON, `quiver mcp install --print` prints the entry:
|
|
106
|
+
|
|
107
|
+
```json
|
|
108
|
+
{ "mcpServers": { "quiver": { "command": "/path/to/quiver", "args": ["mcp"] } } }
|
|
109
|
+
```
|
|
110
|
+
|
|
111
|
+
The server serves the project of the folder it is started in, or of `$QUIVER_PROJECT` when that is set. It logs to `~/.quiver/logs/`.
|
|
112
|
+
|
|
113
|
+
Claude Code starts the server in the project folder. Other assistants may start it somewhere else, such as your home folder; there it serves only the global skills. Set `QUIVER_PROJECT` in that assistant's MCP config to serve a project's skills.
|
|
114
|
+
|
|
115
|
+
**Instructions.** When a session starts, the server tells the assistant which skills exist here: their IDs and descriptions, the always-on skills, and that new skills are saved with `create_skill`.
|
|
116
|
+
|
|
117
|
+
**Tools:**
|
|
118
|
+
|
|
119
|
+
| Tool | Input | Result |
|
|
120
|
+
|---|---|---|
|
|
121
|
+
| `list_skills` | — | The skills served here: ID, name, description, and `global` or `project`. |
|
|
122
|
+
| `get_skill` | `id` | The skill's instructions, its extra files and its folder. |
|
|
123
|
+
| `get_skill_file` | `id`, `path` | One extra file of a skill, such as `references/checklist.md`. Large and binary files return their path instead. |
|
|
124
|
+
| `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. |
|
|
125
|
+
|
|
126
|
+
**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.
|
|
127
|
+
|
|
128
|
+
**Live updates.** While a session runs, the server watches the library. Skills you add, remove or change show up in `list_skills` and the prompts right away. The skill list in the instructions is built once, so it changes from the next session on.
|
|
129
|
+
|
|
130
|
+
## Always-on skills: limits
|
|
131
|
+
|
|
132
|
+
- Changes take effect in the next session, because the instructions cannot change during a session.
|
|
133
|
+
- Only the skill's text is delivered. Plugin hooks, such as a per-message reminder, are not run.
|
|
134
|
+
- Subagents are not reliable: in testing, one of two subagents followed the always-on skill.
|
|
135
|
+
|
|
136
|
+
## Security
|
|
137
|
+
|
|
138
|
+
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.
|
|
139
|
+
|
|
140
|
+
- Add only sources you trust, and read their skills before you assign them.
|
|
141
|
+
- `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>`.
|
|
142
|
+
- Source skills are read-only in Quiver. To change one, copy it into your own skills.
|
|
143
|
+
- `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`.
|
|
144
|
+
|
|
145
|
+
## Uninstall
|
|
146
|
+
|
|
147
|
+
The last command deletes your own skills too. To keep them, first push `~/.quiver/local` somewhere: it is a git repository.
|
|
148
|
+
|
|
149
|
+
```sh
|
|
150
|
+
quiver mcp uninstall # remove the MCP server from Claude Code
|
|
151
|
+
rm "$(command -v quiver)" # remove the binary; with npm: npm uninstall -g @kheif/quiver
|
|
152
|
+
rm -rf ~/.quiver # delete the library
|
|
153
|
+
```
|
|
154
|
+
|
|
155
|
+
Projects keep their `.quiver.json`; delete it there if you no longer need it.
|
|
156
|
+
|
|
157
|
+
## Development
|
|
158
|
+
|
|
159
|
+
```sh
|
|
160
|
+
make build # bin/quiver
|
|
161
|
+
make test # go test ./..., including the end-to-end suite in e2e/
|
|
162
|
+
make lint # golangci-lint
|
|
163
|
+
```
|
|
164
|
+
|
|
165
|
+
See [PROJECT.md](PROJECT.md) for the design and [tasks/](tasks/README.md) for the plan.
|
|
166
|
+
|
|
167
|
+
## License
|
|
168
|
+
|
|
169
|
+
Apache License 2.0. See [LICENSE](LICENSE).
|
package/bin/quiver.js
ADDED
|
@@ -0,0 +1,43 @@
|
|
|
1
|
+
#!/usr/bin/env node
|
|
2
|
+
// Runs the quiver binary of this platform. npm installs only the platform
|
|
3
|
+
// package that matches (see optionalDependencies in package.json).
|
|
4
|
+
"use strict";
|
|
5
|
+
|
|
6
|
+
const { spawnSync } = require("node:child_process");
|
|
7
|
+
|
|
8
|
+
const packages = {
|
|
9
|
+
"darwin arm64": "@kheif/quiver-darwin-arm64",
|
|
10
|
+
"darwin x64": "@kheif/quiver-darwin-x64",
|
|
11
|
+
"linux arm64": "@kheif/quiver-linux-arm64",
|
|
12
|
+
"linux x64": "@kheif/quiver-linux-x64",
|
|
13
|
+
"win32 arm64": "@kheif/quiver-win32-arm64",
|
|
14
|
+
"win32 x64": "@kheif/quiver-win32-x64",
|
|
15
|
+
};
|
|
16
|
+
|
|
17
|
+
const pkg = packages[`${process.platform} ${process.arch}`];
|
|
18
|
+
if (!pkg) {
|
|
19
|
+
console.error(`quiver: there is no build for ${process.platform} ${process.arch}`);
|
|
20
|
+
process.exit(1);
|
|
21
|
+
}
|
|
22
|
+
const file = process.platform === "win32" ? "quiver.exe" : "quiver";
|
|
23
|
+
let bin;
|
|
24
|
+
try {
|
|
25
|
+
bin = require.resolve(`${pkg}/bin/${file}`);
|
|
26
|
+
} catch {
|
|
27
|
+
console.error(`quiver: ${pkg} is missing. Reinstall without --omit=optional: npm install -g @kheif/quiver`);
|
|
28
|
+
process.exit(1);
|
|
29
|
+
}
|
|
30
|
+
|
|
31
|
+
// QUIVER_NPM tells quiver mcp install that it runs from an npm install.
|
|
32
|
+
const r = spawnSync(bin, process.argv.slice(2), {
|
|
33
|
+
stdio: "inherit",
|
|
34
|
+
env: { ...process.env, QUIVER_NPM: "1" },
|
|
35
|
+
});
|
|
36
|
+
if (r.error) {
|
|
37
|
+
console.error(`quiver: ${r.error.message}`);
|
|
38
|
+
process.exit(1);
|
|
39
|
+
}
|
|
40
|
+
if (r.signal) {
|
|
41
|
+
process.kill(process.pid, r.signal);
|
|
42
|
+
}
|
|
43
|
+
process.exit(r.status ?? 1);
|
package/package.json
CHANGED
|
@@ -1,6 +1,36 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@kheif/quiver",
|
|
3
|
-
"version": "
|
|
4
|
-
"
|
|
5
|
-
"
|
|
6
|
-
|
|
3
|
+
"version": "1.0.0",
|
|
4
|
+
"description": "Central skill manager for AI assistants, delivered as an MCP server.",
|
|
5
|
+
"license": "Apache-2.0",
|
|
6
|
+
"keywords": [
|
|
7
|
+
"mcp",
|
|
8
|
+
"agent-skills",
|
|
9
|
+
"claude-code",
|
|
10
|
+
"skills",
|
|
11
|
+
"cli"
|
|
12
|
+
],
|
|
13
|
+
"homepage": "https://github.com/kheif/quiver#readme",
|
|
14
|
+
"bugs": "https://github.com/kheif/quiver/issues",
|
|
15
|
+
"repository": {
|
|
16
|
+
"type": "git",
|
|
17
|
+
"url": "git+https://github.com/kheif/quiver.git"
|
|
18
|
+
},
|
|
19
|
+
"bin": {
|
|
20
|
+
"quiver": "bin/quiver.js"
|
|
21
|
+
},
|
|
22
|
+
"files": [
|
|
23
|
+
"bin"
|
|
24
|
+
],
|
|
25
|
+
"engines": {
|
|
26
|
+
"node": ">=18"
|
|
27
|
+
},
|
|
28
|
+
"optionalDependencies": {
|
|
29
|
+
"@kheif/quiver-darwin-arm64": "1.0.0",
|
|
30
|
+
"@kheif/quiver-darwin-x64": "1.0.0",
|
|
31
|
+
"@kheif/quiver-linux-arm64": "1.0.0",
|
|
32
|
+
"@kheif/quiver-linux-x64": "1.0.0",
|
|
33
|
+
"@kheif/quiver-win32-arm64": "1.0.0",
|
|
34
|
+
"@kheif/quiver-win32-x64": "1.0.0"
|
|
35
|
+
}
|
|
36
|
+
}
|