skillcask 0.7.0 → 0.9.0

package/README.md

@@ -135,7 +135,7 @@ local = ".skills"        # project skills
 min-release-age = "3d"   # cooldown for add/update; "0" disables
 allow-ranges = true      # false: every version must be exact
 packagist = true         # false: drop the implicit Packagist repository
-github-requires = false  # true: dependencies may come from GitHub
+github-requires = false  # true: dependencies may come from GitHub or git URLs
 allow-sources = ["acme", "own", "packagist", "github"]   # only these sources; default: all
 deny-patterns = false    # true: risky patterns in new skill text fail instead of warning
 ```
@@ -161,6 +161,9 @@ follow `config.toml`.
 # ~/.config/skillcask/config.toml
 [agents]
 targets = ["claude", "kiro"]
+
+[search]
+skills-sh = true   # search also asks skills.sh (it receives the query); written by search --remember
 ```
 
 When a target is dropped, the next `install` removes the links skillcask made there; `doctor`
@@ -222,6 +225,7 @@ version: 1.2.0
 requires:
   acme/security-review: ^1.0
   github:mattpocock/skills/pr: main
+  "git:https://git.example.com/team/skills.git#review": ^2.0
 ---
 ```
 
@@ -229,7 +233,7 @@ requires:
 cooldown, same hashes, one version per package (the highest one every requirer accepts). They
 stay out of `skills.toml`; the lock records each package's `requires` and switches to
 `version = 2`. A dependency is looked up only in your repositories, in order, then Packagist;
-a `github:` one needs `github-requires = true`. `remove` drops dependencies nobody needs any
+a `github:` or `git:<url>[#skill]` one needs `github-requires = true`. `remove` drops dependencies nobody needs any
 more, and `status` shows them as `via <requirer>`.
 
 ### Name conflicts
@@ -261,13 +265,16 @@ skillcask -g install --frozen    # e.g. from a dotfiles repository
 - Skills go to `~/.agents/skills` (read by most agents), with links in `~/.claude/skills`
   (`[agents] targets`, see Agents). Links are absolute, so a symlinked
   `~/.claude` works. `[agents] local` does not apply.
-- Personal skills you wrote by hand stay where they are and are not linked anywhere.
+- Personal skills you wrote by hand stay where they are and are not linked anywhere. `status`
+  lists them, and copies other tools put in a target, as `not managed`; `status --json` names the
+  source `npx skills` recorded for one. `skillcask -g add --adopt <source>` moves such a skill to
+  `~/.config/skillcask/adopted/` and installs the package's skill of the same name in its place.
 - The list of managed paths is `~/.agents/skills/.skillcask-installed`, local to the machine;
   nothing touches git.
 
 ### Commands
 
-Every command except `publish` and `validate` takes `-g, --global`.
+Every command except `publish`, `validate` and `projects` takes `-g, --global`.
 
 | Command | |
 |---|---|
@@ -278,20 +285,26 @@ Every command except `publish` and `validate` takes `-g, --global`.
 | `remove <vendor/name>…` | Drop from manifest and lock; delete files, links and gitignore lines. |
 | `install [--frozen]` | Install the lock. `--frozen` (implied by `CI`) fails when the lock is out of date. |
 | `update [vendor/name…] [--diff]` | Re-resolve within constraints. `--diff` prints what changes in each updated or added package; it does not ask before installing. |
-| `outdated [--strict]` | Newer versions, and when cooled-down ones become eligible. `--strict` exits 1 when `update` would lock a newer version. |
-| `diff [vendor/name] [--to constraint]` | Unified diff of skill files from the locked version to the one `update` would lock, see below. |
-| `info <vendor/name[@constraint]\|github:owner/repo\|skill>` | A package's skills, versions, description, license and requirements, or which package installs a skill. |
-| `status` | Exit 1 when manifest, lock or installed files disagree. |
+| `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. |
+| `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. |
+| `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. |
+| `status` | Exit 1 when manifest, lock or installed files disagree. Also lists the repositories in use (name, type, URL without credentials) and whether `allow-sources` admits each. |
 | `doctor [--fix]` | Broken or committed links, stale gitignore block, modified skills; lists each check it ran. |
-| `search <query>` | Packagist (`type=ai-agent-skill`) and skill packages of the other repositories, GitLab included. |
+| `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. |
+| `search <query> [--skills-sh\|--no-skills-sh [--remember]]` | Packagist (`type=ai-agent-skill`) and skill packages of the other repositories, GitLab included; with skills.sh on, also the GitHub skills it lists, as `github:owner/repo/skill` with their install count. skills.sh is off until you turn it on, since it receives the query: the first search in a terminal asks once, `--remember` saves a flag's choice, both in `config.toml`. |
 | `auth set\|remove <host>` | Keep a registry token in git's credential helper (Keychain, Credential Manager, libsecret). |
 | `publish --vendor v --base-url URL --out DIR [--inline] [--dist-url TPL] [paths…]` | Build a static Composer repository from a monorepo. |
 | `validate [paths…]` | Check `SKILL.md` files against the Agent Skills spec, see below. |
+| `projects [dirs…]` | Directories that hold `skills.toml` under the given ones (default: the current one), up to 6 levels down; hidden directories, `node_modules`, `vendor`, `target` and `Library` are skipped. |
+| `ui` | A terminal UI over the commands above: skills with their state and updates, `info`, SKILL.md and `audit` per skill, add, adopt, update (diff first), remove, doctor, a filter of the list, search of the registries (and skills.sh, asked once), the repositories in use (`R`) and a projects picker; `g` switches between the project and `--global`. |
 | `<other>` | Runs `skillcask-<other>` from `PATH`, like git and cargo plugins. |
 
-`status`, `outdated`, `info`, `search` and `doctor` take `--json`: one JSON document on one line of
+`status`, `outdated`, `info`, `search`, `doctor`, `audit` and `projects` take `--json`: one JSON document on one line of
 stdout, with the same exit code; warnings and errors stay on stderr. Package text in it is
-escaped as in the terminal (`<U+202E>`). For example `skillcask outdated --json | jq
+escaped as in the terminal (`<U+202E>`). `status --json` has `repositories`
+(`[{"name", "type", "url", "allowed"}]`); `search --json` results carry `source` (the repository
+name, or `skills.sh`) and `installs`, and the document has `"skills-sh": true|false|null` (`null`:
+never decided). For example `skillcask outdated --json | jq
 '.packages[] | select(.within != .locked)'`.
 
 Exit codes: 0 ok, 1 manifest/lock/status problems, 2 authentication, 3 network, 4 hash mismatch,
@@ -322,6 +335,26 @@ before it writes the lock, then installs without asking: run `skillcask diff` fi
 and decide. A scheduled CI job can run `skillcask outdated --strict` (exit 1 when something is to
 update), then `skillcask update --diff` and open a pull request with the output.
 
+**Reviewing a lock change:** `skillcask diff --from old.lock` prints the same diff from the
+versions in another lock to those in `skills.lock`, plus the packages it drops, so a reviewer
+sees the skill text a pull request brings in instead of new versions and hashes. Each new dist
+is verified against `skills.lock` as `install` would, and the policy decides which repositories
+may be fetched. skillcask does not run git; the job fetches the old lock:
+
+```yaml
+# GitLab CI: print the diff in the merge request pipeline
+skills-diff:
+  rules:
+    - if: $CI_PIPELINE_SOURCE == "merge_request_event"
+      changes: [skills.lock]
+  script:
+    - git fetch --depth 1 origin "$CI_MERGE_REQUEST_TARGET_BRANCH_NAME"
+    - git show FETCH_HEAD:skills.lock | skillcask diff --from -
+```
+
+`--from -` reads the old lock from stdin. On GitHub the same lines run in a `pull_request` job with `$GITHUB_BASE_REF`; posting the
+output as a comment is up to the CI.
+
 **Where a skill comes from:** `skillcask info vendor/name` shows the package's skills with their
 descriptions, its versions, description, license, `abandoned` and `requires`, for the locked
 version or else the newest one `add` would take (`@constraint` for another); `info
@@ -432,6 +465,24 @@ too young falls back to an older commit when the server supports partial fetches
   Skills that teach shell setup trigger some of these legitimately, so they are warnings. With
   `deny-patterns = true` under `[policy]` (or enforced in `config.toml`) they fail the command
   with exit 1 and nothing is written.
+- `skillcask audit` reviews what is installed now, every skill in `.agents/skills` and the project
+  skills: the commands its shell code blocks run, the hosts of its URLs, the paths in the home
+  directory or under system roots, the environment variables it reads and the files an agent could
+  run. That is read from the text, so it is a hint for review, not a sandbox. It also reports a
+  locked skill that differs from the lock, and every risky line and invisible character above,
+  with no limit per file, and exits 1 on any of them. `--sarif` prints a SARIF 2.1.0 log for code
+  scanning, e.g. in GitHub Actions:
+
+  ```yaml
+  - uses: puniserv/skillcask@v0.8.0
+    with:
+      args: install --frozen
+  - run: skillcask audit --sarif > skills.sarif
+  - uses: github/codeql-action/upload-sarif@v3
+    if: always()
+    with:
+      sarif_file: skills.sarif
+  ```
 - Plain git sources pin the commit; the lock's `dist-sha256` hashes the commit's file list
   (path, mode, sha256 of the content), so it does not depend on how a server packs objects.
 - `min-release-age` for GitHub sources uses times GitHub sets: release publication for tags,

package/npm-shrinkwrap.json

@@ -19,7 +19,7 @@
       "hasInstallScript": true,
       "license": "MIT OR Apache-2.0",
       "name": "skillcask",
-      "version": "0.7.0"
+      "version": "0.9.0"
     },
     "node_modules/detect-libc": {
       "engines": {
@@ -48,5 +48,5 @@
     }
   },
   "requires": true,
-  "version": "0.7.0"
+  "version": "0.9.0"
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "artifactDownloadUrls": [
-    "https://github.com/puniserv/skillcask/releases/download/v0.7.0"
+    "https://github.com/puniserv/skillcask/releases/download/v0.9.0"
   ],
   "bin": {
     "skillcask": "run-skillcask.js"
@@ -104,7 +104,7 @@
       "zipExt": ".tar.xz"
     }
   },
-  "version": "0.7.0",
+  "version": "0.9.0",
   "volta": {
     "node": "18.14.1",
     "npm": "9.5.0"