skillcask 0.2.0 → 0.4.0

package/README.md

@@ -93,8 +93,12 @@ Codex lists both.
 
 ```toml
 [repositories]
-# Packagist is the implicit last repository.
 acme = { type = "composer", url = "https://git.example.com/api/v4/group/42/-/packages/composer/packages.json" }
+# A repository you review yourself can skip the cooldown; the others keep it.
+own = { url = "https://git.example.com/own/packages.json", min-release-age = "0" }
+# Default sources, written by `init`; `= false` turns one off. Packagist is always searched last.
+packagist = { url = "https://repo.packagist.org" }
+github = { type = "github", url = "https://api.github.com" }   # GitHub Enterprise: its API URL
 
 [skills]
 "netresearch/agent-jira-skill" = "^3.34"
@@ -111,12 +115,64 @@ 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
+allow-sources = ["acme", "own", "packagist", "github"]   # only these sources; default: all
 ```
 
 Constraints follow Composer semantics: `^0.3` means `>=0.3.0 <0.4.0`, `~1.2` means
 `>=1.2 <2.0`, and pre-releases are only selected when the constraint names a stability
 (`^1.0@beta`).
 
+### Allowed sources and policy for every project
+
+`allow-sources` lists the only places skills may come from: repository names, `packagist`,
+`github`, or `https://` URL prefixes (`https://api.github.com/repos/acme/` allows one GitHub
+organisation). Other repositories get no request, and `install` refuses a lock entry from them,
+also with `--frozen`, so a committed lock cannot bring them back. Dependencies follow the same
+rule.
+
+Policy can also come from `config.toml` next to the global manifest (`~/.config/skillcask`) and
+from the environment. The first layer that sets a key wins:
+
+1. `SKILLCASK_ALLOW_SOURCES`, `SKILLCASK_MIN_RELEASE_AGE`, `SKILLCASK_ALLOW_RANGES`,
+   `SKILLCASK_PACKAGIST`, `SKILLCASK_GITHUB_REQUIRES` (overriding an enforced key prints a
+   warning);
+2. keys `config.toml` lists in `enforce`: a project that sets them otherwise fails;
+3. `[policy]` in `skills.toml`;
+4. the other keys of `config.toml`, as defaults.
+
+```toml
+# ~/.config/skillcask/config.toml: only the company registry and GitHub, in every project
+[policy]
+allow-sources = ["https://gitlab.example.com/", "github"]
+enforce = ["allow-sources"]
+```
+
+`config.toml` and the environment take URL prefixes, not repository names, since a name means
+whatever a project calls it. `skillcask status` prints each key that is set and where it came
+from.
+
+### Dependencies
+
+A skill that needs other skills lists them in its `SKILL.md`:
+
+```yaml
+---
+name: gitlab-branch-mr
+version: 1.2.0
+requires:
+  acme/security-review: ^1.0
+  github:mattpocock/skills/pr: main
+---
+```
+
+`add`, `install` and `update` resolve, lock and install them like your own entries: same
+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
+more, and `status` shows them as `via <requirer>`.
+
 ### Name conflicts
 
 Skills have no namespaces: an agent knows a skill by its name. Two skills with the same name in
@@ -165,13 +221,19 @@ Every command except `publish` takes `-g, --global`.
 | `outdated` | Newer versions, and when cooled-down ones become eligible. |
 | `status` | Exit 1 when manifest, lock or installed files disagree. |
 | `doctor [--fix]` | Broken or committed links, stale gitignore block, modified skills. |
-| `search <query>` | Packagist (`type=ai-agent-skill`) and listed private packages. |
+| `search <query>` | Packagist (`type=ai-agent-skill`) and skill packages of the other repositories, GitLab included. |
+| `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. |
 | `<other>` | Runs `skillcask-<other>` from `PATH`, like git and cargo plugins. |
 
 Exit codes: 0 ok, 1 manifest/lock/status problems, 2 authentication, 3 network, 4 hash mismatch,
 5 IO or archive error.
 
+Output is coloured in a terminal (`NO_COLOR` turns it off, `CLICOLOR_FORCE` on) and errors name
+the next step on a `hint:` line. For coding agents, `--agent` or `SKILLCASK_AGENT=1` prints terse,
+uncoloured, tab-separated output with only the rows that need action; it is on by itself when
+`AI_AGENT` or `CLAUDECODE=1` is set, unless `SKILLCASK_AGENT=0`.
+
 ### Skills from GitHub and skills.sh
 
 [skills.sh](https://skills.sh) lists skills as `owner/repo/skill`, for example
@@ -229,11 +291,16 @@ what you picked.
   and paths that collide by case or Unicode form fail a skill that contains them, and are
   skipped outside the selected skills.
 - No package code runs, ever. No telemetry.
-- `min-release-age` for GitHub sources reads commit dates, which the committer sets. A
-  backdated commit passes the cooldown; reviewing what `add`/`update` change in `skills.lock` is
-  the real check there.
+- `min-release-age` for GitHub sources uses times GitHub sets: release publication for tags,
+  push times from the Activity API for branches. A tag without a release, or a ref GitHub lists no
+  pushes for, falls back to commit dates, which the committer sets; reviewing what `add`/`update`
+  change in `skills.lock` is the real check there.
 - Credentials come from Composer's `auth.json` / `COMPOSER_AUTH` (`http-basic`, `bearer`,
-  `gitlab-token`, `gitlab-oauth`) and are never printed. In GitLab CI use `http-basic` with the
+  `gitlab-token`, `gitlab-oauth`), then from git's credential helper, and are never printed.
+  `skillcask auth set git.example.com` keeps a token in the macOS Keychain, the Windows Credential
+  Manager or libsecret instead of a plain-text file (the default username `PRIVATE-TOKEN` sends
+  GitLab's header; `--username oauth2` a Bearer token). `SKILLCASK_GIT_CREDENTIALS=0` turns the
+  helper off. In GitLab CI use `http-basic` with the
   user `gitlab-ci-token` and the password `$CI_JOB_TOKEN`.
 
 ## Publishing skills

package/npm-shrinkwrap.json

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

package/package.json

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