skillcask 0.7.0 → 0.8.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/README.md CHANGED
@@ -135,7 +135,7 @@ local = ".skills" # project skills
135
135
  min-release-age = "3d" # cooldown for add/update; "0" disables
136
136
  allow-ranges = true # false: every version must be exact
137
137
  packagist = true # false: drop the implicit Packagist repository
138
- github-requires = false # true: dependencies may come from GitHub
138
+ github-requires = false # true: dependencies may come from GitHub or git URLs
139
139
  allow-sources = ["acme", "own", "packagist", "github"] # only these sources; default: all
140
140
  deny-patterns = false # true: risky patterns in new skill text fail instead of warning
141
141
  ```
@@ -222,6 +222,7 @@ version: 1.2.0
222
222
  requires:
223
223
  acme/security-review: ^1.0
224
224
  github:mattpocock/skills/pr: main
225
+ "git:https://git.example.com/team/skills.git#review": ^2.0
225
226
  ---
226
227
  ```
227
228
 
@@ -229,7 +230,7 @@ requires:
229
230
  cooldown, same hashes, one version per package (the highest one every requirer accepts). They
230
231
  stay out of `skills.toml`; the lock records each package's `requires` and switches to
231
232
  `version = 2`. A dependency is looked up only in your repositories, in order, then Packagist;
232
- a `github:` one needs `github-requires = true`. `remove` drops dependencies nobody needs any
233
+ a `github:` or `git:<url>[#skill]` one needs `github-requires = true`. `remove` drops dependencies nobody needs any
233
234
  more, and `status` shows them as `via <requirer>`.
234
235
 
235
236
  ### Name conflicts
@@ -261,7 +262,10 @@ skillcask -g install --frozen # e.g. from a dotfiles repository
261
262
  - Skills go to `~/.agents/skills` (read by most agents), with links in `~/.claude/skills`
262
263
  (`[agents] targets`, see Agents). Links are absolute, so a symlinked
263
264
  `~/.claude` works. `[agents] local` does not apply.
264
- - Personal skills you wrote by hand stay where they are and are not linked anywhere.
265
+ - Personal skills you wrote by hand stay where they are and are not linked anywhere. `status`
266
+ lists them, and copies other tools put in a target, as `not managed`; `status --json` names the
267
+ source `npx skills` recorded for one. `skillcask -g add --adopt <source>` moves such a skill to
268
+ `~/.config/skillcask/adopted/` and installs the package's skill of the same name in its place.
265
269
  - The list of managed paths is `~/.agents/skills/.skillcask-installed`, local to the machine;
266
270
  nothing touches git.
267
271
 
@@ -278,18 +282,19 @@ Every command except `publish` and `validate` takes `-g, --global`.
278
282
  | `remove <vendor/name>…` | Drop from manifest and lock; delete files, links and gitignore lines. |
279
283
  | `install [--frozen]` | Install the lock. `--frozen` (implied by `CI`) fails when the lock is out of date. |
280
284
  | `update [vendor/name…] [--diff]` | Re-resolve within constraints. `--diff` prints what changes in each updated or added package; it does not ask before installing. |
281
- | `outdated [--strict]` | Newer versions, and when cooled-down ones become eligible. `--strict` exits 1 when `update` would lock a newer version. |
282
- | `diff [vendor/name] [--to constraint]` | Unified diff of skill files from the locked version to the one `update` would lock, see below. |
283
- | `info <vendor/name[@constraint]\|github:owner/repo\|skill>` | A package's skills, versions, description, license and requirements, or which package installs a skill. |
285
+ | `outdated [--strict]` | Newer versions, when cooled-down ones become eligible, and GitHub or git tags moved since they were locked. `--strict` exits 1 when `update` would lock a newer version. |
286
+ | `diff [vendor/name] [--to constraint\|--from old.lock]` | Unified diff of skill files from the locked version to the one `update` would lock, or from an older lock to `skills.lock`, see below. |
287
+ | `info <vendor/name[@constraint]\|github:owner/repo\|git:url\|skill>` | A package's skills, versions, description, license and requirements, or which package installs a skill. |
284
288
  | `status` | Exit 1 when manifest, lock or installed files disagree. |
285
289
  | `doctor [--fix]` | Broken or committed links, stale gitignore block, modified skills; lists each check it ran. |
290
+ | `audit [--json\|--sarif]` | What each installed skill reaches (commands, hosts, paths, env vars, scripts) and its findings: modified files, risky lines, invisible characters. Exit 1 on any finding. |
286
291
  | `search <query>` | Packagist (`type=ai-agent-skill`) and skill packages of the other repositories, GitLab included. |
287
292
  | `auth set\|remove <host>` | Keep a registry token in git's credential helper (Keychain, Credential Manager, libsecret). |
288
293
  | `publish --vendor v --base-url URL --out DIR [--inline] [--dist-url TPL] [paths…]` | Build a static Composer repository from a monorepo. |
289
294
  | `validate [paths…]` | Check `SKILL.md` files against the Agent Skills spec, see below. |
290
295
  | `<other>` | Runs `skillcask-<other>` from `PATH`, like git and cargo plugins. |
291
296
 
292
- `status`, `outdated`, `info`, `search` and `doctor` take `--json`: one JSON document on one line of
297
+ `status`, `outdated`, `info`, `search`, `doctor` and `audit` take `--json`: one JSON document on one line of
293
298
  stdout, with the same exit code; warnings and errors stay on stderr. Package text in it is
294
299
  escaped as in the terminal (`<U+202E>`). For example `skillcask outdated --json | jq
295
300
  '.packages[] | select(.within != .locked)'`.
@@ -322,6 +327,26 @@ before it writes the lock, then installs without asking: run `skillcask diff` fi
322
327
  and decide. A scheduled CI job can run `skillcask outdated --strict` (exit 1 when something is to
323
328
  update), then `skillcask update --diff` and open a pull request with the output.
324
329
 
330
+ **Reviewing a lock change:** `skillcask diff --from old.lock` prints the same diff from the
331
+ versions in another lock to those in `skills.lock`, plus the packages it drops, so a reviewer
332
+ sees the skill text a pull request brings in instead of new versions and hashes. Each new dist
333
+ is verified against `skills.lock` as `install` would, and the policy decides which repositories
334
+ may be fetched. skillcask does not run git; the job fetches the old lock:
335
+
336
+ ```yaml
337
+ # GitLab CI: print the diff in the merge request pipeline
338
+ skills-diff:
339
+ rules:
340
+ - if: $CI_PIPELINE_SOURCE == "merge_request_event"
341
+ changes: [skills.lock]
342
+ script:
343
+ - git fetch --depth 1 origin "$CI_MERGE_REQUEST_TARGET_BRANCH_NAME"
344
+ - git show FETCH_HEAD:skills.lock | skillcask diff --from -
345
+ ```
346
+
347
+ `--from -` reads the old lock from stdin. On GitHub the same lines run in a `pull_request` job with `$GITHUB_BASE_REF`; posting the
348
+ output as a comment is up to the CI.
349
+
325
350
  **Where a skill comes from:** `skillcask info vendor/name` shows the package's skills with their
326
351
  descriptions, its versions, description, license, `abandoned` and `requires`, for the locked
327
352
  version or else the newest one `add` would take (`@constraint` for another); `info
@@ -432,6 +457,24 @@ too young falls back to an older commit when the server supports partial fetches
432
457
  Skills that teach shell setup trigger some of these legitimately, so they are warnings. With
433
458
  `deny-patterns = true` under `[policy]` (or enforced in `config.toml`) they fail the command
434
459
  with exit 1 and nothing is written.
460
+ - `skillcask audit` reviews what is installed now, every skill in `.agents/skills` and the project
461
+ skills: the commands its shell code blocks run, the hosts of its URLs, the paths in the home
462
+ directory or under system roots, the environment variables it reads and the files an agent could
463
+ run. That is read from the text, so it is a hint for review, not a sandbox. It also reports a
464
+ locked skill that differs from the lock, and every risky line and invisible character above,
465
+ with no limit per file, and exits 1 on any of them. `--sarif` prints a SARIF 2.1.0 log for code
466
+ scanning, e.g. in GitHub Actions:
467
+
468
+ ```yaml
469
+ - uses: puniserv/skillcask@v0.8.0
470
+ with:
471
+ args: install --frozen
472
+ - run: skillcask audit --sarif > skills.sarif
473
+ - uses: github/codeql-action/upload-sarif@v3
474
+ if: always()
475
+ with:
476
+ sarif_file: skills.sarif
477
+ ```
435
478
  - Plain git sources pin the commit; the lock's `dist-sha256` hashes the commit's file list
436
479
  (path, mode, sha256 of the content), so it does not depend on how a server packs objects.
437
480
  - `min-release-age` for GitHub sources uses times GitHub sets: release publication for tags,
@@ -19,7 +19,7 @@
19
19
  "hasInstallScript": true,
20
20
  "license": "MIT OR Apache-2.0",
21
21
  "name": "skillcask",
22
- "version": "0.7.0"
22
+ "version": "0.8.0"
23
23
  },
24
24
  "node_modules/detect-libc": {
25
25
  "engines": {
@@ -48,5 +48,5 @@
48
48
  }
49
49
  },
50
50
  "requires": true,
51
- "version": "0.7.0"
51
+ "version": "0.8.0"
52
52
  }
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "artifactDownloadUrls": [
3
- "https://github.com/puniserv/skillcask/releases/download/v0.7.0"
3
+ "https://github.com/puniserv/skillcask/releases/download/v0.8.0"
4
4
  ],
5
5
  "bin": {
6
6
  "skillcask": "run-skillcask.js"
@@ -104,7 +104,7 @@
104
104
  "zipExt": ".tar.xz"
105
105
  }
106
106
  },
107
- "version": "0.7.0",
107
+ "version": "0.8.0",
108
108
  "volta": {
109
109
  "node": "18.14.1",
110
110
  "npm": "9.5.0"