skillshop 2.1.0 → 4.0.0

package/README.md

@@ -1,6 +1,6 @@
 # Skillshop
 
-Skillshop installs and manages agent skills. Its CLI includes a bundled skill registry, with the same named install, update, and agent configuration commands as the earlier `skillz` CLI. It also lets project owners export skills from their own npm packages. A skill is a directory containing `SKILL.md` and any supporting files.
+Skillshop installs and manages agent skills. For user-authored skills, a plain folder library is the source of truth. Download individual skills from GitHub, install them into project or global destinations, and sync later source edits across recorded copies. The bundled registry and npm package-library APIs remain available for compatibility. A skill is a directory containing `SKILL.md` and any supporting files.
 
 The command is `skillshop`; `sk` runs the same CLI. The previous `skillz` command is no longer an executable alias. Existing `.skillz-lock` and `~/.skillz` state remain readable.
 
@@ -13,28 +13,43 @@ npm install --global skillshop
 skillshop init
 ```
 
-`init` asks which agents you use and saves their destinations in `~/.skillshop/config.json`. Change the selection later with `skillshop config agents`. Codex and OpenCode use `.agents/skills` inside projects and `~/.agents/skills` for user-level installs. Copilot and Claude use their own skill directories. Shared destinations get one copy.
+`skillshop init` asks which agents you use and saves their destinations in `~/.skillshop/config.json`. It is optional for project skill installs: without saved agent selection, Skillshop uses the nearest existing `.agents`, `.github`, or `.codex` directory and falls back to project-root `.agents/skills`. Run `skillshop init` to choose system-wide defaults; change that selection later with `skillshop config agents`. Codex and OpenCode use `.agents/skills` inside projects and `~/.agents/skills` for user-level installs. Copilot and Claude use their own skill directories. Shared destinations get one copy.
 
-### Install a named skill
-
-List the skills bundled with Skillshop, then install one:
+### Use a personal folder library
 
 ```bash
-skillshop list
-skillshop one-shot
-# Equivalent: skillshop install one-shot
+skillshop library init                 # selects ~/skillshop-library
+skillshop library init ./my-skills     # selects or adopts an existing folder
+skillshop library list
+skillshop download @alice/review       # adds source only
+skillshop install @alice/review        # downloads if absent, then installs locally
+skillshop install @alice/review --global
+skillshop install review               # installs an existing selected source
+skillshop sync                         # updates all recorded project and global copies
 ```
 
-Run a project install inside a Git repository. Skillshop copies the skill into each configured project destination and records managed copies in `.skillshop-lock`. It also installs the `skillshop` guidance skill. The lockfile and managed skill directories go into the repository's local Git exclude file, leaving unrelated skill directories alone.
+`library init` can create a missing folder or select an existing library. It preserves existing skill directories and config; no `package.json`, npm metadata, or version field is required. Without an explicit directory it selects the visible `~/skillshop-library` folder. The library config is `skillshop-library.json`; the default source directory is `skills/`. A skill can contain any regular files and nested folders, including hidden references and executable scripts.
+
+`download @owner/skill` reads `https://github.com/owner/skillshop-library.git` and copies only `skills/skill` into the selected personal library. The `@` marks a remote owner/skill reference; it is not part of the GitHub owner or repository URL. Download does not install the skill. `install @owner/skill` downloads when that source is absent, then installs from the library. If the same repository source is already present, local edits are reused without an upstream fetch. `install name` installs a matching skill from the selected library. Once a library is selected, named installs and `skillshop list` use that library; they do not fall back to bundled skills or add bundled guidance. Add `--global` to install into configured user directories. Unprefixed `owner/skill` inputs are rejected; use `@owner/skill` for remote references.
+
+`download @owner/skill --force` explicitly replaces the personal source directory after validation. A same-name authored or different-source skill otherwise fails safely. `skillshop sync` copies the current full directory from each recorded personal source to its Skillshop-managed project and global copies. It includes file additions, edits, removals, hidden files, binary contents, and modes; stale extras inside those owned copies are removed. Sync never fetches GitHub and changing the selected library does not redirect existing copies.
 
-To install a named skill for your user account instead:
+`sync` is also the explicit migration step for older tracked bundled installs. `library init` does not migrate them. If a selected library already has a skill, that source wins and tracked bundle copies are synchronized from it. Otherwise, Skillshop imports a missing source only when every surviving tracked project and global copy agrees across full paths, bytes, and modes. Divergent copies and unreadable ownership state are reported. Unknown source kinds, unmanaged directories, and imported snapshots are left untouched; if they prevent a complete consensus decision, sync reports that conflict. Missing recorded destinations are pruned, never recreated. Keep durable edits in the personal source; sync intentionally replaces local edits inside an owned installed copy.
+
+### Install a bundled registry skill (compatibility mode)
+
+When no personal library is selected, the bundled registry remains available:
 
 ```bash
+skillshop list
+skillshop one-shot
+# Equivalent: skillshop install one-shot
 skillshop one-shot --global
-# Equivalent: sk install one-shot --global
 ```
 
-For Codex or OpenCode, this writes `~/.agents/skills/one-shot`. A global install replaces an existing skill directory with that name, including local edits and extra files. Global installs use `~/.skillshop/global-skills.json` for bookkeeping. Each CLI run reconciles recorded installations; it does not install the entire bundled registry.
+Run project installs inside a Git repository. Skillshop records copies in `.skillshop-lock` and adds only its managed paths to the repository's local Git exclude file. In this compatibility mode it also installs bundled `skillshop` guidance. A global bundled install writes `~/.skillshop/global-skills.json`; for Codex or OpenCode it targets `~/.agents/skills`.
+
+In bundled compatibility mode, most ordinary commands reconcile recorded bundled installations. When a personal library is selected, `list` and named installs join library, download, qualified install, sync, upgrade, and agent instruction commands in bypassing that legacy reconciliation. Upgrade refreshes changed-version bundled copies from the newly installed package in a fresh process. Same-version bundled copies keep local edits; a changed-version replacement overwrites edits in that managed copy. To keep durable local changes, initialize a personal library, use `skillshop sync` to adopt tracked bundled copies where their contents agree, edit the library source, then sync it to owned copies. Personal-library copies are excluded from bundled refresh.
 
 ### Update or remove skills
 
@@ -46,236 +61,138 @@ skillshop uninstall one-shot
 skillshop uninstall one-shot --global
 ```
 
-`update` replaces skills managed in the current project's lockfile. `update --push` updates registered projects. Neither command updates global copies; reinstall a global skill by name with `--global`. Project uninstall removes only a skill recorded in `.skillshop-lock`. Global uninstall removes the named skill from configured user directories.
+`update` refreshes skills managed in the current project's lockfile from their recorded source. `update --push` updates registered projects. Use `skillshop sync` to propagate personal-library changes to recorded local and global copies. Project uninstall removes only a skill recorded in `.skillshop-lock`. Global uninstall removes the named skill from configured user directories.
 
-An exact version such as `skillshop one-shot@2026.8.21` checks the currently bundled version. It does not fetch a historical release. Use `skillshop migrate` to discover older lockfiles and register their repositories.
-
-### Manage agent instructions
-
-```bash
-skillshop agents
-skillshop agents --global
-```
-
-The local command updates a managed block in the nearest existing `AGENTS.md`. The global command updates the supported user instruction files. Sibling `*.block.md` fragments are composed in filename order. Text outside Skillshop's managed blocks is preserved.
-
-### Use skills from another package
-
-A distributor can declare which exported skills a global npm install should place in your user skill directory:
+### Upgrade Skillshop
 
 ```bash
-npm install --global @example/skill-library
+skillshop upgrade
 ```
 
-Those declared skills are copied during the package's install script. This package installer targets `~/.agents/skills` by default, independently of the agents selected with `skillshop init`. Updating the package replaces the same named user skills. If scripts are disabled, run `skillshop install-user /path/to/installed-package` manually.
+The command upgrades the npm installation that supplied the invoked CLI. A project-local installation updates Skillshop in the owning npm project and preserves the dependency section where it is already declared. It refreshes only that project's recorded Skillshop-managed skill copies. A global installation updates its npm prefix, then refreshes recorded global copies and copies in registered projects; it does not update those projects' package manifests. Running from a source checkout keeps the historical global-install behavior and does not edit the checkout's package manifest.
 
-To copy one exported skill into a project instead:
+After npm succeeds, the newly installed CLI runs in a fresh process and refreshes only existing copies recorded in `.skillshop-lock` or `~/.skillshop/global-skills.json` whose bundled skill version changed. Same-version copies retain local edits. A changed-version replacement overwrites local edits in that managed copy. For durable local changes, initialize a personal library, explicitly sync to adopt tracked bundled copies when their surviving copies agree, then edit the library source and sync. Deleted paths are pruned from ownership records instead of recreated. Unmanaged directories and package-import snapshots are not adopted. An npm install failure stops before copy refresh; a later refresh failure reports that Skillshop was upgraded and gives a nonzero result with the partial-refresh summary.
 
-```bash
-npm install @example/skill-library skillshop
-npx skillshop import @example/skill-library:review
-```
+`skillshop init` is optional. It configures agent destinations and is not required to upgrade Skillshop. The upgrade command never initializes, renders, or rewrites project `AGENTS.md` files or instruction templates.
 
-The `library:skill` argument names an installed package and one skill it exports. The command copies the skill to `.agents/skills/review` in the current project. Use `--to` for another destination or `--global` to copy it to `~/.agents/skills/review`. This is a snapshot. Reimport with `--force` to replace an existing project copy. `skillshop resolve @example/skill-library:review` reports its source location without copying it.
-
-### Example: one user, two scopes
+An exact version such as `skillshop one-shot@2026.8.21` checks the currently bundled version. It does not fetch a historical release. Use `skillshop migrate` to discover older lockfiles and register their repositories.
 
-Suppose you use Codex and work in `~/work/sample-app`, which is already a Git repository. Select Codex when `skillshop init` prompts, then install one bundled skill for every project and another only for this app:
+### Manage agent instructions
 
 ```bash
-skillshop init
-skillshop one-shot --global
-cd ~/work/sample-app
-skillshop changelog
-```
-
-The global command writes `~/.agents/skills/one-shot/SKILL.md`. The project command writes `.agents/skills/changelog/SKILL.md` and `.agents/skills/skillshop/SKILL.md` inside `sample-app`, then records both managed skills in `.skillshop-lock`. It does not copy `one-shot` into the project. Running `skillshop update` in `sample-app` refreshes the locked project skills; run `skillshop one-shot --global` again to replace the global copy.
-
-Package imports are separate from this lockfile workflow. `import` copies a snapshot from another package; `skillshop update` does not refresh that snapshot. `export` names a skill for consumers of a package and does not install it anywhere.
-
-## For project owners: distribute skills
-
-### 1. Export the skills
-
-In an npm package, put each skill in a directory with a `SKILL.md`. For example:
-
-```text
-my-library/
-  package.json
-  .agents/skills/review/SKILL.md
-  .agents/skills/triage/SKILL.md
-```
-
-For example, `.agents/skills/review/SKILL.md` could contain:
-
-```markdown
----
-name: review
-description: Review a proposed code change
----
-
-# Review
-
-Read the diff, identify concrete defects, and cite the affected files.
+skillshop agents
+skillshop agents init
+skillshop agents --check
+skillshop agents --global
 ```
 
-Keep any references or scripts needed by the skill beside its `SKILL.md`; Skillshop copies the whole directory.
+There are two local modes. Plain `skillshop agents` keeps the bounded legacy behavior for an uninitialized project: it updates the nearest existing `AGENTS.md` within the selected boundary, or creates one at the boundary root if none exists. After project sources are initialized, plain `skillshop agents` renders them instead. The global command remains separate and updates the supported user instruction files.
 
-Add Skillshop, initialize the export list, and name the skill you want to publish:
-
-```bash
-npm install skillshop
-npx skillshop library init
-npx skillshop export skill:review ./.agents/skills/review
-npx skillshop export skill:triage ./.agents/skills/triage
-```
+Initialize project-owned instructions with `skillshop agents init`. The neutral starter template is `.agents/instructions/AGENTS.template.md`; put source blocks beside it as `*.block.md`. Skillshop renders these sources into a distinct managed region in the project-root `AGENTS.md`. Existing user text and prior Skillshop managed guidance are preserved. Edit the template and source blocks, not the generated region. Repeated `skillshop agents init` leaves existing sources alone. If an initialized project's template is removed, `skillshop agents` reports an error rather than restoring bundled personal guidance. Symlinked source, template, block, or output path components are rejected, including dangling links.
 
-This writes `skillshop.library.json`:
+The default boundary is the nearest Git repository or worktree root. Outside Git, the current working directory is the boundary. Use `--project <directory>` to choose another boundary; a relative path is resolved from the command's current directory. This is required when a nested project inside a larger repository should own its own output. Put all three explicit-boundary scripts in `packages/app/package.json` so init, rendering, and checking stay in that package:
 
 ```json
 {
-  "schemaVersion": 1,
-  "exports": {
-    "skill:review": "./.agents/skills/review",
-    "skill:triage": "./.agents/skills/triage"
+  "scripts": {
+    "agents": "skillshop agents --project .",
+    "agents:init": "skillshop agents init --project .",
+    "agents:check": "skillshop agents --check --project ."
   }
 }
 ```
 
-The `exports` map is an explicit allowlist. Skillshop does not scan your repository for other skills. `skillshop export` also builds the library; run `skillshop build` after editing the JSON by hand. The build generates `skillshop.manifest.mjs`, adds the package's `./skillshop` export, and includes declared local skill directories in `package.json#files` when that field exists. Commit the resulting package files with your source.
-
-### 2. Declare user-level installation, if needed
+For a local project dependency, add Skillshop as a development dependency and opt into rendering through explicit scripts:
 
-To copy selected skills during a global npm install, add `skillshop.userInstall` and the generic lifecycle command to the distributor's `package.json`:
+```bash
+npm install --save-dev skillshop
+```
 
 ```json
 {
-  "name": "@example/skill-library",
-  "version": "1.0.0",
-  "dependencies": {
-    "skillshop": "^2.1.0"
-  },
-  "files": [],
   "scripts": {
-    "prepack": "skillshop build",
-    "postinstall": "skillshop install-user . --if-global"
-  },
-  "skillshop": {
-    "userInstall": ["skill:review"]
+    "agents": "skillshop agents",
+    "agents:init": "skillshop agents init",
+    "agents:check": "skillshop agents --check"
   }
 }
 ```
 
-Every `userInstall` entry must be unique and appear in `skillshop.library.json`. In this example, `skill:review` installs for the user on a global npm install. `skill:triage` remains available for explicit project imports. The runtime dependency makes the `skillshop` command available to npm's `postinstall` script. `--if-global` skips the user copy on a project-local install. npm's `--ignore-scripts` skips `postinstall` entirely.
+Run `npm run agents:init` once, edit the project sources, then run `npm run agents`. `npm run agents:check` exits successfully when the generated region in the working tree matches the current sources; it does not inspect Git's index or commit. CI can run `npm ci` followed by `npm run agents:check`. Commit the npm manifest and lockfile, `.agents/instructions/AGENTS.template.md`, its source blocks, and the rendered root `AGENTS.md`. There is no install hook: initialization and rendering happen only when the scripts are run.
 
-An install replaces each declared destination directory. If a later release removes a name from `userInstall`, Skillshop does not delete a copy previously installed in a user's directory.
+Project and bundled source templates support explicit includes:
 
-### 3. Check and pack the package
+```markdown
+{{ include "020_testing.block.md" }}
 
-```bash
-npx skillshop library list
-npx skillshop validate
-npx skillshop build
-npm pack --dry-run
+{{ blocks }}
 ```
 
-Check that the npm package contains `skillshop.manifest.mjs`, every exported `SKILL.md`, and any assets those skills need. The export list controls what Skillshop can resolve; it does not prevent your own broad `files` patterns from publishing other files. A real `npm pack` and global install from its tarball are useful checks before a release.
+Use `{{ include "020_testing.block.md" }}` or `{{ include '020_testing.block.md' }}` for named blocks. The older `{{ fragments["020_testing.block.md"] }}` and single-quoted lookup forms remain supported. `{{ blocks }}` inserts the remaining fragments in filename order, excluding every explicitly included file even when its include appears later in the template. Repeated includes render at each position. Fragment contents are inserted literally; placeholder-looking text inside a block is not evaluated recursively. Invalid expressions and missing fragments fail before generated output is written.
 
-After checking the tarball, publish the package with `npm publish`. Use `npm publish --access public` for a public scoped package.
+These expressions apply to source templates only. Skillshop does not interpret them in destination instruction files or sibling fragments.
 
-### Example: what happens after publication
+### Use skills from another package
 
-With the two-skill package above published as `@example/skill-library`, a global install copies only the declared `skill:review` to the user's skill directory:
+A distributor can declare which exported skills a global npm install should place in your user skill directory:
 
 ```bash
 npm install --global @example/skill-library
-# ~/.agents/skills/review/SKILL.md now comes from the package
 ```
 
-An application that needs `skill:triage` can install the package locally and copy that exported skill into its own repository:
+Those declared skills are copied during the package's install script. This package installer targets `~/.agents/skills` by default, independently of the agents selected with `skillshop init`. Updating the package replaces the same named user skills. If scripts are disabled, run `skillshop install-user /path/to/installed-package` manually.
+
+To copy one exported skill into a project instead:
 
 ```bash
-cd ~/work/sample-app
 npm install @example/skill-library skillshop
-npx skillshop import @example/skill-library:triage
+npx skillshop import @example/skill-library:review
 ```
 
-After the distributor publishes an update, reinstalling the package globally replaces the user's `review` directory. The application's `triage` snapshot stays as it was until the application updates the package and imports again with `--force`. The two installation paths are independent.
+The `library:skill` argument names an installed package and one skill it exports. The command copies the skill to `.agents/skills/review` in the current project. Use `--to` for another destination or `--global` to copy it to `~/.agents/skills/review`. This is a snapshot. Reimport with `--force` to replace an existing project copy. `skillshop resolve @example/skill-library:review` reports its source location without copying it.
 
-### Re-export a skill from another library
+### Example: one user, two scopes
 
-A package can expose a selected upstream skill under its own name:
+Suppose you use Codex and work in `~/work/sample-app`, which is already a Git repository. Select Codex when `skillshop init` prompts, then install one bundled skill for every project and another only for this app:
 
 ```bash
-npm install @example/upstream
-npx skillshop export skill:review --from @example/upstream --skill skill:review
+skillshop init
+skillshop one-shot --global
+cd ~/work/sample-app
+skillshop changelog
 ```
 
-The resulting export in `skillshop.library.json` is:
+The global command writes `~/.agents/skills/one-shot/SKILL.md`. The project command writes `.agents/skills/changelog/SKILL.md` and `.agents/skills/skillshop/SKILL.md` inside `sample-app`, then records both managed skills in `.skillshop-lock`. It does not copy `one-shot` into the project. Running `skillshop update` in `sample-app` refreshes the locked project skills; run `skillshop one-shot --global` again to replace the global copy.
 
-```json
-{
-  "skill:review": {
-    "from": "@example/upstream",
-    "skill": "skill:review"
-  }
-}
-```
+Package imports are separate from this lockfile workflow. `import` copies a snapshot from another package; `skillshop update` does not refresh that snapshot. `export` names a skill for consumers of a package and does not install it anywhere.
+
+## For project owners: distribute skills
 
-That object is one entry inside the manifest's `exports` map. The upstream package must be a runtime dependency or a non-optional peer dependency. Re-exporting is explicit; depending on another library does not expose all of its skills.
+### Personal skills: share a folder through GitHub
 
-## CLI and JavaScript API
+The recommended authoring format is a normal folder. Fork the bundled template at [`templates/skillshop-library`](templates/skillshop-library) or create the same layout in a GitHub repository named `skillshop-library`:
 
 ```text
-skillshop init
-skillshop config agents
-skillshop list
-skillshop <name> [--global]
-skillshop install <name> [--global]
-skillshop update [name]
-skillshop update --push
-skillshop uninstall <name> [--global]
-skillshop agents [--global]
-skillshop migrate [root ...]
-skillshop library init
-skillshop library list
-skillshop export skill:<name> <directory>
-skillshop export skill:<name> --from <package> [--skill skill:<source-name>]
-skillshop unexport skill:<name>
-skillshop validate
-skillshop build
-skillshop resolve <library>:<skill>
-skillshop import <library>:<skill> [--global] [--to <directory>] [--force]
-skillshop install-user [package-dir] [--if-global] [--to <skills-dir>]
+skillshop-library/
+  skillshop-library.json
+  skills/
+    review/
+      SKILL.md
+      references/
+      scripts/
 ```
 
-`init` and `list` keep their bundled-registry meanings. `library init`, `library list`, `validate`, and `build` operate on the package library in the current directory. In a `library:skill` reference, `library` can be an installed package name or a local package directory. `import` defaults to `.agents/skills/<skill>`; `--global` replaces `~/.agents/skills/<skill>`. `unexport` changes the package's public skill list; it does not delete the source directory. Remove a skill from `userInstall` before unexporting it.
+The config declares the relative source directory. Each skill needs a standard `SKILL.md` with `name` and `description`; author/version metadata is optional. Put references, scripts, and other assets beside it. Skillshop downloads the complete directory and preserves executable modes.
 
-Applications can use the same operations without invoking the CLI:
-
-```js
-import { exportSkill, reexportSkill, buildSkillLibrary } from 'skillshop/export';
-import { resolveSkill, importSkill } from 'skillshop/import';
-import { installDeclaredUserSkills } from 'skillshop/user-install';
+```bash
+skillshop download @alice/review
+skillshop install @alice/review
+skillshop install @alice/review --global
+skillshop sync
 ```
 
-For example, an application can read an exported skill directly from an installed package, or copy it into a workspace it manages:
-
-```js
-import { readFile } from 'node:fs/promises';
-import { resolveSkill, importSkill } from 'skillshop/import';
-
-const reference = '@example/skill-library:triage';
-const { manifestPath } = await resolveSkill({ reference });
-const instructions = await readFile(manifestPath, 'utf8');
-// Pass instructions to your agent runtime.
-
-await importSkill({
-  reference,
-  overwrite: true,
-});
-```
+`download @owner/skill` adds a source to the personal folder library without installing it. `install @owner/skill` downloads if needed and installs from that source; subsequent local edits are reused. `install name` uses a bare name for an existing library source. `sync` updates recorded local and global copies from the saved source roots. It never fetches upstream. See [the forkable library template](templates/skillshop-library/README.md) for its full layout and command details.
 
-`resolveSkill` leaves the skill inside the installed package. `importSkill` copies its complete directory, including files alongside `SKILL.md`. Set `overwrite: true` only when the application intends to replace an existing destination.
+### Existing package API compatibility
 
-`importSkill({ overwrite: true })` replaces a destination. Its optional `merge: true` mode overlays packaged files and preserves unrelated destination files. User-level installation always uses replacement, even when called through `installDeclaredUserSkills`.
+The published npm export/import APIs remain supported for existing consumers. Their authoring, lifecycle, and JavaScript API guide is in [Package library compatibility](docs/package-library-compatibility.md). New user-authored libraries can use the folder and GitHub workflow above without npm packaging.

package/docs/package-library-compatibility.md

@@ -0,0 +1,194 @@
+# Package library compatibility
+
+This guide documents the existing npm package export/import APIs. It is retained for consumers of those published APIs. It is not required for personal folder libraries or GitHub skill sharing.
+
+### Package API compatibility: export skills from npm packages
+
+The npm export/import API remains supported for existing package-based libraries. It is not required for personal skill authoring.
+
+#### 1. Export the skills
+
+In an npm package, put each skill in a directory with a `SKILL.md`. For example:
+
+```text
+my-library/
+  package.json
+  .agents/skills/review/SKILL.md
+  .agents/skills/triage/SKILL.md
+```
+
+For example, `.agents/skills/review/SKILL.md` could contain:
+
+```markdown
+---
+name: review
+description: Review a proposed code change
+---
+
+# Review
+
+Read the diff, identify concrete defects, and cite the affected files.
+```
+
+Keep any references or scripts needed by the skill beside its `SKILL.md`; Skillshop copies the whole directory.
+
+Add Skillshop, initialize the export list, and name the skill you want to publish:
+
+```bash
+npm install skillshop
+npx skillshop library init
+npx skillshop export skill:review ./.agents/skills/review
+npx skillshop export skill:triage ./.agents/skills/triage
+```
+
+This writes `skillshop.library.json`:
+
+```json
+{
+  "schemaVersion": 1,
+  "exports": {
+    "skill:review": "./.agents/skills/review",
+    "skill:triage": "./.agents/skills/triage"
+  }
+}
+```
+
+The `exports` map is an explicit allowlist. Skillshop does not scan your repository for other skills. `skillshop export` also builds the library; run `skillshop build` after editing the JSON by hand. The build generates `skillshop.manifest.mjs`, adds the package's `./skillshop` export, and includes declared local skill directories in `package.json#files` when that field exists. Commit the resulting package files with your source.
+
+### 2. Declare user-level installation, if needed
+
+To copy selected skills during a global npm install, add `skillshop.userInstall` and the generic lifecycle command to the distributor's `package.json`:
+
+```json
+{
+  "name": "@example/skill-library",
+  "version": "1.0.0",
+  "dependencies": {
+    "skillshop": "^2.1.0"
+  },
+  "files": [],
+  "scripts": {
+    "prepack": "skillshop build",
+    "postinstall": "skillshop install-user . --if-global"
+  },
+  "skillshop": {
+    "userInstall": ["skill:review"]
+  }
+}
+```
+
+Every `userInstall` entry must be unique and appear in `skillshop.library.json`. In this example, `skill:review` installs for the user on a global npm install. `skill:triage` remains available for explicit project imports. The runtime dependency makes the `skillshop` command available to npm's `postinstall` script. `--if-global` skips the user copy on a project-local install. npm's `--ignore-scripts` skips `postinstall` entirely.
+
+An install replaces each declared destination directory. If a later release removes a name from `userInstall`, Skillshop does not delete a copy previously installed in a user's directory.
+
+### 3. Check and pack the package
+
+```bash
+npx skillshop library list
+npx skillshop validate
+npx skillshop build
+npm pack --dry-run
+```
+
+Check that the npm package contains `skillshop.manifest.mjs`, every exported `SKILL.md`, and any assets those skills need. The export list controls what Skillshop can resolve; it does not prevent your own broad `files` patterns from publishing other files. A real `npm pack` and global install from its tarball are useful checks before a release.
+
+After checking the tarball, publish the package with `npm publish`. Use `npm publish --access public` for a public scoped package.
+
+### Example: what happens after publication
+
+With the two-skill package above published as `@example/skill-library`, a global install copies only the declared `skill:review` to the user's skill directory:
+
+```bash
+npm install --global @example/skill-library
+# ~/.agents/skills/review/SKILL.md now comes from the package
+```
+
+An application that needs `skill:triage` can install the package locally and copy that exported skill into its own repository:
+
+```bash
+cd ~/work/sample-app
+npm install @example/skill-library skillshop
+npx skillshop import @example/skill-library:triage
+```
+
+After the distributor publishes an update, reinstalling the package globally replaces the user's `review` directory. The application's `triage` snapshot stays as it was until the application updates the package and imports again with `--force`. The two installation paths are independent.
+
+### Re-export a skill from another library
+
+A package can expose a selected upstream skill under its own name:
+
+```bash
+npm install @example/upstream
+npx skillshop export skill:review --from @example/upstream --skill skill:review
+```
+
+The resulting export in `skillshop.library.json` is:
+
+```json
+{
+  "skill:review": {
+    "from": "@example/upstream",
+    "skill": "skill:review"
+  }
+}
+```
+
+That object is one entry inside the manifest's `exports` map. The upstream package must be a runtime dependency or a non-optional peer dependency. Re-exporting is explicit; depending on another library does not expose all of its skills.
+
+## CLI and JavaScript API
+
+```text
+skillshop init
+skillshop config agents
+skillshop list
+skillshop <name> [--global]
+skillshop install <name> [--global]
+skillshop update [name]
+skillshop update --push
+skillshop uninstall <name> [--global]
+skillshop agents init [--project <directory>]
+skillshop agents [--project <directory>] [--check]
+skillshop agents --global
+skillshop migrate [root ...]
+skillshop library init
+skillshop library list
+skillshop export skill:<name> <directory>
+skillshop export skill:<name> --from <package> [--skill skill:<source-name>]
+skillshop unexport skill:<name>
+skillshop validate
+skillshop build
+skillshop resolve <library>:<skill>
+skillshop import <library>:<skill> [--global] [--to <directory>] [--force]
+skillshop install-user [package-dir] [--if-global] [--to <skills-dir>]
+```
+
+`init` and `list` keep their bundled-registry meanings. `library init`, `library list`, `validate`, and `build` operate on the package library in the current directory. In a `library:skill` reference, `library` can be an installed package name or a local package directory. `import` defaults to `.agents/skills/<skill>`; `--global` replaces `~/.agents/skills/<skill>`. `unexport` changes the package's public skill list; it does not delete the source directory. Remove a skill from `userInstall` before unexporting it.
+
+Applications can use the same operations without invoking the CLI:
+
+```js
+import { exportSkill, reexportSkill, buildSkillLibrary } from 'skillshop/export';
+import { resolveSkill, importSkill } from 'skillshop/import';
+import { installDeclaredUserSkills } from 'skillshop/user-install';
+```
+
+For example, an application can read an exported skill directly from an installed package, or copy it into a workspace it manages:
+
+```js
+import { readFile } from 'node:fs/promises';
+import { resolveSkill, importSkill } from 'skillshop/import';
+
+const reference = '@example/skill-library:triage';
+const { manifestPath } = await resolveSkill({ reference });
+const instructions = await readFile(manifestPath, 'utf8');
+// Pass instructions to your agent runtime.
+
+await importSkill({
+  reference,
+  overwrite: true,
+});
+```
+
+`resolveSkill` leaves the skill inside the installed package. `importSkill` copies its complete directory, including files alongside `SKILL.md`. Set `overwrite: true` only when the application intends to replace an existing destination.
+
+`importSkill({ overwrite: true })` replaces a destination. Its optional `merge: true` mode overlays packaged files and preserves unrelated destination files. User-level installation always uses replacement, even when called through `installDeclaredUserSkills`.

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "skillshop",
-  "version": "2.1.0",
-  "description": "Build, export, resolve, and install portable agent skill libraries",
+  "version": "4.0.0",
+  "description": "Install and sync agent skills from personal folder libraries",
   "type": "module",
   "bin": {
     "skillshop": "./src/cli.js",
@@ -18,6 +18,8 @@
   "files": [
     "agents-content/",
     "skills-content/",
+    "templates/",
+    "docs/",
     "src/",
     "README.md"
   ],