yourskills 0.1.0 → 0.1.1
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/README.md +60 -0
- package/dist/main.js +1396 -15
- package/package.json +5 -9
package/README.md
ADDED
|
@@ -0,0 +1,60 @@
|
|
|
1
|
+
# yourskills
|
|
2
|
+
|
|
3
|
+
Install the agent skills and bundles your team publishes, from the terminal.
|
|
4
|
+
|
|
5
|
+
`yourskills` asks your organization's registry where a skill lives and installs it at the
|
|
6
|
+
commit your registry pins. The registry never sends skill files: they are fetched from
|
|
7
|
+
your own git host with your own credentials, so a private skill stays private.
|
|
8
|
+
|
|
9
|
+
Documentation lives at **[yourskills.store](https://yourskills.store)**.
|
|
10
|
+
|
|
11
|
+
## Install
|
|
12
|
+
|
|
13
|
+
```bash
|
|
14
|
+
npm i -g yourskills
|
|
15
|
+
```
|
|
16
|
+
|
|
17
|
+
Needs **Node 22.20.0 or later**. You do not need Bun, and you do not need to install the
|
|
18
|
+
`skills` command separately: it ships as a dependency.
|
|
19
|
+
|
|
20
|
+
Point the command at your registry, then sign in:
|
|
21
|
+
|
|
22
|
+
```bash
|
|
23
|
+
yourskills config set server https://api.yourskills.store
|
|
24
|
+
yourskills login
|
|
25
|
+
```
|
|
26
|
+
|
|
27
|
+
## Use
|
|
28
|
+
|
|
29
|
+
```bash
|
|
30
|
+
yourskills # the command palette, if you would rather not memorise
|
|
31
|
+
yourskills search pull request # find something
|
|
32
|
+
yourskills bundle backend-dev # install a bundle at its pinned commits
|
|
33
|
+
yourskills add create-pr # or one skill
|
|
34
|
+
```
|
|
35
|
+
|
|
36
|
+
Installs are **global by default**, for every agent you have. Add `-p` to install into the
|
|
37
|
+
current project instead, which records them in a `yourskills.json` you commit. A teammate
|
|
38
|
+
who clones that repository runs `yourskills install` and gets the same skills at the same
|
|
39
|
+
commits.
|
|
40
|
+
|
|
41
|
+
```bash
|
|
42
|
+
yourskills installed # what is on this machine, and at which commit
|
|
43
|
+
yourskills outdated # what your registry has moved on from
|
|
44
|
+
yourskills update # catch up
|
|
45
|
+
yourskills remove <skill>
|
|
46
|
+
yourskills doctor # when something is wrong and you want to know what
|
|
47
|
+
```
|
|
48
|
+
|
|
49
|
+
## Hooks
|
|
50
|
+
|
|
51
|
+
`yourskills hooks install` registers a session-start check with your agent, so it can tell
|
|
52
|
+
you when an installed skill has moved. It never writes skill files on its own.
|
|
53
|
+
|
|
54
|
+
Usage counting is separate and **opt in**, with `yourskills hooks install --track`. When it
|
|
55
|
+
is on, an invocation sends the skill's registry id, the commit you installed it at, which
|
|
56
|
+
agent ran it, and when. The CLI never sends a user identifier. `YOURSKILLS_NO_TRACK=1`
|
|
57
|
+
turns it off outright, and `yourskills hooks uninstall` removes what we registered and
|
|
58
|
+
nothing else.
|
|
59
|
+
|
|
60
|
+
Run `yourskills --help` for the full command list.
|