yourskills 0.1.2 → 0.1.4

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 (3) hide show
  1. package/README.md +36 -15
  2. package/dist/main.js +5419 -2027
  3. package/package.json +1 -1
package/README.md CHANGED
@@ -6,7 +6,8 @@ Install the agent skills and bundles your team publishes, from the terminal.
6
6
  commit your registry pins. The registry never sends skill files: they are fetched from
7
7
  your own git host with your own credentials, so a private skill stays private.
8
8
 
9
- Documentation lives at **[yourskills.store](https://yourskills.store)**.
9
+ Documentation lives at **[yourskills.store](https://yourskills.store)**. The package is
10
+ **[npmjs.com/package/yourskills](https://www.npmjs.com/package/yourskills)**.
10
11
 
11
12
  ## Install
12
13
 
@@ -27,34 +28,54 @@ yourskills login
27
28
  ## Use
28
29
 
29
30
  ```bash
30
- yourskills # the command palette, if you would rather not memorise
31
+ yourskills # opens the command palette, if you would rather not memorise
31
32
  yourskills search pull request # find something
32
- yourskills bundle backend-dev # install a bundle at its pinned commits
33
+ yourskills bundles # the bundles your team publishes
34
+ yourskills add backend-dev # install a bundle at its pinned commits
33
35
  yourskills add create-pr # or one skill
34
36
  ```
35
37
 
38
+ One verb for both. A name is a skill or a bundle and your registry knows which, so you
39
+ only have to know what you want. `bundle:<name>` and `skill:<name>` force the kind, which
40
+ is worth typing in a script and nowhere else. `yourskills bundle <name>` is the old
41
+ spelling of `add <name>` and still works.
42
+
36
43
  Installs are **global by default**, for every agent you have. Add `-p` to install into the
37
44
  current project instead, which records them in a `yourskills.json` you commit. A teammate
38
45
  who clones that repository runs `yourskills install` and gets the same skills at the same
39
46
  commits.
40
47
 
41
48
  ```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
49
+ yourskills installed # what is on this machine, and at which commit
50
+ yourskills outdated # what your registry has moved on from
51
+ yourskills update # catch up
52
+ yourskills remove <name> # a skill, or a bundle and every skill it brought in
53
+ yourskills doctor # when something is wrong and you want to know what
47
54
  ```
48
55
 
49
56
  ## Hooks
50
57
 
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.
58
+ The session-start hook registers itself, once per machine, at the end of your first login,
59
+ and prints where it wrote and how to undo it. You do not run `yourskills hooks install`
60
+ for it. Once a day, at the start of a session, it installs any
61
+ skill your registry has moved on to and tells you what it changed:
62
+
63
+ ```
64
+ yourskills: updated 2 skills to the ref your registry pins
65
+ create-pr a1b2c3d -> e4f5a6b
66
+ review-code 9876543 -> 1234567
67
+ ```
68
+
69
+ It only touches skills already in your manifest, only moves them to the commit your own
70
+ registry pins, and says so every time. `yourskills config set autoUpdate false` keeps the
71
+ check and stops the installing.
72
+
73
+ Usage counting is a separate hook and never registers itself. It is **opt in**, with
74
+ `yourskills hooks install --track`. When it is on, an invocation sends the skill's registry
75
+ id, the commit you installed it at, which agent ran it, and when. The CLI never sends a
76
+ user identifier. `YOURSKILLS_NO_TRACK=1` turns it off outright.
53
77
 
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.
78
+ `yourskills hooks status` shows what is registered and where. `yourskills hooks uninstall`
79
+ removes what we registered and nothing else.
59
80
 
60
81
  Run `yourskills --help` for the full command list.