@glexcorp/gskp 0.1.1 → 0.1.2

package/docs/QUICKSTART.md

@@ -5,7 +5,7 @@ Get from clone to a working skill in under 5 minutes.
 ## Prerequisites
 
 - **Node.js 18+** for the `gskp` npm CLI and package build
-- **bash** shell (macOS, Linux, or WSL on Windows) for clone-based `./init.sh`, `scripts/pack.sh`, and remaining shell-backed `gskp` commands
+- **bash** shell (macOS, Linux, or WSL on Windows) for `scripts/pack.sh` and remaining shell-backed `gskp` commands
 - **jq** for git-checkout `scripts/pack.sh` write commands and `gskp install-deck` materialization: `brew install jq` (macOS) or `apt install jq` (Debian/Ubuntu). Node-owned `gskp install`, `remove`, `refresh`, `doctor`, `prune`, `pin`, `unpin`, `status`, `list-packs`, `set-mode`, and `set-update-mode` do not require `jq`
 - **Claude Code** or **OpenAI Codex** installed on your machine
 - **pnpm** (optional, for running tests): `npm install -g pnpm`
@@ -14,28 +14,30 @@ Get from clone to a working skill in under 5 minutes.
 
 ### Source checkout
 
-Use the source checkout when you are developing this repository or want global core skills installed directly from a local clone:
+Use the source checkout when you are developing this repository or installing base skills from a local clone:
 
 ```bash
 git clone <this-repo-url> ~/agentic-skills
-cd ~/agentic-skills
-./init.sh
+cd ~/my-project
+npx skillpacks init
 ```
 
-`init.sh` installs repo-managed global core skill directories into `~/.claude/skills/` and `~/.codex/skills/`. Track-latest installs are managed copies with drift metadata; pinned archived skills are the symlink case. Domain packs are not installed globally — that is intentional context hygiene.
+`npx skillpacks init` installs repo-managed base skill directories **project-local** into the current repository's `.claude/skills/` and `.codex/skills/` roots and records `base_skills: true` in `.agents/project.json`. Track-latest installs are managed copies with drift metadata; pinned archived skills are the symlink case. Domain packs are not installed as base skills — that is intentional context hygiene.
 
 ### npm CLI
 
-With the published npm package, use `npx @glexcorp/gskp` from the project that should receive local skills:
+With the published npm package, use `npx skillpacks` from the project that should receive local skills:
 
 ```bash
 cd ~/my-project
-npx @glexcorp/gskp --version
-npx @glexcorp/gskp init
-npx @glexcorp/gskp list
+npx skillpacks --version
+npx skillpacks init
+npx skillpacks list
 ```
 
-The npm CLI does not install user-home global skills by default. `npx @glexcorp/gskp init` installs base skills into the current repository's local `.claude/skills/` and `.codex/skills/` roots and records `base_skills: true` in `.agents/project.json`. Later `npx @glexcorp/gskp refresh` updates those base skills from the package snapshot being run. If you explicitly want user-home global core skills from npm, run `npx @glexcorp/gskp init --global` (or the backward-compatible `npx @glexcorp/gskp init-global`). Domain packs are never installed globally.
+The npm CLI installs base skills **project-local only** — there is no user-home (global) install path. `npx skillpacks init` installs base skills into the current repository's local `.claude/skills/` and `.codex/skills/` roots and records `base_skills: true` in `.agents/project.json`. Later `npx skillpacks refresh` updates those base skills from the package snapshot being run. To clean up legacy user-home base installs from the retired init path, run `npx skillpacks uninstall-global`. Domain packs are never installed as base skills.
+
+The scoped alias package is published from the same release artifact and version. Users who prefer that package identity can run `npx @glexcorp/gskp init`, `npx @glexcorp/gskp install devtool`, and the same subcommands.
 
 ## 2. Install a Pack in Your Project
 
@@ -43,10 +45,10 @@ Navigate to any project repository and install the pack that matches your domain
 
 ```bash
 cd ~/my-project
-npx @glexcorp/gskp init
-npx @glexcorp/gskp install devtool    # for developer tools
-npx @glexcorp/gskp install game        # for games
-npx @glexcorp/gskp install business-discovery  # for SaaS/business apps
+npx skillpacks init
+npx skillpacks install devtool    # for developer tools
+npx skillpacks install game        # for games
+npx skillpacks install business-discovery  # for SaaS/business apps
 ```
 
 From a source checkout, the equivalent compatibility route is:
@@ -60,9 +62,9 @@ This creates `.agents/project.json` and project-local skill roots in `.claude/sk
 The npm CLI can also install a canonical deck from manifest metadata:
 
 ```bash
-npx @glexcorp/gskp install-deck business-afps
-npx @glexcorp/gskp install-deck devtool-afps
-npx @glexcorp/gskp install-deck game-afps
+npx skillpacks install-deck business-afps
+npx skillpacks install-deck devtool-afps
+npx skillpacks install-deck game-afps
 ```
 
 ## 3. Reload Skills in Your CLI
@@ -83,7 +85,7 @@ Source checkout:
 npm:
 
 ```bash
-npx @glexcorp/gskp status
+npx skillpacks status
 ```
 
 Or from within Claude Code: run `/pack` with no arguments. From Codex: run `$pack`.
@@ -121,9 +123,9 @@ After running a skill, look for these artifacts:
 Alignment maintenance from npm is available through:
 
 ```bash
-npx @glexcorp/gskp alignment bundles --check
-npx @glexcorp/gskp alignment pages audit
-npx @glexcorp/gskp alignment pages inject-tts --force alignment/example.html
+npx skillpacks alignment bundles --check
+npx skillpacks alignment pages audit
+npx skillpacks alignment pages inject-tts --force alignment/example.html
 ```
 
 From a source checkout, the direct script paths remain canonical: `node scripts/upgrade-alignment-page.mjs`, `node scripts/audit-alignment-pages.mjs`, and `node scripts/inject-tts.mjs`.
@@ -133,11 +135,11 @@ From a source checkout, the direct script paths remain canonical: `node scripts/
 Moving from a source checkout to npm does not change the project-local files. From the target project directory, run the npm command that matches your existing pack designation:
 
 ```bash
-npx @glexcorp/gskp refresh
-npx @glexcorp/gskp doctor
+npx skillpacks refresh
+npx skillpacks doctor
 ```
 
-`@glexcorp/gskp@<semver>` selects the package snapshot. Skill pins remain skill-level pins, for example `npx @glexcorp/gskp pin quality-sweep v0.0`. If a pinned archive version is not present in the installed npm package, upgrade the npm package or use a source checkout that contains that archive.
+`skillpacks@<semver>` selects the package snapshot. Skill pins remain skill-level pins, for example `npx skillpacks pin quality-sweep v0.0`. If a pinned archive version is not present in the installed npm package, upgrade the npm package or use a source checkout that contains that archive.
 
 ## What's Next
 

package/docs/decks.md

@@ -18,15 +18,15 @@ Rapid decks are for weekly experiments. Deliberate decks are for products that j
 Install decks through the npm CLI:
 
 ```bash
-npx @glexcorp/gskp install-deck vard
-npx @glexcorp/gskp install-deck ord
-npx @glexcorp/gskp install-deck business-afps
-npx @glexcorp/gskp install-deck business-afps --full
-npx @glexcorp/gskp install-deck devtool-afps
-npx @glexcorp/gskp install-deck game-afps
+npx skillpacks install-deck vard
+npx skillpacks install-deck ord
+npx skillpacks install-deck business-afps
+npx skillpacks install-deck business-afps --full
+npx skillpacks install-deck devtool-afps
+npx skillpacks install-deck game-afps
 ```
 
-In the current `@glexcorp/gskp@0.1.0` release, npm deck materialization still uses the packaged shell backend, so `install-deck` requires `bash` and `jq`. Direct npm pack installs such as `npx @glexcorp/gskp install devtool` are Node-owned and do not require `jq`.
+In the current `skillpacks@0.1.0` release, npm deck materialization still uses the packaged shell backend, so `install-deck` requires `bash` and `jq`. Direct npm pack installs such as `npx skillpacks install devtool` are Node-owned and do not require `jq`.
 
 ---
 
@@ -38,7 +38,7 @@ In the current `@glexcorp/gskp@0.1.0` release, npm deck materialization still us
 **Install:**
 
 ```bash
-npx @glexcorp/gskp install-deck vard
+npx skillpacks install-deck vard
 ```
 
 **Canonical chain:**
@@ -55,7 +55,7 @@ vard-scan -> vard-align -> vard-ship
 **Graduation:** When an experiment shows traction, graduate to Business AFPS:
 
 ```bash
-npx @glexcorp/gskp install business-discovery
+npx skillpacks install business-discovery
 ```
 
 Then start the deliberate pipeline with `/idea-scope-brief` or `/customer-discovery`.
@@ -70,7 +70,7 @@ Then start the deliberate pipeline with `/idea-scope-brief` or `/customer-discov
 **Install:**
 
 ```bash
-npx @glexcorp/gskp install-deck ord
+npx skillpacks install-deck ord
 ```
 
 **Canonical chain:**
@@ -87,7 +87,7 @@ ord-scan -> ord-align -> ord-ship
 **Graduation:** When a package gains traction (stars, downloads, issues), graduate to Devtool AFPS:
 
 ```bash
-npx @glexcorp/gskp install devtool
+npx skillpacks install devtool
 ```
 
 Then start the deliberate pipeline with `/devtool-adoption` or `/devtool-positioning`.
@@ -102,15 +102,15 @@ Then start the deliberate pipeline with `/devtool-adoption` or `/devtool-positio
 **Install:**
 
 ```bash
-npx @glexcorp/gskp install-deck business-afps
+npx skillpacks install-deck business-afps
 ```
 
 Add packs progressively as the product matures:
 
 ```bash
-npx @glexcorp/gskp install customer-lifecycle   # after ICP + competitive analysis
-npx @glexcorp/gskp install business-growth      # after lifecycle evidence
-npx @glexcorp/gskp install business-ops         # for ongoing operations
+npx skillpacks install customer-lifecycle   # after ICP + competitive analysis
+npx skillpacks install business-growth      # after lifecycle evidence
+npx skillpacks install business-ops         # for ongoing operations
 ```
 
 **Canonical chain:**
@@ -131,7 +131,7 @@ See `docs/pack-workflow-matrix.md` for the full default route with optional deto
 **Install:**
 
 ```bash
-npx @glexcorp/gskp install-deck devtool-afps
+npx skillpacks install-deck devtool-afps
 ```
 
 **Canonical chain:**
@@ -152,7 +152,7 @@ devtool-positioning -> devtool-adoption -> devtool-dx-journey -> devtool-docs-au
 **Install:**
 
 ```bash
-npx @glexcorp/gskp install-deck game-afps
+npx skillpacks install-deck game-afps
 ```
 
 **Canonical chain:**

package/docs/packs.md

@@ -1,10 +1,10 @@
 # Project-Local Skill Packs
 
-Project-local packs keep domain-specific workflows out of global assistant context.
+Project-local packs keep domain-specific workflows out of base assistant context.
 
 ## Design
 
-- Global skills live in `global/{claude,codex}`.
+- Base skills live in `base/{claude,codex}`.
 - Domain packs live in `packs/<pack>/{claude,codex}`.
 - Project designation lives in `.agents/project.json`.
 - Mixed monorepos can declare scoped domain routing in `.agents/project.json.project_scopes`.
@@ -56,28 +56,28 @@ In this model, `project_type` is the default designation for uncategorized work,
 npm CLI commands:
 
 ```bash
-npx @glexcorp/gskp list
-npx @glexcorp/gskp recommend
-npx @glexcorp/gskp install game
-npx @glexcorp/gskp install business-discovery
-npx @glexcorp/gskp install business-growth
-npx @glexcorp/gskp install business-ops
-npx @glexcorp/gskp install devtool
-npx @glexcorp/gskp install creator-foundation
-npx @glexcorp/gskp install youtube-ops
-npx @glexcorp/gskp install code-quality
-npx @glexcorp/gskp install agentic-skills-bench
-npx @glexcorp/gskp install monorepo
-npx @glexcorp/gskp install remotion
-npx @glexcorp/gskp install project-fleet
-npx @glexcorp/gskp install alignment-loop
-npx @glexcorp/gskp remove game
-npx @glexcorp/gskp refresh
-npx @glexcorp/gskp status
-npx @glexcorp/gskp doctor
-npx @glexcorp/gskp doctor --fix
-npx @glexcorp/gskp doctor --fix --agent-docs --dry-run
-npx @glexcorp/gskp set-update-mode <mode>
+npx skillpacks list
+npx skillpacks recommend
+npx skillpacks install game
+npx skillpacks install business-discovery
+npx skillpacks install business-growth
+npx skillpacks install business-ops
+npx skillpacks install devtool
+npx skillpacks install creator-foundation
+npx skillpacks install youtube-ops
+npx skillpacks install code-quality
+npx skillpacks install agentic-skills-bench
+npx skillpacks install monorepo
+npx skillpacks install remotion
+npx skillpacks install project-fleet
+npx skillpacks install alignment-loop
+npx skillpacks remove game
+npx skillpacks refresh
+npx skillpacks status
+npx skillpacks doctor
+npx skillpacks doctor --fix
+npx skillpacks doctor --fix --agent-docs --dry-run
+npx skillpacks set-update-mode <mode>
 ```
 
 Source-checkout equivalents remain available from a local clone:
@@ -89,11 +89,11 @@ scripts/pack.sh refresh
 scripts/pack.sh status
 ```
 
-`npx @glexcorp/gskp install <name>` accepts either a pack name or a skill name from the packaged manifest. Node-owned npm commands preserve `.agents/project.json` fields without requiring `jq`; source-checkout `scripts/pack.sh` write commands still use `jq` for structured JSON edits.
+`npx skillpacks install <name>` accepts either a pack name or a skill name from the packaged manifest. Node-owned npm commands preserve `.agents/project.json` fields without requiring `jq`; source-checkout `scripts/pack.sh` write commands still use `jq` for structured JSON edits.
 
 `doctor` and `set-update-mode` are part of the skill-install drift model — see [Skill-install drift](#skill-install-drift-track-latest-vs-pinned) below.
 
-The npm CLI can install canonical decks from manifest metadata: `npx @glexcorp/gskp install-deck vard`, `npx @glexcorp/gskp install-deck ord`, `npx @glexcorp/gskp install-deck business-afps`, `npx @glexcorp/gskp install-deck devtool-afps`, and `npx @glexcorp/gskp install-deck game-afps`. Deck materialization still uses the packaged shell backend in this phase, so it requires `bash` and `jq`.
+The npm CLI can install canonical decks from manifest metadata: `npx skillpacks install-deck vard`, `npx skillpacks install-deck ord`, `npx skillpacks install-deck business-afps`, `npx skillpacks install-deck devtool-afps`, and `npx skillpacks install-deck game-afps`. Deck materialization still uses the packaged shell backend in this phase, so it requires `bash` and `jq`.
 
 Assistant-native usage also supports guided setup:
 
@@ -143,7 +143,7 @@ For the full workflow/dependency matrix, see [`docs/pack-workflow-matrix.md`](pa
 The `monorepo` pack is an execution overlay for pnpm workspace repositories. It targets repositories with `pnpm-workspace.yaml` and optionally `turbo.json`.
 
 ```bash
-npx @glexcorp/gskp install monorepo
+npx skillpacks install monorepo
 ```
 
 Skills:
@@ -152,14 +152,14 @@ Skills:
 mono-detect, mono-exec, mono-guard, mono-ship
 ```
 
-The pack uses an augmentation injection pattern. Its skills add pre/post behavior around the global `exec` and `ship` contracts instead of replacing them:
+The pack uses an augmentation injection pattern. Its skills add pre/post behavior around the base `exec` and `ship` contracts instead of replacing them:
 
 - `mono-detect` writes `.agents/monorepo.json` with workspace packages, package paths, package scripts, dependency graph, and Turborepo awareness.
 - `mono-exec` injects monorepo detection, lane-spec generation, guard pre-flight checks, serial cross-cutting work, and package-scoped dispatch around standard `run`.
 - `mono-guard` validates lane specs before dispatch and checks integrated diffs against declared ownership after dispatch.
 - `mono-ship` injects package-scoped test/lint/build and transitive-dependent validation before delegating to standard `ship`.
 
-This differs from the former `*-kanban` duplication pattern. The hibernated kanban packs provided alternate command variants such as `exec-kanban`, `ship-kanban`, and `ship-end-kanban`; the active monorepo pack keeps the global lifecycle skills authoritative and makes them workspace-aware through pre/post steps.
+This differs from the former `*-kanban` duplication pattern. The hibernated kanban packs provided alternate command variants such as `exec-kanban`, `ship-kanban`, and `ship-end-kanban`; the active monorepo pack keeps the base lifecycle skills authoritative and makes them workspace-aware through pre/post steps.
 
 Lane dispatch uses two artifacts:
 
@@ -186,7 +186,7 @@ Use `scope: package-scoped` when work is contained to declared package paths, `s
 The `remotion` pack contains the production path that turns reference-video research and creator-media strategy into Remotion-ready artifacts.
 
 ```bash
-npx @glexcorp/gskp install remotion
+npx skillpacks install remotion
 ```
 
 Skills:
@@ -204,7 +204,7 @@ youtube-format-research -> video-script -> video-build
 Install it alongside `creator-foundation` and, when YouTube evidence is needed, `youtube-ops` for the full path from channel evidence, positioning, programming, or product-led media strategy into production:
 
 ```bash
-npx @glexcorp/gskp install creator-foundation youtube-ops remotion
+npx skillpacks install creator-foundation youtube-ops remotion
 ```
 
 ## Alignment Loop Pack
@@ -212,7 +212,7 @@ npx @glexcorp/gskp install creator-foundation youtube-ops remotion
 The `alignment-loop` pack is a lightweight planning on-ramp for projects that need shared taste and intent before a full specification cycle.
 
 ```bash
-npx @glexcorp/gskp install alignment-loop
+npx skillpacks install alignment-loop
 ```
 
 Skills:
@@ -229,15 +229,15 @@ taste-calibration -> destination-doc -> vertical-slice-splitter -> implementatio
 
 ## Compatibility
 
-If a tool does not discover project-local `.claude/skills` or `.codex/skills`, use the global `pack` and `research-roadmap` skills as launchers. They should read `.agents/project.json` and the local pack files directly.
+If a tool does not discover project-local `.claude/skills` or `.codex/skills`, use the base `pack` and `research-roadmap` skills as launchers. They should read `.agents/project.json` and the local pack files directly.
 
-Do not install `packs/*` globally as a fallback; that recreates the context pollution this design avoids.
+Do not install `packs/*` as base skills as a fallback; that recreates the context pollution this design avoids.
 
-Commit `.agents/project.json` with the project. Do not commit generated local skill roots under `.claude/skills` or `.codex/skills`; recreate them with `npx @glexcorp/gskp refresh` or, from a source checkout, `scripts/pack.sh refresh`.
+Commit `.agents/project.json` with the project. Do not commit generated local skill roots under `.claude/skills` or `.codex/skills`; recreate them with `npx skillpacks refresh` or, from a source checkout, `scripts/pack.sh refresh`.
 
 `scripts/pack.sh install`, `remove`, `refresh`, and `set-mode` preserve existing `project_scopes`, `notes`, and `skill_updates` fields when `jq` is available. The npm `gskp` Node-owned project commands preserve `project_scopes`, `notes`, `pinned_versions`, `enabled_skills`, `skill_updates`, and `agent_mode` without requiring `jq`; see `docs/skillpacks-npm-distribution.md` for the current command compatibility matrix.
 
-To migrate an existing project from a local checkout workflow to npm after publication, keep `.agents/project.json` committed and run `npx @glexcorp/gskp refresh` from that project. The generated `.claude/skills` and `.codex/skills` roots will be recreated from the package snapshot. If the project pins a skill version, the installed package must include that skill's `archive/<version>/SKILL.md`.
+To migrate an existing project from a local checkout workflow to npm after publication, keep `.agents/project.json` committed and run `npx skillpacks refresh` from that project. The generated `.claude/skills` and `.codex/skills` roots will be recreated from the package snapshot. If the project pins a skill version, the installed package must include that skill's `archive/<version>/SKILL.md`.
 
 Pack writes use `.agents/.pack.lock` with owner metadata (`pid`, `started_at`, `command`). If a previous pack command exits without releasing the lock and its recorded process is no longer running, the next pack command removes the stale lock automatically. If a live process still owns the lock, timeout errors include the owner metadata.
 
@@ -257,33 +257,33 @@ scripts/pack.sh refresh    # re-copy installs from canonical, rewriting markers
 
 `doctor` statuses: `ok` (matches canonical), `stale (vOld → vNew)` (canonical moved), `unknown` (a pre-upgrade marker has no `source_sha` — run `refresh` once to enable tracking, never a false `stale`), `pinned vX (frozen)`, and `missing-source` (canonical path gone). `doctor` only detects *canonical moved*; it does not detect local edits to an installed copy.
 
-**Update mode.** `.agents/project.json` may carry `skill_updates.mode` — `warn` (default) or `auto`. Set it with `scripts/pack.sh set-update-mode <warn|auto|unset>`. A trigger (the session-start hook, or sync-with-approval) that sees `mode == auto`, or global `~/.agentic-skills/preferences.json` `skills.auto_refresh == true`, runs `refresh` automatically; otherwise it only warns. `doctor` itself never mutates — it renders the effective policy.
+**Update mode.** `.agents/project.json` may carry `skill_updates.mode` — `warn` (default) or `auto`. Set it with `scripts/pack.sh set-update-mode <warn|auto|unset>`. A trigger (the session-start hook, or sync-with-approval) that sees `mode == auto`, or machine-wide `~/.agentic-skills/preferences.json` `skills.auto_refresh == true`, runs `refresh` automatically; otherwise it only warns. `doctor` itself never mutates — it renders the effective policy.
 
-**Session-start hook (opt-in, off by default).** `/init-agentic-skills` offers to enable a `SessionStart` hook (`scripts/skill-drift-hook.sh`) that warns about stale installs at session start, or auto-refreshes when `skills.auto_refresh` / `skill_updates.mode == auto` is set. Register or remove the hook directly with `scripts/init-agentic-skills.sh hook enable|disable`, which writes (or clears) the `~/.claude/settings.json` `SessionStart` entry and sets the `session_start_hook` preference. Preferences live in `~/.agentic-skills/preferences.json` under `skills` (`session_start_hook`, `auto_refresh`); set them with `scripts/init-agentic-skills.sh set-pref <key> <value>` and inspect them with `scripts/init-agentic-skills.sh show-prefs`. Disable by declining the prompt, running `scripts/init-agentic-skills.sh set-pref session_start_hook false`, or `scripts/init-agentic-skills.sh hook disable`.
+**Session-start hook (opt-in, off by default).** An optional `SessionStart` hook (`scripts/skill-drift-hook.sh`) warns about stale project skill installs at session start, or auto-refreshes when `skill_updates.mode == auto` (or machine-wide `~/.agentic-skills/preferences.json` `skills.auto_refresh == true`) is set. Enable it by registering a `SessionStart` entry in `~/.claude/settings.json` that runs `bash <checkout>/scripts/skill-drift-hook.sh` (Claude Code's `/update-config` can write this for you) and setting `skills.session_start_hook: true` in `~/.agentic-skills/preferences.json`. The hook is gated on that preference, so an unset or `false` value makes it a silent no-op. Remove the `SessionStart` entry (or set the preference to `false`) to disable it.
 
-Global installs follow the same model: `scripts/init-agentic-skills.sh doctor` reports global drift against `global/<tool>/<skill>`, and `/init-agentic-skills update` re-copies them (the global "refresh").
+Base skill installs follow the same model: `npx skillpacks doctor` reports project base drift against `base/<tool>/<skill>`, and `npx skillpacks refresh` recreates them from the package snapshot (the base "refresh").
 
 ## Team Setup Checklist
 
 For teams adopting agentic-skills across multiple developers:
 
 1. **Choose a checkout path.** Each developer clones this repo locally. The path does not need to match across developers, but `scripts/pack.sh refresh` may need to re-run if the checkout moves.
-2. **Run `./init.sh` once per developer.** This installs global core skills to each developer's `~/.claude/skills/` and `~/.codex/skills/`.
+2. **Run `npx skillpacks init` once per project.** This installs base skills **project-local** into the project's `.claude/skills/` and `.codex/skills/` and records `base_skills: true` in `.agents/project.json`.
 3. **Commit `.agents/project.json`.** This file records the project's pack designation and should be checked into the target project repository.
 4. **Never commit generated skill roots.** `.claude/skills/` and `.codex/skills/` in consumer projects are generated from `.agents/project.json`. Add them to `.gitignore`.
 5. **Run `scripts/pack.sh refresh` after pulling pack changes.** When `.agents/project.json` changes upstream (e.g. a new pack is added), each developer runs refresh to recreate their local skill roots.
 6. **Restart CLI after install/remove/refresh.** Skills are not hot-reloaded. Claude Code: `/reload-skills` then `/clear` or restart. Codex: fresh session.
 7. **Agree on shipping workflow.** The default is direct-to-primary (commit and push to main/master). If your team uses feature branches, note this in `.agents/project.json` `notes` or your project's CLAUDE.md.
 
-## Former Global Domain Skills
+## Former Base Domain Skills
 
-Business/product workflows that used to be globally installed now live in narrow business packs. Prefer the current lane:
+Business/product workflows that used to be base skills now live in narrow business packs. Prefer the current lane:
 
 ```bash
-npx @glexcorp/gskp install business-discovery
-npx @glexcorp/gskp install customer-lifecycle
-npx @glexcorp/gskp install business-growth
-npx @glexcorp/gskp install business-ops
+npx skillpacks install business-discovery
+npx skillpacks install customer-lifecycle
+npx skillpacks install business-growth
+npx skillpacks install business-ops
 ```
 
 `business-app` remains a compatibility alias that installs all four. Creator-media and YouTube work is split between `creator-foundation`, `youtube-ops`, and `remotion`; fleet/portfolio work lives in `project-fleet`.