@glexcorp/gskp 0.1.1 → 0.1.2

package/AGENTS.md

@@ -1,4 +1,4 @@
-<!-- provision-agentic-config v0.10 -->
+<!-- provision-agentic-config v0.11 -->
 ## Workflow Orchestration
 
 ### 1. Plan Mode Default
@@ -42,7 +42,7 @@
 ### Missing Skill Fallback
 - If a user invokes a command-like skill such as `$benchmark-test-skill design-system` and the leading command is not in the injected session skill list, search project-local packs before falling back to the trailing argument as the active skill.
 - Check `packs/*/codex/*/SKILL.md` and pack metadata such as `packs/*/PACK.md`; project-local pack skills may exist in this repository even when they are not visible in the active session list.
-- For any missing skill, run `scripts/pack.sh which <skill-name>` to locate the providing pack. If found in an uninstalled pack, recommend `npx @glexcorp/gskp install <pack-or-skill>` from the project shell for either the skill or the full pack, and note the post-install reload path: Claude Code `/reload-skills` first, `/clear` can pick up the refreshed registry, restart if the top-level `.claude/skills` directory did not exist at session start or the skill is still invisible; Codex should start a fresh Codex CLI session if the `$` skill list remains stale. If found in an installed pack, suggest the same reload path. If not found in any pack, suggest `$skills` or `$skills search <keyword>`.
+- For any missing skill, run `scripts/pack.sh which <skill-name>` to locate the providing pack. If found in an uninstalled pack, recommend `npx skillpacks install <pack-or-skill>` from the project shell for either the skill or the full pack, and note the post-install reload path: Claude Code `/reload-skills` first, `/clear` can pick up the refreshed registry, restart if the top-level `.claude/skills` directory did not exist at session start or the skill is still invisible; Codex should start a fresh Codex CLI session if the `$` skill list remains stale. If found in an installed pack, suggest the same reload path. If not found in any pack, suggest `$skills` or `$skills search <keyword>`.
 
 ### Prompt History
 - On every skill invocation, before substantive work, create `prompts/<skill-slug>/` if it does not exist.

package/CLAUDE.md

@@ -1,4 +1,4 @@
-<!-- provision-agentic-config v0.10 -->
+<!-- provision-agentic-config v0.11 -->
 ## Workflow Orchestration
 
 ### 1. Plan Mode Default
@@ -41,7 +41,7 @@
 
 ### Missing Skill Fallback
 - When a skill invocation fails because the skill is not found, run `scripts/pack.sh which <skill-name>` to check if the skill exists in an available pack.
-- If found in an uninstalled pack, recommend `npx @glexcorp/gskp install <pack-or-skill>` from the project shell for either the skill or the full pack, and note the post-install reload path: Claude Code `/reload-skills` first, `/clear` can pick up the refreshed registry, restart if the top-level `.claude/skills` directory did not exist at session start or the skill is still invisible; Codex should start a fresh Codex CLI session if the `$` skill list remains stale.
+- If found in an uninstalled pack, recommend `npx skillpacks install <pack-or-skill>` from the project shell for either the skill or the full pack, and note the post-install reload path: Claude Code `/reload-skills` first, `/clear` can pick up the refreshed registry, restart if the top-level `.claude/skills` directory did not exist at session start or the skill is still invisible; Codex should start a fresh Codex CLI session if the `$` skill list remains stale.
 - If found in an installed pack, suggest the same reload path to pick up the local skill roots.
 - If not found in any pack, suggest `/skills` or `/skills search <keyword>`.
 
@@ -163,4 +163,4 @@ Research-producing skills maintain a shared project glossary at `research/glossa
 
 ### Cross-Pack Routing
 
-When a skill recommends another skill from a different pack, verify the target pack is installed via `.agents/project.json` `enabled_packs`. If not installed, include `npx @glexcorp/gskp install <pack-name>` as the prerequisite in the recommendation.
+When a skill recommends another skill from a different pack, verify the target pack is installed via `.agents/project.json` `enabled_packs`. If not installed, include `npx skillpacks install <pack-name>` as the prerequisite in the recommendation.

package/README.md

@@ -1,10 +1,10 @@
-# Agentic Skills
+# gSkillPacks
 
 A shared skill library for Claude Code and OpenAI Codex.
 
 The library now uses a two-layer model:
 
-- **Global core skills** are domain-neutral and safe to expose in every project.
+- **Base skills** are domain-neutral and safe to expose in every project.
 - **Project-local packs** hold domain-specific workflows such as business apps, video games, and developer tools.
 
 This keeps game research out of B2B SaaS sessions, and keeps business-product assumptions out of game and devtool projects.
@@ -12,7 +12,7 @@ This keeps game research out of B2B SaaS sessions, and keeps business-product as
 ## Prerequisites
 
 - **Node.js 18+** for the `gskp` npm CLI and package build.
-- **bash** shell (macOS, Linux, or WSL on Windows) for `./init.sh`, `scripts/pack.sh`, and the remaining shell-backed `gskp` commands.
+- **bash** shell (macOS, Linux, or WSL on Windows) for `scripts/pack.sh` and the 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` project commands do not require `jq`.
 - **Claude Code** or **OpenAI Codex** installed on your machine
 - **pnpm** (optional, for running tests): `npm install -g pnpm`
@@ -27,11 +27,11 @@ The source-checkout path is available today and remains supported:
 
 ```bash
 git clone <this-repo-url> ~/agentic-skills
-cd ~/agentic-skills
-./init.sh
+cd ~/my-project
+npx skillpacks init
 ```
 
-Project-local packs are installed from the checkout:
+Base skills install **project-local** into the current repository (`.claude/skills/`, `.codex/skills/`). Project-local packs are installed from the checkout:
 
 ```bash
 cd ~/my-project
@@ -46,37 +46,36 @@ With the published npm package, users can install from the current project direc
 
 ```bash
 cd ~/my-project
-npx @glexcorp/gskp init
-npx @glexcorp/gskp install devtool
-npx @glexcorp/gskp install code-quality
-npx @glexcorp/gskp install-deck game-afps
-npx @glexcorp/gskp refresh
-npx @glexcorp/gskp status
+npx skillpacks init
+npx skillpacks install devtool
+npx skillpacks install code-quality
+npx skillpacks install-deck game-afps
+npx skillpacks refresh
+npx skillpacks status
 ```
 
-`npx @glexcorp/gskp init` installs the base skills for the current repository as project-local roots. `npx @glexcorp/gskp install <pack-or-skill>` adds domain packs or individual pack skills. Both write project-local files: `.agents/project.json`, `.claude/skills/*`, and `.codex/skills/*`. Package semver such as `@glexcorp/gskp@0.1.0` selects the bundled skill snapshot; `npx @glexcorp/gskp refresh` recreates enabled base skills and packs from that snapshot. Individual skill pins still use each skill's `version:` value through `gskp pin <skill> <version>`.
+`npx skillpacks init` installs the base skills for the current repository as project-local roots. `npx skillpacks install <pack-or-skill>` adds domain packs or individual pack skills. Both write project-local files: `.agents/project.json`, `.claude/skills/*`, and `.codex/skills/*`. Package semver such as `skillpacks@0.1.0` selects the bundled skill snapshot; `npx skillpacks refresh` recreates enabled base skills and packs from that snapshot. Individual skill pins still use each skill's `version:` value through `skillpacks pin <skill> <version>` or `gskp pin <skill> <version>`.
 
-The package still installs both `gskp` and `skillpacks` binaries for global or local `npm exec --package @glexcorp/gskp ...` usage. Do not use `npx skillpack ...` singular; that is an unrelated npm package with a different project format.
+The same release is also published as the scoped alias package `@glexcorp/gskp`, so `npx @glexcorp/gskp init` is equivalent to `npx skillpacks init` at the same version. Both packages install both `gskp` and `skillpacks` binaries for global or local `npm exec --package skillpacks ...` or `npm exec --package @glexcorp/gskp ...` usage. Do not use `npx skillpack ...` singular; that is an unrelated npm package with a different project format.
 
 ## Initialization
 
 ```bash
-./init.sh
+cd ~/my-project
+npx skillpacks init
 ```
 
-`init.sh` initializes only user-home global core skills:
-
-- `global/claude/*` -> `~/.claude/skills/*`
-- `global/codex/*` -> `~/.codex/skills/*`
+`npx skillpacks init` initializes base skills **project-local** for the current repository:
 
-It does **not** install `packs/*` globally.
+- `base/claude/*` -> `<project>/.claude/skills/*`
+- `base/codex/*` -> `<project>/.codex/skills/*`
 
-For npm consumers, prefer `npx @glexcorp/gskp init` in each target repository. That installs the same base skill sources project-locally and records `base_skills: true` in `.agents/project.json`, so later `npx @glexcorp/gskp refresh` updates them from the package version being run. Use `npx @glexcorp/gskp init --global` (or the backward-compatible `npx @glexcorp/gskp init-global`) only when you explicitly want user-home global core installs from the package snapshot. Domain packs are never installed globally.
+It records `base_skills: true` in `.agents/project.json`, so later `npx skillpacks refresh` updates them from the package version being run. It does **not** install `packs/*` — domain packs are never installed as base skills.
 
-To remove repo-managed global skill installs:
+There is no user-home (global) base install. To clean up legacy repo-managed base installs left in `~/.claude/skills` and `~/.codex/skills` by the retired init path:
 
 ```bash
-./init.sh --uninstall
+npx skillpacks uninstall-global
 ```
 
 ## Project Packs
@@ -84,48 +83,48 @@ To remove repo-managed global skill installs:
 Project packs are enabled per repository.
 
 ```bash
-npx @glexcorp/gskp list
-npx @glexcorp/gskp recommend
-npx @glexcorp/gskp install business-discovery
-npx @glexcorp/gskp install business-growth
-npx @glexcorp/gskp install business-ops
-npx @glexcorp/gskp install game
-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 install design-system
-npx @glexcorp/gskp which design-system
-npx @glexcorp/gskp status
-npx @glexcorp/gskp remove game
-npx @glexcorp/gskp remove design-system
+npx skillpacks list
+npx skillpacks recommend
+npx skillpacks install business-discovery
+npx skillpacks install business-growth
+npx skillpacks install business-ops
+npx skillpacks install game
+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 install design-system
+npx skillpacks which design-system
+npx skillpacks status
+npx skillpacks remove game
+npx skillpacks remove design-system
 ```
 
-`npx @glexcorp/gskp install <name>` accepts either a pack name or a skill name from any pack. Pack names install every skill in the pack. Skill names install only that one project-local skill and record it under `.agents/project.json` `enabled_skills`.
+`npx skillpacks install <name>` accepts either a pack name or a skill name from any pack. Pack names install every skill in the pack. Skill names install only that one project-local skill and record it under `.agents/project.json` `enabled_skills`.
 
-For source-checkout development, `scripts/pack.sh install <pack-or-skill>` remains supported from a local clone. The npm CLI also supports `npx @glexcorp/gskp refresh`, `npx @glexcorp/gskp doctor`, `npx @glexcorp/gskp doctor --fix`, `npx @glexcorp/gskp doctor --fix --agent-docs --dry-run`, and deck installation from manifest metadata including `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`.
+For source-checkout development, `scripts/pack.sh install <pack-or-skill>` remains supported from a local clone. The npm CLI also supports `npx skillpacks refresh`, `npx skillpacks doctor`, `npx skillpacks doctor --fix`, `npx skillpacks doctor --fix --agent-docs --dry-run`, and deck installation from manifest metadata including `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`.
 
 Alignment convention maintenance also has npm wrappers:
 
 ```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 @glexcorp/gskp alignment verify
+npx skillpacks alignment bundles --check
+npx skillpacks alignment pages audit
+npx skillpacks alignment pages inject-tts --force alignment/example.html
+npx skillpacks alignment verify
 ```
 
-Use direct `node scripts/upgrade-alignment-page.mjs`, `node scripts/audit-alignment-pages.mjs`, and `node scripts/inject-tts.mjs` commands from a source checkout. Use `npx @glexcorp/gskp alignment ...` from npm-installed target repos.
+Use direct `node scripts/upgrade-alignment-page.mjs`, `node scripts/audit-alignment-pages.mjs`, and `node scripts/inject-tts.mjs` commands from a source checkout. Use `npx skillpacks alignment ...` from npm-installed target repos.
 
-`scripts/pack.sh list-packs` is an internal subcommand used by Codex `$exec` routing (see `global/codex/exec/SKILL.md`). It prints enabled packs from `.agents/project.json` one per line with no decoration, distinct from the human-facing `list` above; prefer `list` or `status` for interactive use.
+`scripts/pack.sh list-packs` is an internal subcommand used by Codex `$exec` routing (see `base/codex/exec/SKILL.md`). It prints enabled packs from `.agents/project.json` one per line with no decoration, distinct from the human-facing `list` above; prefer `list` or `status` for interactive use.
 
 Claude users can run `/pack` with no arguments, and Codex users can run `$pack` with no arguments. If `.agents/project.json` exists, the skill refreshes local skill roots from that committed project designation. If it is missing, the assistant inspects the repository, recommends a pack, and asks before installing.
 
-`npx @glexcorp/gskp which <skill>` shows which pack provides a skill and whether it is installed. `npx @glexcorp/gskp refresh` recreates local skill roots; it does not by itself force an active CLI skill registry to reload. Claude Code watches existing `.claude/skills` roots and supports `/reload-skills`; `/clear` starts a new empty-context conversation and can also pick up refreshed skills. Restart Claude Code if `.claude/skills` did not exist when the session started or the skill is still invisible. In Codex, start a fresh Codex CLI session if the `$` skill list stays stale.
+`npx skillpacks which <skill>` shows which pack provides a skill and whether it is installed. `npx skillpacks refresh` recreates local skill roots; it does not by itself force an active CLI skill registry to reload. Claude Code watches existing `.claude/skills` roots and supports `/reload-skills`; `/clear` starts a new empty-context conversation and can also pick up refreshed skills. Restart Claude Code if `.claude/skills` did not exist when the session started or the skill is still invisible. In Codex, start a fresh Codex CLI session if the `$` skill list stays stale.
 
 Pack installation creates local repo-managed skill roots in the current project. Active installs expose the canonical `SKILL.md` and exclude `archive/`:
 
@@ -176,7 +175,7 @@ Pack commands also write `.agents/.pack.lock` owner metadata and automatically r
 
 `.agents/project.json` also accepts an optional `agent_mode` field (`"claude-only" | "codex-only" | "hybrid"`) that names the Phase 11 operating mode for the project. Set or clear it with `scripts/pack.sh set-mode <claude-only|codex-only|hybrid|unset>`; the value is preserved across `install`, `remove`, and `refresh`. `SKILLS_AGENT_MODE` overrides the file for the current shell, and `scripts/agent-mode.sh` resolves the effective mode (env > project.json > empty). See `docs/operating-modes.md`.
 
-If an assistant does not discover project-local skills, use the global `pack` or `research-roadmap` skill as the launcher. The pack files still stay project-local.
+If an assistant does not discover project-local skills, use the base `pack` or `research-roadmap` skill as the launcher. The pack files still stay project-local.
 
 For workflow ordering, lead-in recommendations, and overlay dependencies, see [`docs/pack-workflow-matrix.md`](docs/pack-workflow-matrix.md).
 
@@ -184,7 +183,7 @@ For workflow ordering, lead-in recommendations, and overlay dependencies, see [`
 
 ```text
 agentic-skills/
-├── global/
+├── base/
 │   ├── claude/<name>/SKILL.md
 │   └── codex/<name>/SKILL.md
 ├── packs/
@@ -210,34 +209,34 @@ agentic-skills/
 │   └── skills-showcase/
 ├── packages/
 │   └── skillpacks/
-├── init.sh
 └── docs/
 ```
 
-The repository root is private workspace metadata. The publishable `gskp` package source lives in `packages/skillpacks/`, while the public Skills Showcase app and its data generators live in `apps/skills-showcase/`.
+The repository root is private workspace metadata. The publishable `skillpacks` package source lives in `packages/skillpacks/`; `@glexcorp/gskp` is generated as a staged package variant during release. The public Skills Showcase app and its data generators live in `apps/skills-showcase/`.
 
-## Global Core
+## Base Core
 
-The global surface is intentionally small and domain-neutral. `./init.sh` installs six skills under `global/claude/` (mirrored under `global/codex/`):
+The base surface is intentionally small and domain-neutral. `npx skillpacks init` installs 11 skills under `base/claude/`, 8 of which are mirrored under `base/codex/`:
 
 ```text
-codebase-status, idea-scope-brief, init-agentic-skills, pack,
-provision-agentic-config, skills
+afps-status, animation-design-planner, autoresearch, autoresearch-prep,
+codebase-status, fork-idea-branch, idea-scope-brief, init-agentic-skills,
+pack, provision-agentic-config, skills
 ```
 
-### Codex-only global skill
+### Claude-only base skills
 
-One global skill ships only under `global/codex/` (no `global/claude/` mirror):
+Three base skills ship only under `base/claude/` (no `base/codex/` mirror):
 
 ```text
-afps-status
+autoresearch, autoresearch-prep, fork-idea-branch
 ```
 
 `$afps-status` summarizes AFPS product-workflow progress from existing artifacts and recommends the next concrete skill command. It is read-mostly reconciliation, not a competing workflow state system.
 
 ### `delegate` moved to the `agent-bridge` pack
 
-`delegate` is **no longer global** — it lives in `packs/agent-bridge/claude/delegate`. Install it with `npx @glexcorp/gskp install agent-bridge`. It remains **Claude-only** with no Codex mirror.
+`delegate` is **no longer a base skill** — it lives in `packs/agent-bridge/claude/delegate`. Install it with `npx skillpacks install agent-bridge`. It remains **Claude-only** with no Codex mirror.
 
 `/delegate` is the synchronous, in-session sibling of `/handoff --target=codex`: it drafts and approves a packet via `scripts/approved-plan.sh`, then invokes `codex exec "<target-skill> --execute-approved"` live from Claude. It is `hybrid`-only by design. Codex users should not expect a `$delegate` — drive hybrid delegation from the Claude side, or use `/handoff --target=codex` for the async variant. See `packs/agent-bridge/claude/delegate/SKILL.md` and `docs/operating-modes.md`.
 
@@ -264,7 +263,7 @@ burn-rate, runway-model, investor-update, reconcile-research,
 mvp-gap, scale-audit, platform-strategy
 ```
 
-`npx @glexcorp/gskp install business-app` remains a compatibility alias that installs all four, but narrow installs are preferred for context size.
+`npx skillpacks install business-app` remains a compatibility alias that installs all four, but narrow installs are preferred for context size.
 
 
 ### Game
@@ -308,7 +307,7 @@ youtube-portfolio, youtube-peer-benchmark, youtube-search-positioning,
 youtube-cadence-diagnosis
 ```
 
-`npx @glexcorp/gskp install creator-media` remains a compatibility alias that installs `creator-foundation` and `youtube-ops`. Use `remotion` for `youtube-format-research`, `video-script`, and `video-build`.
+`npx skillpacks install creator-media` remains a compatibility alias that installs `creator-foundation` and `youtube-ops`. Use `remotion` for `youtube-format-research`, `video-script`, and `video-build`.
 
 LinkedIn-first evidence work uses the `creator-foundation` matrix/schema/dossier path:
 
@@ -365,7 +364,7 @@ extract-shared-types, quality-sweep
 For pnpm workspace monorepos that may use Turborepo and need package-aware execution, guardrails, and shipping.
 
 ```bash
-npx @glexcorp/gskp install monorepo
+npx skillpacks install monorepo
 ```
 
 ```text
@@ -398,16 +397,16 @@ PoketoWork kanban packs are hibernated while Poketo.work is being rebuilt. Their
 
 ## Moved Skills
 
-Former global business/product skills now live in narrower project packs. `business-app` remains a compatibility alias for all four business packs.
+Former base business/product skills now live in narrower project packs. `business-app` remains a compatibility alias for all four business packs.
 
 ```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
 ```
 
-Creator-media and YouTube work is similarly split between `creator-foundation`, `youtube-ops`, and `remotion`. Fleet/portfolio work moved from global core into `project-fleet`.
+Creator-media and YouTube work is similarly split between `creator-foundation`, `youtube-ops`, and `remotion`. Fleet/portfolio work moved from base core into `project-fleet`.
 
 ## Version Pinning
 
@@ -415,14 +414,14 @@ Skills can be pinned to an archived version. When a skill's version is bumped, t
 
 ```bash
 # Archive current version before bumping
-bash scripts/skill-archive.sh global/claude/ship
+bash scripts/skill-archive.sh base/claude/codebase-status
 
 # Pin a pack skill to an archived version
 scripts/pack.sh pin devtool-adoption v0.0
 scripts/pack.sh unpin devtool-adoption
 
-# Pin a global skill during initialization
-./init.sh --pin ship=v0.0
+# Pin a base skill to an archived version
+npx skillpacks pin ship v0.0
 
 # Audit archive integrity
 bash scripts/skill-archive-audit.sh
@@ -442,7 +441,7 @@ See [`docs/skill-versioning.md`](docs/skill-versioning.md) for the full versioni
 pnpm --dir tests test
 ```
 
-`skill-deps.sh`, `skill-pack-routing-audit.sh`, and `skill-versions.sh` scan `global/` and `packs/`; `skill-mirror-parity-audit.sh` checks mirrored pack skill pairs under `packs/`.
+`skill-deps.sh`, `skill-pack-routing-audit.sh`, and `skill-versions.sh` scan `base/` and `packs/`; `skill-mirror-parity-audit.sh` checks mirrored pack skill pairs under `packs/`.
 
 Live agent behavior tests are opt-in because they invoke authenticated CLIs and may spend model budget:
 

package/{global → base}/claude/fork-idea-branch/SKILL.md

@@ -10,7 +10,7 @@ argument-hint: "[path-a-label] [path-b-label] [--from <skill>] [--reuse <artifac
 
 Use this skill when a single research path should split into multiple parallel product paths — for example, two compelling ICPs with conflicting pain points that need separate products, or positioning evidence showing the concept serves fundamentally different markets. This skill archives the current research, scaffolds new product paths, and routes each back to `/idea-scope-brief` for a fresh start.
 
-This is a global helper, not part of any pack's linear workflow. It can be invoked directly by the user or suggested by research skills when alignment page answers indicate divergent paths.
+This is a base helper, not part of any pack's linear workflow. It can be invoked directly by the user or suggested by research skills when alignment page answers indicate divergent paths.
 
 This skill is distinct from `/product-line fork` (which adds a path to the portfolio). This skill splits and restarts research from scratch.
 

package/{global → base}/claude/init-agentic-skills/CHANGELOG.md

@@ -1,5 +1,13 @@
 # Changelog
 
+## v0.10 - 2026-06-13
+
+- Sunset the user-home (global) install path. Base skills now install **project-local** via `npx skillpacks init` only; there is no `init.sh`, `--global`, or `~/.claude/skills` base install. Rewrote the process around `npx skillpacks` (`init`/`refresh`/`status`/`doctor`) and added an `uninstall-global` mode that runs `npx skillpacks uninstall-global` to clean up legacy repo-managed installs left in `~/.claude/skills` and `~/.codex/skills`. Dropped the `update`/`latest` checkout-refresh flow and the first-run drift-preference prompts that depended on the retired launcher.
+
+## v0.9 - 2026-06-13
+
+- Renamed the source skill set from "global" to "base": canonical sources moved to `base/<tool>/<skill>`, and drift/refresh prose now says "base skills". The `--global`/`init-global` install-location flags are unchanged.
+
 ## v0.8 - 2026-06-12
 
 - Standardized active pack and skill install guidance on `npx skillpacks install <pack-or-skill>` instead of agent-native `/pack install` or `$pack install` recommendations.

package/base/claude/init-agentic-skills/SKILL.md

@@ -0,0 +1,41 @@
+---
+name: init-agentic-skills
+description: Make the base agentic-skills available in a project by installing them project-local with npx skillpacks init, report and fix skill-install drift, clean up legacy user-home installs, and route domain packs to the pack skill. Use when Claude needs to enable base skills for a project, repair stale installs, confirm initialization status, remove old global installs, or explain how to enable packs.
+type: ops
+version: v0.10
+argument-hint: "[init|status|doctor|refresh|uninstall-global]"
+---
+
+# Init Agentic Skills
+
+Make the base agentic-skills available by installing them **project-local** into the current project's `.claude/skills` and `.codex/skills`. Installation is distributed through the npm `skillpacks` package — there is no user-home (global) install path. Active installs are repo-managed directories that expose the canonical `SKILL.md` and exclude `archive/`; pinned installs intentionally point at `archive/<version>`. Keep domain packs project-local too; use `/pack` from the target project or `npx skillpacks install <pack-or-skill>` when packs are needed.
+
+## Process
+
+1. Parse `$ARGUMENTS`:
+   - No args, `init`, or `refresh`: run `npx skillpacks init` from the project root to install the base skills project-local (`.claude/skills` + `.codex/skills`) and enable `base_skills` in `.agents/project.json`. Use `npx skillpacks refresh` instead when the project is already initialized and you only need to recreate roots from `.agents/project.json`.
+   - `status`: run `npx skillpacks status` to report the project designation, enabled packs, and installed skills.
+   - `doctor`: run `npx skillpacks doctor` to report project skill-install drift (read-only). It compares installed `.claude/skills` and `.codex/skills` copies against their canonical sources via the `.agentic-skills-managed` marker's `source_sha`. Report `STALE` skills with the printed fix command, `unknown` skills as needing a refresh to enable tracking, `missing` skills whose source is gone, and `pinned` skills as frozen. Run `npx skillpacks doctor --fix` to clean generated skill-root drift.
+   - `uninstall-global`: run `npx skillpacks uninstall-global` only after confirming the user wants legacy repo-managed base installs removed from `~/.claude/skills` and `~/.codex/skills`. This cleans up installs created by the retired user-home init path; it removes only skillpacks-owned installs and leaves unmanaged directories untouched.
+   - `help`, `--help`, or `-h`: run `npx skillpacks --help`.
+2. Report the command run, the project skill directories, installed counts, and any warnings about non-repo-managed collisions.
+3. Explain pack access separately:
+   - Do not install `packs/*` as base skills.
+   - In the project that needs domain workflows, run `/pack` for guided setup, or `npx skillpacks install <pack-or-skill>` from the project shell for an explicit pack or individual pack skill.
+   - If a project already has `.agents/project.json`, use `/pack refresh` (or `npx skillpacks refresh`) after this base initialization to recreate local pack skill roots.
+4. If the active session still cannot see a newly installed or refreshed skill, report the skill-visibility reload path:
+   - Claude Code: run `/reload-skills` first; `/clear` starts a new empty-context conversation and can pick up the refreshed registry; restart if the top-level `.claude/skills` directory did not exist at session start or the skill is still invisible.
+   - Codex: start a fresh Codex CLI session if the `$` skill list remains stale.
+
+## Constraints
+
+- Drive installation through `npx skillpacks` (the npm `skillpacks` CLI); do not recreate install logic by hand or reintroduce a user-home/global install path.
+- Base skills are project-local: they install into the current project's `.claude/skills` and `.codex/skills`, not into `~/.claude/skills` or `~/.codex/skills`.
+- Do not overwrite real directories or files under `.claude/skills` or `.codex/skills` that are not repo-managed.
+- Treat packs as project-local capabilities managed through `/pack` (`npx skillpacks` under the hood).
+- Stop and report exact errors if `npx skillpacks` fails.
+- Do not install `packs/*` as base skills in any mode.
+
+## Default Shipping Contract
+
+Follow the shared shipping contract convention in CLAUDE.md.

package/base/claude/init-agentic-skills/archive/v0.9/SKILL.md

@@ -0,0 +1,56 @@
+---
+name: init-agentic-skills
+description: Initialize this agentic-skills checkout on a developer machine by running the repository init script, verify base managed skill installs, uninstall repo-managed installs when requested, and route project-local pack setup to the pack skill. Use when Claude needs to make all base agentic-skills skills available on the current machine, repair stale installs, confirm initialization status, or explain how to enable packs for a project.
+type: ops
+version: v0.9
+argument-hint: "[init|status|doctor|update|latest|--uninstall]"
+---
+
+# Init Agentic Skills
+
+Initialize this `agentic-skills` checkout on the current machine by installing base skills for both Claude and Codex. Active installs are repo-managed directories that expose the canonical `SKILL.md` and exclude `archive/`; copied managed launchers resolve this checkout through `.agentic-skills-managed` provenance. Pinned installs intentionally point at `archive/<version>`. Keep domain packs project-local; use `/pack` from the target project or `npx skillpacks install <pack-or-skill>` from the project shell when packs are needed.
+
+## Process
+
+1. Parse `$ARGUMENTS`:
+   - No args, `init`, `refresh`, or `sync`: run `scripts/init-agentic-skills.sh`, then run the first-run setup prompts in step 6 when the drift preferences are still unset.
+   - `status`: run `scripts/init-agentic-skills.sh status`, then report the local checkout commit, remote URL, and whether GitHub freshness is enabled by `~/.agentic-skills/preferences.json` at `sync.github_freshness_check`.
+   - `doctor`: run `scripts/init-agentic-skills.sh doctor` to report base skill-install drift (read-only). It compares installed `~/.claude/skills` and `~/.codex/skills` copies against canonical `base/<tool>/<skill>` via the `.agentic-skills-managed` marker's `source_sha`. Report `stale` skills with the fix `/init-agentic-skills update`, `unknown` skills as needing a re-init to enable tracking, and `pinned` skills as frozen.
+   - `update` or `latest`: run `scripts/init-agentic-skills.sh update` only after confirming the user wants to check GitHub, fast-forward the local checkout, and rerun `init.sh`. This re-copy is the base "refresh" — it rewrites markers with current `source_version`/`source_sha`, clearing drift.
+   - `--uninstall`, `uninstall`, or `remove`: run `scripts/init-agentic-skills.sh --uninstall` only after confirming the user wants repo-managed base installs removed.
+   - `help`, `--help`, or `-h`: run `scripts/init-agentic-skills.sh --help`.
+2. Report the initializer command, the Claude and Codex skill directories, installed/skipped counts, and warnings about non-repo-managed collisions.
+3. Explain pack access separately:
+   - Do not install `packs/*` as base skills.
+   - In the project that needs domain workflows, run `/pack` for guided setup, or `npx skillpacks install <pack-or-skill>` from the project shell for an explicit pack or individual pack skill.
+   - If a project already has `.agents/project.json`, use `/pack refresh` after this base initialization to recreate local pack skill roots.
+4. If the active session still cannot see a newly installed or refreshed skill, report the skill-visibility reload path:
+   - Claude Code: run `/reload-skills` first; `/clear` starts a new empty-context conversation and can pick up the refreshed registry; restart if the top-level `.claude/skills` directory did not exist at session start or the skill is still invisible.
+   - Codex: start a fresh Codex CLI session if the `$` skill list remains stale.
+5. For `update` / `latest` mode:
+   - Confirm before running commands that fetch, pull, or reinstall.
+   - Fetch GitHub freshness, compare the local checkout to `origin/HEAD`, and update only with a fast-forward-only operation such as `git pull --ff-only` or an equivalent `git fetch` + `git merge --ff-only`.
+   - If the update cannot fast-forward cleanly, stop and report the exact reason without rebasing, merging, stashing, or force-resetting.
+   - After a successful fast-forward, rerun `init.sh`.
+   - Warn that Claude Code should use `/reload-skills` first, then `/clear` or restart if needed, and that Codex should start a fresh Codex CLI session if the `$` skill list remains stale.
+6. First-run drift preferences (init / clone setup):
+   - Default policy is **track-latest** (installed skills follow canonical; drift is observable). The two prompts below are **opt-in and off by default**, so the explicit-control default stays out of the box.
+   - Only prompt when the preference keys are still unset. Check with `scripts/init-agentic-skills.sh show-prefs`; skip silently when both are already set.
+   - Ask (a): "Enable a session-start hook that warns when tracked skills are behind canonical?" Default **no**.
+     - If yes: run `scripts/init-agentic-skills.sh hook enable` (registers a `SessionStart` hook in `~/.claude/settings.json` invoking `scripts/skill-drift-hook.sh` and sets `skills.session_start_hook=true`).
+     - If no: run `scripts/init-agentic-skills.sh set-pref session_start_hook false`.
+   - Ask (b): "Auto-refresh latest skills on session start (instead of just warning)?" Default **no**.
+     - Run `scripts/init-agentic-skills.sh set-pref auto_refresh <true|false>` with the answer. Auto-refresh only takes effect when the hook is enabled.
+   - To disable later: decline the prompt, run `scripts/init-agentic-skills.sh set-pref session_start_hook false`, or run `scripts/init-agentic-skills.sh hook disable` to remove the settings entry.
+
+## Constraints
+
+- Delegate base initialization to `scripts/init-agentic-skills.sh`; do not recreate install logic by hand.
+- Do not overwrite real directories or files under `~/.claude/skills`, `~/.codex/skills`, `.claude/skills`, or `.codex/skills`.
+- Treat packs as project-local capabilities managed by `scripts/pack.sh` through `/pack`.
+- Stop and report exact errors if the launcher cannot resolve the repository root or if root `init.sh` fails.
+- Do not install `packs/*` as base skills in any mode.
+
+## Default Shipping Contract
+
+Follow the shared shipping contract convention in CLAUDE.md.

package/{global → base}/claude/pack/CHANGELOG.md

@@ -1,5 +1,13 @@
 # Changelog
 
+## v0.10 - 2026-06-13
+
+- Base-skill install reference updated from the retired `init.sh` to project-local `npx skillpacks init`.
+
+## v0.9 - 2026-06-13
+
+- Renamed the domain-neutral core skill set from "global" to "base" in the description and notes (these are the `init.sh`-initialized base skills).
+
 ## v0.8 - 2026-06-12
 
 - Standardized active pack and skill install guidance on `npx skillpacks install <pack-or-skill>` instead of agent-native `/pack install` or `$pack install` recommendations.