@skaile/workspaces 5.2.0 → 5.4.0

package/dist/factory-assets/skills/authoring-skaile-assets/SKILL.md

@@ -2,7 +2,7 @@
 name: authoring-skaile-assets
 description: "Use when authoring or restructuring an AI-asset repository (skills, agents, prompts, contracts, MCP servers, connectors, flows, bundles) so it resolves cleanly through @skaile/workspaces and any store. Covers file layout, the 11 asset kinds, frontmatter conventions, the requires-vs-dependencies split, and how to test a source locally before publishing."
 metadata:
-  version: '0.1.0'
+  version: '0.1.1'
   stage: alpha
   tags:
     - skaile
@@ -21,14 +21,14 @@ metadata:
 You are helping an author build or fix an **AI-asset repository** (a "source") so
 that `@skaile/workspaces` — and any store mirroring it — can discover, resolve,
 and deploy its assets. This skill owns the *content* side (files on disk). Its
-companion **[authoring-skaile-manifests]** owns the `skaile.yaml` manifest and
+companion **[authoring-skaile-manifests]** owns the `skaile.manifest.yaml` manifest and
 the dependency grammar; read it before publishing.
 
 ## Mental model
 
 A **source** is a git repo of asset bytes. Identity is the global tuple
 `(publisher, kind, name, version)` and is **asset-intrinsic** — declared in the
-source's own `skaile.yaml`, never chosen by the consuming project. A consumer
+source's own `skaile.manifest.yaml`, never chosen by the consuming project. A consumer
 reaches the bytes by cloning the source repo (`sources[]`) or by querying a
 catalog (`stores[]`); both paths are content-hash verified and interchangeable.
 
@@ -58,11 +58,11 @@ catalog (`stores[]`); both paths are content-hash verified and interchangeable.
 
 ## File layout — two options
 
-**A. Explicit (recommended for curated repos).** Put `skaile.yaml` at the repo
-root with an `assets:` list and lay files out however you like; `root:`/`files:`
-point at each asset. See [authoring-skaile-manifests].
+**A. Explicit (recommended for curated repos).** Put `skaile.manifest.yaml` at
+the repo root with an `assets:` list and lay files out however you like;
+`root:`/`files:` point at each asset. See [authoring-skaile-manifests].
 
-**B. Convention (zero-config).** Omit `skaile.yaml`; the walker falls back to the
+**B. Convention (zero-config).** Omit `skaile.manifest.yaml`; the walker falls back to the
 agentskills.io layout:
 
 ```
@@ -72,7 +72,7 @@ agentskills.io layout:
   mcp-servers/excel/MCP.md
 ```
 
-> ⚠️ If `skaile.yaml` has a **non-empty `assets:` list, it is exhaustive** — only
+> ⚠️ If `skaile.manifest.yaml` has a **non-empty `assets:` list, it is exhaustive** — only
 > listed assets are resolvable. Files on disk that you forgot to list still show
 > up in `skaile manage` (the browse scan walks the filesystem) but **fail at
 > install** with `Asset not found`. Keep the list complete, or omit it and rely
@@ -86,10 +86,10 @@ extensions nested under `metadata:` (both locations are read for `version` and
 
 ```markdown
 ---
-name: audit                       # MUST equal the assets[].name in skaile.yaml
+name: audit                       # MUST equal the assets[].name in skaile.manifest.yaml
 description: "Use when ..."        # one line; this is what the model matches on
 metadata:
-  version: '1.4.0'                 # source skaile.yaml is authoritative; this is a hint only
+  version: '1.4.0'                 # source skaile.manifest.yaml is authoritative; this is a hint only
   stage: stable
   tags: [review, quality, ci]
   requires:                        # peer assets this one needs — kind:name form
@@ -102,9 +102,9 @@ metadata:
 ```
 
 Rules that bite:
-- **`name:` MUST equal the `assets[].name`** in `skaile.yaml`. Mismatch is an
+- **`name:` MUST equal the `assets[].name`** in `skaile.manifest.yaml`. Mismatch is an
   index-time hard error.
-- `metadata.version` is **ignored for resolution** — the source `skaile.yaml`
+- `metadata.version` is **ignored for resolution** — the source `skaile.manifest.yaml`
   version (or git-tag waterfall) is authoritative. Keep it as documentation only.
 - `description:` is the model-facing trigger. Write it as "Use when …"; it
   decides whether the skill gets surfaced.
@@ -141,8 +141,10 @@ dependencies:
 1. Pick the kind + name; create the manifest file (`SKILL.md`, `agent.yaml`, …).
 2. Write a sharp `description:` ("Use when …").
 3. Declare same-source peers in `requires:` (`kind:name`).
-4. If publishing as a curated source: add the asset to `skaile.yaml` `assets:`
-   and confirm `name:` matches. Run [authoring-skaile-manifests] to author/verify.
+4. If publishing as a curated source: add the asset to `skaile.manifest.yaml`
+   `assets:` (`skaile library create` does this; after hand edits run
+   `skaile library index <library>`) and confirm `name:` matches. Run
+   [authoring-skaile-manifests] to author/verify.
 5. Test locally before pushing (below).
 6. Commit; tag a SemVer release (`vX.Y.Z`) so the version waterfall resolves.
 
@@ -169,7 +171,7 @@ above.
 |---|---|---|
 | `Asset not found` on an asset visible in `manage` | omitted from `assets:` | add it, or drop `assets:` and use convention |
 | `name mismatch` at index time | `SKILL.md` `name:` ≠ `assets[].name` | make them equal |
-| `publisher must be declared` | non-GitHub source URL, no `publisher:` | set `publisher:` in `skaile.yaml` |
+| `publisher must be declared` | non-GitHub source URL, no `publisher:` | set `publisher:` in `skaile.manifest.yaml` |
 | `publisher required in asset ref` | a dep uses legacy `kind:name@pub` | migrate to `kind:@pub/name` (see [authoring-skaile-manifests]) |
 | dep silently absent at runtime | `requires:` used a full canonical ref | `requires:` is `kind:name` only; full refs go in bundle/project `dependencies:` |
 

package/dist/factory-assets/skills/authoring-skaile-manifests/SKILL.md

@@ -1,8 +1,8 @@
 ---
 name: authoring-skaile-manifests
-description: "Use when creating or fixing a skaile.yaml manifest for a new or existing skill / asset / MCP-server repo so it works with @skaile/workspaces and stores. Covers the publication half (publisher, version, assets[]), the consumption half (sources, stores, dependencies, overrides), the canonical dependency-ref grammar (kind:@publisher/name#version), the version waterfall, conflict resolution, and the v3 lock file. Also use to generate a manifest from an existing tree or migrate a legacy manifest."
+description: "Use when creating or fixing the skaile.manifest.yaml (publication) or skaile.yaml (consumption) manifest for a new or existing skill / asset / MCP-server repo so it works with @skaile/workspaces and stores. Covers the publication half (publisher, version, assets[] in skaile.manifest.yaml), the consumption half (sources, stores, dependencies, overrides in skaile.yaml), the canonical dependency-ref grammar (kind:@publisher/name#version), the version waterfall, conflict resolution, and the v3 lock file. Also use to generate a manifest from an existing tree or migrate a legacy manifest."
 metadata:
-  version: '0.1.0'
+  version: '0.1.1'
   stage: alpha
   tags:
     - skaile
@@ -15,24 +15,25 @@ metadata:
     - lockfile
 ---
 
-# Authoring `skaile.yaml` manifests
+# Authoring `skaile.manifest.yaml` and `skaile.yaml` manifests
 
-You are creating or repairing a `skaile.yaml` so a repo (skills, assets, or an
-MCP server) resolves through `@skaile/workspaces` and any store. This skill owns
-the manifest and the **latest dependency standard**. For file layout and asset
-content, see **[authoring-skaile-assets]**.
+You are creating or repairing the manifest(s) of a repo (skills, assets, or an
+MCP server) so it resolves through `@skaile/workspaces` and any store. This
+skill owns the manifests and the **latest dependency standard**. For file layout
+and asset content, see **[authoring-skaile-assets]**.
 
 Reference (canonical): the in-repo concept doc `docs/concepts/manifest-schema.md`
 and the spec `_devlog/specs/2026-05-31-manifest-canonical-identity.md`.
 The full dependency standard is in
 [`references/dependency-standard.md`](./references/dependency-standard.md).
 
-## One file, two halves
+## Two files, two halves
 
-`skaile.yaml` lives at the repo root. A repo can be **source-only** (publication
-half), **project-only** (consumption half), or both.
+Publication and consumption live in **separate files** at the repo root. A repo
+can be **source-only** (`skaile.manifest.yaml`), **project-only** (`skaile.yaml`),
+or both. `publisher:`, `version:` and `assets:` are rejected in `skaile.yaml`.
 
-### Publication half — "this repo IS a source"
+### Publication half — "this repo IS a source" (`skaile.manifest.yaml`)
 
 ```yaml
 publisher: skaile-ai            # optional; defaults to the source URL's GitHub org/user
@@ -73,7 +74,7 @@ assets:                         # optional; when present it EXHAUSTIVELY lists p
 > `Asset not found`. When you add an agent/flow/skill to the tree, add it here
 > too — or omit `assets:` entirely and let the convention walker find everything.
 
-### Consumption half — "this repo IS a project"
+### Consumption half — "this repo IS a project" (`skaile.yaml`)
 
 ```yaml
 sources:                        # absent → no direct git resolution
@@ -149,7 +150,7 @@ complete rules, SHA-synthetic versions, and worked examples.
 
 The version for an asset is the first of:
 
-1. `assets[].version` (per-asset in the source `skaile.yaml`).
+1. `assets[].version` (per-asset in the source `skaile.manifest.yaml`).
 2. The source's top-level `version:`.
 3. A SemVer-shaped git tag (`git describe --tags`), `v` stripped.
 4. Synthetic `0.0.0-sha.<7char>` from the resolved commit.
@@ -173,7 +174,7 @@ mean identical content everywhere, or every downstream consumer breaks.
 
 ## Generate a manifest from an existing repo
 
-For a new or existing skill/asset/MCP repo with no (or a stale) `skaile.yaml`:
+For a new or existing skill/asset/MCP repo with no (or a stale) `skaile.manifest.yaml`:
 
 1. **Enumerate assets on disk** — find every manifest file:
    ```bash
@@ -223,11 +224,13 @@ regenerate with `rm skaile.lock.yaml && skaile install`.
 
 ## Migration
 
-There is no `skaile manifest migrate` command. The transform
+There is no CLI command for manifest migration. The transform
 (`repositories:`/`ai_resources:` → `sources:`/`dependencies:`, bare deps →
 `@<publisher>`, `@skaile` → `@skaile-ai` rebrand, legacy `kind:name@pub` →
-`kind:@pub/name`) is done by the **`migrate-skaile-manifest`** skill. Run it from
-an AI session against each legacy `skaile.yaml`.
+`kind:@pub/name`, and the publication keys `publisher:`/`version:`/`assets:`
+moving from `skaile.yaml` to `skaile.manifest.yaml`) is done by the
+**`migrate-skaile-manifest`** skill. Run it from an AI session against each
+legacy `skaile.yaml`.
 
 ## Manifest checklist
 

package/dist/factory-assets/skills/skaile-author-asset/SKILL.md

@@ -1,8 +1,8 @@
 ---
 name: "skaile-author-asset"
-description: "Use when an asset author needs to build a skill in a local library and publish it. Covers the source/library/store model, laying out a repo (any depth, optional plugin grouping), the SKILL.md format, and the .skaile-source.yaml manifest (v1 glob vs v2 author-shipped inventory) and publish flow via the skaile CLI."
+description: "Use when an asset author needs to build a skill in a local library and publish it. Covers the source/library/store model, laying out a repo (any depth, optional plugin grouping), the SKILL.md format, and the skaile.manifest.yaml publication manifest and publish flow (library publish/register/yank) via the skaile CLI."
 metadata:
-  version: "0.1.1"
+  version: "0.1.2"
   tags:
     - "authoring"
     - "skill"
@@ -19,7 +19,7 @@ metadata:
 # Author an AI-Asset
 
 How to author a **skill** (or any asset kind) in a local library, lay out the
-repository, write the `.skaile-source.yaml` **manifest**, and
+repository, keep its `skaile.manifest.yaml` **manifest** current, and
 **publish** it through the store.
 
 For the canonical skill folder layout and frontmatter spec, read the companion
@@ -78,7 +78,7 @@ names carry no meaning, so lay the repo out however suits you:
 
 ```
 my-assets/                       # repo root (a "source")
-├── .skaile-source.yaml          # manifest (see §4)
+├── skaile.manifest.yaml         # publication manifest (see §4)
 ├── .claude-plugin/
 │   └── plugin.json              # optional grouping (see below)
 ├── skills/
@@ -92,13 +92,13 @@ my-assets/                       # repo root (a "source")
 
 **Publisher** is never read from a path segment. Resolution order:
 
-1. A per-asset `publisher` in a v2 inventory (§4).
-2. `publisher_overrides` — a per-path entry in the manifest.
-3. `publisher_default` — a literal such as `'@acme'`.
-4. Otherwise the repo name.
+1. A per-asset `publisher` on the `assets[]` entry (§4).
+2. The manifest's top-level `publisher`.
+3. Otherwise your store identity or the library name (`library create` warns when it falls back).
 
-With `publisher_default: '@acme'`, every asset is published as `@acme/<name>`;
-use `publisher_overrides` for the exceptions.
+With `publisher: acme` at the top of `skaile.manifest.yaml`, every asset is
+published as `@acme/<name>`; set `publisher` on an entry for the exceptions.
+Change the default later with `skaile library set <library> publisher=<slug>`.
 
 **Grouping in `skaile manage`** is optional and comes from Claude plugin
 manifests, not from folders: list the asset directories in
@@ -126,7 +126,7 @@ metadata:
   tags: [research, brief]
   stage: alpha          # alpha | beta | stable | deprecated
   requires:             # cross-asset dependencies (optional)
-    - "@research/brief-format@^2"
+    - "skill:brief-format"
 ---
 
 # Brief
@@ -140,86 +140,98 @@ metadata:
 
 Keep the body tight — it ships as a prompt.
 
-## 4. The manifest — `.skaile-source.yaml`
+## 4. The manifest — `skaile.manifest.yaml`
 
-One file at the **repo root** declares how the repo maps to publisher
-namespaces. Two modes:
+One file at the **library/repo root** declares what the repo **publishes**:
+the default `publisher`, a default `version`, and the `assets[]` inventory.
+`skaile library init` / `library create` write and maintain it; the publish
+commands read it as the **allowlist** — only assets listed in `assets[]` are
+published.
 
-### v1 — glob mode (default)
+```yaml
+# skaile.manifest.yaml
+publisher: acme                  # GitHub-shaped, no "@"; inherited by every asset
+version: 1.0.0                   # repo-level default version
+dev_paths:                       # optional: dev-only prefixes, excluded unless --dev
+  - ai-assets-dev
+assets:
+  - kind: skill
+    name: brief
+    root: research/skills/brief  # a directory, walked recursively
+    description: Generates a project brief
+    keywords: [research, brief]
+    dependencies:                # canonical refs only: kind:@<publisher>/<name>[#version]
+      - skill:@acme/brief-format#^2
+  - kind: agent
+    name: analyst
+    files:                       # or an explicit file list (repo-relative)
+      - agents/analyst/agent.yaml
+    publisher: research          # per-asset publisher override
+    version: 2.0.0               # per-asset version override
+```
 
-Discovery walks the tree, matches kind globs, and resolves each asset's
-publisher from the manifest. Use this while a repo is evolving fast.
+Keep it in sync with the tree instead of hand-editing the inventory:
 
-```yaml
-version: 1
-publisher_default: '@acme'       # literal publisher; never derived from a folder name
-default_ref: main
-publisher_overrides:
-  - path: research-contracts/
-    publisher: '@research-contracts'
+```bash
+skaile library create skill my-skill --library personal   # scaffolds the asset AND adds its assets[] entry
+skaile library index personal                              # after hand edits: add new assets, drop deleted ones
+skaile validate <library-path>                             # schema + canonical names, run before publishing
 ```
 
-### v2 — author-shipped inventory (pinned)
+An asset on disk but missing from `assets[]` is **not published**; an entry
+whose `root:` directory is gone makes `library publish` fail until
+`library index` drops it. `sha256` per entry is optional — if you pin one, a
+mismatch is a hard error.
 
-Add an `assets:` block and bump to `version: 2`. Discovery then treats the
-block as authoritative: it **skips the glob walk**, uses your curated `files[]`
-filter, your per-entry publisher, your `requires[]` graph, and verifies your
-`sha256`. Use this for reproducible, signed, audit-friendly releases.
+> `.skaile-source.yaml` is the **legacy** source config of third-party repos
+> (`publisher_default`, `publisher_overrides`, `dev_paths`). It is not what a
+> library writes and no longer sets a publisher; `skaile.manifest.yaml`
+> replaces it.
 
-```yaml
-version: 2
-publisher_default: '@acme'
-default_ref: main
-assets:
-  - path: research/skills/brief    # relative to repo root
-    kind: skill
-    publisher: '@research'         # required per entry
-    name: brief
-    version: 1.0.0
-    sha256: "<64-hex>"             # optional locally, REQUIRED to publish
-    files:                         # explicit; no wildcards; ≥1
-      - SKILL.md
-      - validator.py
-      - references/template.md
-    requires:
-      - "@research/brief-format@^2"
-    metadata:
-      description: Generates a project brief
-      keywords: [research, brief]
-```
+### Curating a repo you don't own
 
-**Never hand-edit the `assets:` block.** Generate it from the asset files (this
-is what `source-manifest-builder` automates):
+For a third-party source added with `skaile source add`, the manifest is a
+**curator** manifest (it carries `source:` and `provenance:`) kept under
+`~/.skaile/store/manifests/`:
 
 ```bash
-skaile source build-manifest --path ./my-assets            # preview
-skaile source build-manifest --path ./my-assets --diff     # show drift (CI-friendly, non-zero on drift)
-skaile source build-manifest --path ./my-assets --write    # write the manifest
-skaile source verify-manifest --path ./my-assets --strict  # verify before commit/publish
+skaile source manifest init <src>              # create it from a discovery walk
+skaile source manifest rebuild <src>           # re-derive after upstream changes (keeps your curation; --overwrite discards it)
+skaile source manifest verify <src> --strict   # verify hashes + manifest parse before publishing
+skaile source manifest publish <src>           # register it in the store
 ```
 
-Hash = sort `files[]` lexicographically, then SHA256 over
-`<relpath>\0<content>\0` per file. Author-computed hashes are wire-compatible
-with server-computed ones. Missing files are a hard error in manifest mode.
-
 ## 5. Publish
 
+`<library>` below is the **library name** (as shown by `skaile library list`),
+never an asset ref.
+
 ```bash
 # Attach a GitHub remote so the library is store-publishable
 skaile library link personal https://github.com/you/my-assets
 
-# Push bytes to GitHub + register the manifest in the store, atomically
-skaile library publish @research/brief@1.0.0
+skaile store login
 
-# Or register a manifest for bytes already on GitHub (no push)
-skaile library register @research/brief@1.0.0
+# Preview the plan: remote, publisher namespace(s), ref, refs to publish
+skaile library publish personal --dry-run
 
-# Retract a catalog entry
-skaile library yank @research/brief@1.0.0
+# Commit + push to the PUBLIC remote, register it as a store source, publish its assets
+skaile library publish personal
+# → skill:@acme/brief#1.0.0
+
+# Or register bytes that are already on GitHub (no commit/push)
+skaile library register personal
+
+# Retract published assets (all, or one with --asset)
+skaile library yank personal --asset skill:@acme/brief#1.0.0
 ```
 
-Consumers then install pointer-only: `skaile install @research/brief@1.0.0`
-fetches from your repo at the pinned commit and verifies SHA256 per file.
+`--asset <ref>` limits `publish` / `register` / `yank` to one asset. A local
+library with no remote needs `--create-repo` (or `library link`) first.
+
+Consumers then install pointer-only with the canonical ref:
+`skaile install skill:@acme/brief#1.0.0` fetches from your repo at the pinned
+commit and verifies SHA256 per file.
 
 ## Dev-only assets — `dev_paths` + `--dev`
 
@@ -232,11 +244,10 @@ pulled in only when a contributor opts in.
 - **Folder name:** keep dev assets under one top-level folder named
   **`ai-assets-dev/`** (intention-revealing; treat the `-dev` suffix as
   reserved).
-- **Mechanism:** declare it in `.skaile-source.yaml` under `dev_paths`:
+- **Mechanism:** declare it in `skaile.manifest.yaml` under `dev_paths`:
 
   ```yaml
-  version: 1
-  publisher_default: '@acme'
+  publisher: acme
   dev_paths:               # excluded from a normal discovery run
     - ai-assets-dev
   ```

package/dist/factory-assets/skills/skaile-manage-workspace/SKILL.md

@@ -2,7 +2,7 @@
 name: "skaile-manage-workspace"
 description: "Use when managing a skaile workspace from the command line: init/install a project, add/remove/list/search assets, work with sources and libraries, the interactive manage TUI, patches, sessions, and catalog config. Wraps the `skaile` CLI workspace surface."
 metadata:
-  version: "0.1.1"
+  version: "0.1.2"
   tags:
     - "cli"
     - "workspace"
@@ -45,8 +45,8 @@ paths, resources) live in `skaile.yaml` and are hand-edited.
 
 ## Assets in a workspace
 
-`skaile <noun>` works across kinds (`skill`, `agent`, `prompt`, `flow`,
-`bundle`, `contract`); the unified verbs:
+The asset verbs work across kinds (`skill`, `agent`, `prompt`, `flow`,
+`bundle`, `contract`):
 
 ```bash
 skaile add <ref> [--global]      # add to skaile.yaml + deploy
@@ -57,7 +57,7 @@ skaile search [kind] [query]     # search across all sources
 skaile info <ref>                # metadata, deps, deploy status
 skaile why <ref>                 # why is this installed (dep chain)
 skaile tree                      # dependency tree
-skaile outdated [name]           # assets behind their source
+skaile outdated [ref]            # assets behind their source
 skaile update [name]             # refresh catalog cache + re-deploy outdated
 skaile diff <ref>                # deployed vs source diff
 skaile doctor [name]             # scan for broken deps
@@ -65,12 +65,14 @@ skaile create <name> [--kind k]  # scaffold a new asset
 skaile history [limit]           # recent actions
 ```
 
-`<ref>` is `@publisher/name` optionally pinned with `@version`.
+`<ref>` is the canonical `kind:@<publisher>/<name>`, optionally pinned with
+`#<version>` — e.g. `skill:@research/brief#1.0.0`. The `kind:` prefix is
+required and the version follows `#`, never `@`.
 
 ### Pointer-only install from the catalog
 
 ```bash
-skaile install @research/brief@1.0.0
+skaile install skill:@research/brief#1.0.0
 ```
 
 Resolves the install manifest from the configured catalog, fetches file bytes
@@ -92,15 +94,19 @@ grouped by publisher/source and Claude plugin, unlisted assets under `Other`), *
 ## Sources (third-party / team repos)
 
 ```bash
-skaile source add <git-url>      # clone + register a github source (~/.skaile/sources/<name>)
+skaile source add <git-url>      # clone + register a github source (~/.skaile/cache/sources/<host>/<owner>/<repo>/)
 skaile source list               # registered sources
 skaile source show <name>
 skaile source remove <name>
 skaile source sync [name]        # re-fetch upstream changes
-skaile source build-manifest --path <p> [--diff|--write]   # author-shipped inventory
-skaile source verify-manifest --path <p> --strict
+skaile source manifest init <src>      # curate a manifest over a source you don't own
+skaile source manifest verify <src> --strict   # verify hashes + manifest parse
 ```
 
+`source manifest *` curates a catalog entry over a source you **don't** own. For
+a library you author yourself, the manifest is its `skaile.manifest.yaml` (kept
+current by `skaile library index <library>`) — see `skaile-author-asset`.
+
 ## Libraries (your authoring places)
 
 ```bash
@@ -110,7 +116,7 @@ skaile library create <kind> <name>    # scaffold a new asset
 skaile library list|status|show <name>
 skaile library default <name>          # set default
 skaile library commit|pull|push|sync <name>   # git ops
-skaile library publish <ref>           # push + register manifest atomically
+skaile library publish <library>       # push + register in the store (<library> is a NAME, not a ref)
 ```
 
 See the `skaile-author-asset` skill for the full authoring + publish flow.
@@ -154,7 +160,7 @@ catalog settings per-workspace.
 ## Dev-only assets
 
 A source can mark assets meant only for developing the project itself (those
-under `ai-assets-dev/`) as dev-only via `dev_paths` in its `.skaile-source.yaml`.
+under `ai-assets-dev/`) as dev-only via `dev_paths` in its `skaile.manifest.yaml`.
 A normal sync excludes them; `--dev` on the sync re-includes them:
 
 ```bash

package/dist/factory-assets/skills/skailify/SKILL.md

@@ -2,7 +2,7 @@
 name: skailify
 description: "Use when a user wants to move an existing coding-agent skill (a Claude Code skill under ~/.claude/skills/, or any SKILL.md directory) into a skaile library so it can be versioned and published. Trigger phrases: 'skailify my skill', 'import this Claude skill into my library', 'move my ~/.claude skill into skaile', 'turn my CC skill into a skaile asset', 'add my local skill to the library'. Drives `skaile asset import` and verifies with `skaile validate`."
 metadata:
-  version: "0.1.0"
+  version: "0.1.1"
   source: AUTHORED
   stage: alpha
   tags:
@@ -52,7 +52,7 @@ wires the entry into `skaile.manifest.yaml`. The low-level `skaile asset migrate
 
 | Flag | Use |
 |---|---|
-| `--to <library>` | Target a non-default library. |
+| `--library <library>` | Target a non-default library. |
 | `--version <semver>` | Stamp when the skill ships none (default `0.1.0`). |
 | `--stage <stage>` | `alpha` (default) \| `beta` \| `stable`. |
 | `--no-normalize` | Copy frontmatter verbatim (rare — only if already skaile-shaped). |
@@ -61,8 +61,12 @@ wires the entry into `skaile.manifest.yaml`. The low-level `skaile asset migrate
 ## After import
 
 - Edit the stamped `metadata.tags` if `import` left them empty.
-- To publish: `skaile library publish <kind>:@<publisher>/<name>@<version>`
-  (needs a git-linked library — see [skaile-author-asset]).
+- To publish: link the library to a GitHub remote once
+  (`skaile library link <library> <git-url>`), sign in (`skaile store login`),
+  then `skaile library publish <library>` — `<library>` is the library **name**,
+  not an asset ref; add `--asset <ref>` for one asset and `--dry-run` to preview
+  (see [skaile-author-asset]). The imported skill publishes as
+  `skill:@<publisher>/<name>#<version>`.
 - Re-running `import` for the same `(kind, name)` updates its manifest entry in
   place rather than duplicating it.
 

package/dist/{flows-BOB5YA5R.js → flows-DTADYIXH.js}

@@ -1,26 +1,26 @@
-export { flowFindFlowForSession, flowGetSession, flowList, flowListSessions, flowShow } from './chunk-FJTC5YFO.js';
+export { flowFindFlowForSession, flowGetSession, flowList, flowListSessions, flowShow } from './chunk-XMQAV6T3.js';
 import './chunk-R6O6YWU7.js';
-import './chunk-7Y43UXKA.js';
+import './chunk-JELTQ4H7.js';
 import './chunk-X5YPJV4N.js';
-import './chunk-XOTJVCJB.js';
-import './chunk-BIMEKYOE.js';
+import './chunk-JKWU6ULI.js';
+import './chunk-QEXEHXX5.js';
 import './chunk-4GY63JU6.js';
-import './chunk-PU5VY7KF.js';
-import './chunk-U6K3I3AX.js';
+import './chunk-JCATNLY3.js';
+import './chunk-XGIS325V.js';
 import './chunk-5BEFNLOR.js';
 import './chunk-A2ULN3KX.js';
-import './chunk-P2EM6FNQ.js';
-import './chunk-TLKM4M47.js';
+import './chunk-6IGFSUTE.js';
+import './chunk-MFHKHXDE.js';
 import './chunk-TOSHZX4C.js';
-import './chunk-YRF5CYHR.js';
+import './chunk-SR4RFKHM.js';
 import './chunk-RVRB27AN.js';
-import './chunk-YANDJSMN.js';
-import './chunk-OABIGSUY.js';
+import './chunk-LFMX2UEF.js';
+import './chunk-WX74MVNA.js';
 import './chunk-ICSCSM5D.js';
 import './chunk-JMKB7IB4.js';
 import './chunk-MJHSLODD.js';
 import './chunk-C3CAXQMA.js';
 import './chunk-BOFL7GIF.js';
 import './chunk-NSBPE2FW.js';
-//# sourceMappingURL=flows-BOB5YA5R.js.map
-//# sourceMappingURL=flows-BOB5YA5R.js.map
+//# sourceMappingURL=flows-DTADYIXH.js.map
+//# sourceMappingURL=flows-DTADYIXH.js.map

package/dist/{flows-BOB5YA5R.js.map → flows-DTADYIXH.js.map}

@@ -1 +1 @@
-{"version":3,"sources":[],"names":[],"mappings":"","file":"flows-BOB5YA5R.js"}
+{"version":3,"sources":[],"names":[],"mappings":"","file":"flows-DTADYIXH.js"}

package/dist/{helpers-ZGK4R5MZ.js → helpers-F2RFRT5D.js}

@@ -1,25 +1,25 @@
-export { KIND_COL_WIDTH, S, TARGET_DEFAULT_HINT, bareSoftDepName, colorRef, fitWidth, formatRelativeTime, formatSoftDepAddPreview, formatSoftDepHint, formatSoftDepRemovePreview, formatSoftDepSection, kindColor, kindColorPad, logErr, logInfo, logOk, logWarn, warnLegacyClaudeCopies } from './chunk-77GKEZ2R.js';
-import './chunk-L257BENF.js';
-import './chunk-B4J4RGNY.js';
-import './chunk-LZ5RH6LD.js';
-import './chunk-4YE7OYTB.js';
+export { KIND_COL_WIDTH, S, TARGET_DEFAULT_HINT, bareSoftDepName, colorRef, fitWidth, formatRelativeTime, formatSoftDepAddPreview, formatSoftDepHint, formatSoftDepRemovePreview, formatSoftDepSection, kindColor, kindColorPad, logErr, logInfo, logOk, logWarn, warnLegacyClaudeCopies } from './chunk-JEA32KB6.js';
+import './chunk-BATL2CWI.js';
+import './chunk-Y5OCUOXF.js';
+import './chunk-Y7UBRRKG.js';
+import './chunk-VKSA2CDJ.js';
 import './chunk-R7FOF242.js';
 import './chunk-ZDKJHQY2.js';
-import './chunk-KGGT6MUM.js';
+import './chunk-37DN45RR.js';
 import './chunk-CGYEHQOX.js';
-import './chunk-BIMEKYOE.js';
+import './chunk-QEXEHXX5.js';
 import './chunk-4GY63JU6.js';
-import './chunk-PU5VY7KF.js';
-import './chunk-U6K3I3AX.js';
+import './chunk-JCATNLY3.js';
+import './chunk-XGIS325V.js';
 import './chunk-5BEFNLOR.js';
 import './chunk-A2ULN3KX.js';
-import './chunk-P2EM6FNQ.js';
-import './chunk-TLKM4M47.js';
+import './chunk-6IGFSUTE.js';
+import './chunk-MFHKHXDE.js';
 import './chunk-TOSHZX4C.js';
-import './chunk-YRF5CYHR.js';
+import './chunk-SR4RFKHM.js';
 import './chunk-RVRB27AN.js';
-import './chunk-YANDJSMN.js';
-import './chunk-OABIGSUY.js';
+import './chunk-LFMX2UEF.js';
+import './chunk-WX74MVNA.js';
 import './chunk-ICSCSM5D.js';
 import './chunk-JMKB7IB4.js';
 import './chunk-MJHSLODD.js';
@@ -30,5 +30,5 @@ import './chunk-UQ6LFBPZ.js';
 import './chunk-TNWXGHLD.js';
 import './chunk-5CYEWBPB.js';
 import './chunk-NSBPE2FW.js';
-//# sourceMappingURL=helpers-ZGK4R5MZ.js.map
-//# sourceMappingURL=helpers-ZGK4R5MZ.js.map
+//# sourceMappingURL=helpers-F2RFRT5D.js.map
+//# sourceMappingURL=helpers-F2RFRT5D.js.map

package/dist/{helpers-ZGK4R5MZ.js.map → helpers-F2RFRT5D.js.map}

@@ -1 +1 @@
-{"version":3,"sources":[],"names":[],"mappings":"","file":"helpers-ZGK4R5MZ.js"}
+{"version":3,"sources":[],"names":[],"mappings":"","file":"helpers-F2RFRT5D.js"}