@owlmeans/agent-skills 0.1.18-rc.21 → 0.1.18-rc.23

package/README.md

@@ -8,7 +8,7 @@ and places them into your project's skill store.
 After installing `@owlmeans/*` packages, run once:
 
 ```sh
-npx @owlmeans/agent-skills@^0.1.18-rc.21
+npx @owlmeans/agent-skills@^0.1.18-rc.22
 ```
 
 The installer scans `node_modules/@owlmeans/*/agent-meta/`, shows you what guidance
@@ -87,7 +87,7 @@ This package ships embedded agent skills under `agent-meta/`. After installing y
 your project's skill store (`.agents/skills/`):
 
 ```sh
-npx @owlmeans/agent-skills@^0.1.18-rc.21
+npx @owlmeans/agent-skills@^0.1.18-rc.23
 ```
 
 The embedded files are version-matched to this package release. Do not edit them

package/agent-meta/manifest.json

@@ -1,8 +1,8 @@
 {
   "schemaVersion": 2,
   "package": "@owlmeans/agent-skills",
-  "version": "0.1.18-rc.21",
-  "generatedAt": "2026-09-15T12:21:31.888Z",
+  "version": "0.1.18-rc.23",
+  "generatedAt": "2026-09-15T12:50:32.595Z",
   "canonicalRepo": "https://github.com/owlmeans/common",
   "entries": [
     {

package/agent-meta/skills/agent-skills/SKILL.md

@@ -8,7 +8,7 @@ user-invocable: false
 # @owlmeans/agent-skills
 
 **Layer:** Cross-cutting domain
-**Install:** `"@owlmeans/agent-skills": "^0.1.18-rc.21"` — in `devDependencies` for the CLI, in
+**Install:** `"@owlmeans/agent-skills": "^0.1.18-rc.23"` — in `devDependencies` for the CLI, in
 `dependencies` for the `./llm` plugins (plus the `@owlmeans/llm*`, `@owlmeans/agent` and
 `@langchain/core` **optional peers**)
 
@@ -184,7 +184,7 @@ tool never throws — a rejected tool call aborts the whole LangGraph superstep.
 
 ## Installer CLI
 
-`npx @owlmeans/agent-skills@^0.1.18-rc.21` walks the **whole** project tree, reads every nested
+`npx @owlmeans/agent-skills@^0.1.18-rc.22` walks the **whole** project tree, reads every nested
 `<dir>/node_modules/@owlmeans` scope it finds, and copies each `agent-meta/` skill into
 `.agents/skills/<name>/SKILL.md`. A workspace keeps its dependencies beside the workspace member
 that declares them, so the root scope is routinely empty and a root-only scan would find nothing.

package/agent-meta/skills/reuse-code/SKILL.md

@@ -47,7 +47,7 @@ How you research the repo depends on whether `@owlmeans/*` is linked locally:
   **https://github.com/owlmeans/common** — `tree.md` and package READMEs — to find the right package.
 
 This is the same dev-linked detection `@owlmeans/agent-skills` uses (see its `detectLinked`). After
-adding an `@owlmeans/*` dependency, run `npx @owlmeans/agent-skills@^0.1.18-rc.21` to deploy its
+adding an `@owlmeans/*` dependency, run `npx @owlmeans/agent-skills@^0.1.18-rc.22` to deploy its
 skill. Prefer an `@owlmeans/*` package over a third-party library or bespoke code whenever one fits.
 
 ### Never add an OwlMeans dependency without an explicit range
@@ -57,7 +57,7 @@ other `@owlmeans/*` packages:
 
 ```json
 "dependencies": {
-  "@owlmeans/queue": "^0.1.18-rc.18"
+  "@owlmeans/queue": "^0.1.18-rc.20"
 }
 ```
 

package/agent-meta/skills/scaffolding/SKILL.md

@@ -20,14 +20,14 @@ the framework shape is [[getting-started]].
 npm create @owlmeans/app@latest my-app
 bun create @owlmeans/app my-app
 yarn create @owlmeans/app my-app
-npx @owlmeans/create-app@^0.1.18-rc.27 my-app
+npx @owlmeans/create-app@^0.1.18-rc.28 my-app
 ```
 
 By default it copies the template, runs `git init`, installs dependencies, and **deploys agent
 guidance** into the project (`.agents/skills/`). `@owlmeans/agent-skills` is a dependency of the
 scaffolder and runs in-process, so the deploy happens whatever `--pm` is. With `--no-install` it
 still runs — the installer's own bundled extras give the project its general/harness guidance;
-only the package-specific skills wait for `npx @owlmeans/agent-skills@^0.1.18-rc.21` after the
+only the package-specific skills wait for `npx @owlmeans/agent-skills@^0.1.18-rc.22` after the
 install.
 
 Flags: `--name <name>`, `--slug <slug>`, `--lang <code>` (default `en`), `--description <text>`,
@@ -91,7 +91,7 @@ Follow **Option B** in the
 [OwlMeans getting-started guide](https://github.com/owlmeans/common/blob/main/docs/getting-started.md): create the bun
 workspace, then `common` (shared `entrypoints.ts`/schemas/config), `api` (`@owlmeans/server-app` +
 `appendStaticResource` handlers + `main`), and `web` (`@owlmeans/web-panel` + shadcn `@`-provided
-primitives + layout/nav/screens). Finish with `npx @owlmeans/agent-skills@^0.1.18-rc.21` to add agent guidance.
+primitives + layout/nav/screens). Finish with `npx @owlmeans/agent-skills@^0.1.18-rc.22` to add agent guidance.
 
 ## What gets generated
 
@@ -169,6 +169,6 @@ project has it even before the installer runs: [[agent-memory]], [[memory-promot
 [[getting-started]]. Regenerate the seed with `sync-agent-meta --seed-only` in the library-manager;
 never hand-edit a seeded copy. The installer adds the remaining general skills
 ([[scaffolding]], [[router-plugins]], [[shadcn-web]], [[shadcn-versions]], [[consent]],
-[[login-methods]], [[login-plugins]], [[agent-skills]]) and every package-specific one. After adding any `@owlmeans/*` dependency, re-run `npx @owlmeans/agent-skills@^0.1.18-rc.21`
+[[login-methods]], [[login-plugins]], [[agent-skills]]) and every package-specific one. After adding any `@owlmeans/*` dependency, re-run `npx @owlmeans/agent-skills@^0.1.18-rc.22`
 — discovery scans **every** `node_modules/@owlmeans` in the workspace (root and nested under
 `sources/*`), so package-specific skills are picked up even though bun nests them.

package/build/args.js

@@ -4,7 +4,7 @@ Skills are written to .agents/skills/<name>/SKILL.md — the Agent Skills standa
 location read by Copilot, Codex and other agents. Projects with a .claude/
 directory also get the per-skill symlinks Claude Code needs.
 
-Usage: npx @owlmeans/agent-skills@^0.1.18-rc.21 [options]
+Usage: npx @owlmeans/agent-skills@^0.1.18-rc.22 [options]
 
 Options:
   --dir <path>        target project directory (default: cwd)

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@owlmeans/agent-skills",
-  "version": "0.1.18-rc.21",
+  "version": "0.1.18-rc.23",
   "license": "MIT",
   "type": "module",
   "scripts": {
@@ -34,16 +34,16 @@
   "devDependencies": {
     "@langchain/core": "^1.2.9",
     "@owlmeans/dep-config": "workspace:*",
-    "@owlmeans/llm": "^0.1.18-rc.22",
-    "@owlmeans/llm-common": "^0.1.18-rc.21",
+    "@owlmeans/llm": "^0.1.18-rc.24",
+    "@owlmeans/llm-common": "^0.1.18-rc.23",
     "@types/bun": "^1.4.0",
     "@types/node": "^26.1.0",
     "nodemon": "^3.1.14",
     "typescript": "^7.0.2"
   },
   "peerDependencies": {
-    "@owlmeans/llm": "^0.1.18-rc.22",
-    "@owlmeans/llm-common": "^0.1.18-rc.21"
+    "@owlmeans/llm": "^0.1.18-rc.24",
+    "@owlmeans/llm-common": "^0.1.18-rc.23"
   },
   "peerDependenciesMeta": {
     "@owlmeans/llm": {

package/src/args.ts

@@ -18,7 +18,7 @@ Skills are written to .agents/skills/<name>/SKILL.md — the Agent Skills standa
 location read by Copilot, Codex and other agents. Projects with a .claude/
 directory also get the per-skill symlinks Claude Code needs.
 
-Usage: npx @owlmeans/agent-skills@^0.1.18-rc.21 [options]
+Usage: npx @owlmeans/agent-skills@^0.1.18-rc.22 [options]
 
 Options:
   --dir <path>        target project directory (default: cwd)