yourskills 0.1.1 → 0.1.3

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 +24 -10
  2. package/dist/main.js +2535 -880
  3. package/package.json +1 -1
package/README.md CHANGED
@@ -17,17 +17,17 @@ npm i -g yourskills
17
17
  Needs **Node 22.20.0 or later**. You do not need Bun, and you do not need to install the
18
18
  `skills` command separately: it ships as a dependency.
19
19
 
20
- Point the command at your registry, then sign in:
20
+ Then sign in. There is no address to configure: the command already knows where your
21
+ registry is.
21
22
 
22
23
  ```bash
23
- yourskills config set server https://api.yourskills.store
24
24
  yourskills login
25
25
  ```
26
26
 
27
27
  ## Use
28
28
 
29
29
  ```bash
30
- yourskills # the command palette, if you would rather not memorise
30
+ yourskills # opens the command palette, if you would rather not memorise
31
31
  yourskills search pull request # find something
32
32
  yourskills bundle backend-dev # install a bundle at its pinned commits
33
33
  yourskills add create-pr # or one skill
@@ -48,13 +48,27 @@ yourskills doctor # when something is wrong and you want to know what
48
48
 
49
49
  ## Hooks
50
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.
51
+ The session-start hook registers itself, once per machine, at the end of your first login,
52
+ and prints where it wrote and how to undo it. You do not run `yourskills hooks install`
53
+ for it. Once a day, at the start of a session, it installs any
54
+ skill your registry has moved on to and tells you what it changed:
53
55
 
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.
56
+ ```
57
+ yourskills: updated 2 skills to the ref your registry pins
58
+ create-pr a1b2c3d -> e4f5a6b
59
+ review-code 9876543 -> 1234567
60
+ ```
61
+
62
+ It only touches skills already in your manifest, only moves them to the commit your own
63
+ registry pins, and says so every time. `yourskills config set autoUpdate false` keeps the
64
+ check and stops the installing.
65
+
66
+ Usage counting is a separate hook and never registers itself. It is **opt in**, with
67
+ `yourskills hooks install --track`. When it is on, an invocation sends the skill's registry
68
+ id, the commit you installed it at, which agent ran it, and when. The CLI never sends a
69
+ user identifier. `YOURSKILLS_NO_TRACK=1` turns it off outright.
70
+
71
+ `yourskills hooks status` shows what is registered and where. `yourskills hooks uninstall`
72
+ removes what we registered and nothing else.
59
73
 
60
74
  Run `yourskills --help` for the full command list.