@glexcorp/gskp 0.1.1 → 0.1.2

package/docs/skillpacks-npm-distribution.md

@@ -7,7 +7,8 @@ Source alignment page: `alignment/idea-scope-brief-npm-distribution.html` (histo
 Approved decisions:
 
 - Primary path: hybrid, starting with COA A and evolving toward COA B/C only when demand justifies it.
-- Public npm/CLI name: `gskp`.
+- Primary public npm package: `skillpacks`.
+- Scoped alias npm package: `@glexcorp/gskp`.
 - Version granularity: skill-level versioning remains authoritative for user pinning.
 - Deck installation: COA B/C-shaped metadata first. Decks should be represented as curated package lists and registry tags; the initial COA A monolith may materialize those selections locally, but deck behavior should not be hard-coded as monolith-only presets.
 - Artifact route: write the detailed design doc in `docs/` first, then use it as the implementation roadmap.
@@ -19,55 +20,62 @@ Current npm check on 2026-06-12:
 - `npm view skp --json` returned an existing external package at version `1.0.0`, so `skp` should not be used.
 - `npm view gskp --json` returned `E404`, so the unscoped package name appears unclaimed or inaccessible to this machine.
 - `npm view agentic-skills --json` returned an existing external package at version `2.5.1`, so `agentic-skills` should not be used as this repo's public npm package name.
-- `npm view skillpack --json` returned an existing unrelated package at version `0.1.3`, so the old `skillpacks` spelling is too typo-adjacent for the primary route.
+- `npm view skillpack --json` returned an existing unrelated package at version `0.1.3`; warn against the singular typo, but keep `skillpacks` as the primary route because it already exists and has users.
 
-Publication status before the `gskp` rename:
+Publication status:
 
 - `skillpacks@0.1.0` and `skillpacks@0.1.1` were published publicly on npm before the short-name change.
-- The package now publishes as `gskp`, while retaining `skillpacks` as a compatibility binary in the package.
-- The next public verification target is `npx @glexcorp/gskp@latest list`, temp-project `install code-quality`, temp-project `install quality-sweep`, temp-project `install-deck game-afps`, and the git-checkout `scripts/pack.sh list` path.
+- Source package metadata is `skillpacks`.
+- Each release also publishes `@glexcorp/gskp` as a scoped alias from the same built artifact and version.
+- Both packages expose both binaries: `skillpacks` and `gskp`.
+- The public verification targets are `npx skillpacks@latest list`, `npx @glexcorp/gskp@latest list`, temp-project `install code-quality`, temp-project `install quality-sweep`, temp-project `install-deck game-afps`, and the git-checkout `scripts/pack.sh list` path.
 
 ## Product Shape
 
-`gskp` becomes the public installer and CLI for this repository's markdown skill library. The first npm release should not restructure the repository into many packages. It should package the current repository content needed to install skills and expose a Node entry point that can drive the existing install model.
+`skillpacks` is the primary public installer and CLI package for this repository's markdown skill library. `@glexcorp/gskp` is a scoped alias package for users who prefer the `gskp` identity. The first npm release should not restructure the repository into many packages. It should package the current repository content needed to install skills and expose a Node entry point that can drive the existing install model.
 
 The initial user experience should be:
 
 ```bash
-npx @glexcorp/gskp init
-npx @glexcorp/gskp install business-discovery
-npx @glexcorp/gskp install-deck vard
-npx @glexcorp/gskp status
-npx @glexcorp/gskp doctor
-npx @glexcorp/gskp refresh
+npx skillpacks init
+npx skillpacks install business-discovery
+npx skillpacks install-deck vard
+npx skillpacks status
+npx skillpacks doctor
+npx skillpacks refresh
 ```
 
-`npx @glexcorp/gskp init` installs the base skill surface into the current repository as local skill roots and records `base_skills: true` in `.agents/project.json`. This makes `npx @glexcorp/gskp refresh` update base skills from the current package snapshot instead of depending on user-home global installs.
+`npx skillpacks init` installs the base skill surface into the current repository as local skill roots and records `base_skills: true` in `.agents/project.json`. This makes `npx skillpacks refresh` update base skills from the current package snapshot. Base skills are **project-local only** — there is no user-home (global) install path.
 
-When a user explicitly wants user-home global core skills from the npm package snapshot, the compatibility path is:
+If a machine still has legacy user-home base installs from the retired init path, clean them up with:
 
 ```bash
-npx @glexcorp/gskp init --global
-# Backward-compatible spelling:
-npx @glexcorp/gskp init-global
+npx skillpacks uninstall-global
 ```
 
-Both global init forms invoke the packaged `init.sh` and keep the global surface limited to core skills. Domain packs remain project-local only.
+This removes only skillpacks-owned installs under `~/.claude/skills` and `~/.codex/skills` and leaves unmanaged directories untouched. Domain packs remain project-local only.
 
-Source-checkout users can keep using:
+Source-checkout users install base skills project-local the same way and keep using `scripts/pack.sh` for packs:
 
 ```bash
-./init.sh
+npx skillpacks init
 scripts/pack.sh install business-discovery
 scripts/pack.sh refresh
 ```
 
 The npm path is now the standard agent-facing install route. The source-checkout commands remain supported for local repository development and compatibility.
 
+Scoped alias examples are equivalent at the same package version:
+
+```bash
+npx @glexcorp/gskp init
+npx @glexcorp/gskp install business-discovery
+```
+
 ## Design Principles
 
 1. Preserve `SKILL.md` as the source format.
-2. Preserve `global/{claude,codex}` and `packs/<pack>/{claude,codex}` as the authoring layout.
+2. Preserve `base/{claude,codex}` and `packs/<pack>/{claude,codex}` as the authoring layout.
 3. Preserve `.agents/project.json` as the project designation file.
 4. Preserve `scripts/pack.sh` while the npm CLI reaches parity.
 5. Keep the first npm release as one package.
@@ -79,13 +87,13 @@ The npm path is now the standard agent-facing install route. The source-checkout
 
 ### Package
 
-The publishable npm package is named `gskp` and lives under `packages/skillpacks/`. The repository root stays private workspace metadata for the monorepo.
+The publishable npm package source is named `skillpacks` and lives under `packages/skillpacks/`. The repository root stays private workspace metadata for the monorepo. During release, `./publish.sh` stages two publish directories from `packages/skillpacks/build`: one with `package.json.name = "skillpacks"` and one with `package.json.name = "@glexcorp/gskp"`.
 
 Current package `package.json` shape:
 
 ```json
 {
-  "name": "@glexcorp/gskp",
+  "name": "skillpacks",
   "version": "0.1.0",
   "description": "CLI and packaged markdown skill library for Claude Code and OpenAI Codex.",
   "type": "module",
@@ -106,7 +114,7 @@ Current package `package.json` shape:
     "bin/",
     "src/",
     "dist/",
-    "global/",
+    "base/",
     "packs/",
     "scripts/pack.sh",
     "scripts/skill-links.sh",
@@ -117,8 +125,7 @@ Current package `package.json` shape:
     "README.md",
     "LICENSE",
     "AGENTS.md",
-    "CLAUDE.md",
-    "init.sh"
+    "CLAUDE.md"
   ],
   "license": "MIT",
   "engines": {
@@ -129,7 +136,18 @@ Current package `package.json` shape:
 
 The root `package.json` is private and declares workspaces for `apps/skills-showcase` and `packages/skillpacks`. The public package uses the repository root MIT license and npm metadata links back to `https://github.com/GeorgeQLe/agentic-skills`. The first release can keep runtime dependencies at zero. If argument parsing grows, add one small dependency later instead of pulling in a framework immediately.
 
-The `skillpacks` binary is retained as an in-package compatibility alias. It should no longer be the primary docs route because `skillpack` singular is an unrelated npm package that can catch common typos.
+Both published packages expose the same binaries:
+
+```json
+{
+  "bin": {
+    "gskp": "bin/skillpacks.mjs",
+    "skillpacks": "bin/skillpacks.mjs"
+  }
+}
+```
+
+Do not use `skillpack` singular; that is an unrelated npm package with a different project format.
 
 ### CLI Entry Point
 
@@ -146,10 +164,9 @@ The wrapper must run `scripts/pack.sh` with the user's current working directory
 
 The npm tarball must include:
 
-- `global/**` active core skills and their local archives.
+- `base/**` active core skills and their local archives.
 - `packs/**` active pack skills and their local archives.
 - `scripts/pack.sh` and script helpers it sources, especially `scripts/skill-links.sh`.
-- `init.sh` or an equivalent `init-global` implementation.
 - deck and pack docs used for help output.
 
 The package build script at `packages/skillpacks/scripts/build-package.mjs` stages these files into `packages/skillpacks/build/` before `npm pack`. The staging step must not generate or mutate Skills Showcase assets.
@@ -165,11 +182,11 @@ The tarball should exclude:
 - generated local roots under `.claude/skills` and `.codex/skills`
 - unrelated benchmark output and session artifacts
 
-Skill-level archives inside `global/**/archive/` and `packs/**/archive/` must remain included because pinning depends on them.
+Skill-level archives inside `base/**/archive/` and `packs/**/archive/` must remain included because pinning depends on them.
 
 ## CLI Surface
 
-Phase 3 compatibility decision: keep `scripts/pack.sh` as the canonical git-checkout compatibility wrapper and as the packaged shell fallback for commands that are not yet worth porting. Do not turn `pack.sh` into a thin wrapper over the Node CLI in this phase; that would make the old checkout path depend on the npm package internals before all discovery and init surfaces are ported. Revisit the decision only after `recommend`, `which`, `install-deck`, and global init behavior are either Node-owned or intentionally documented as permanent shell surfaces.
+Phase 3 compatibility decision: keep `scripts/pack.sh` as the canonical git-checkout compatibility wrapper and as the packaged shell fallback for commands that are not yet worth porting. Do not turn `pack.sh` into a thin wrapper over the Node CLI in this phase; that would make the old checkout path depend on the npm package internals before all discovery and init surfaces are ported. Revisit the decision only after `recommend`, `which`, and `install-deck` are either Node-owned or intentionally documented as permanent shell surfaces. (Base init is fully Node-owned and project-local; the user-home global init path has been retired.)
 
 <!-- gskp-compatibility-matrix:start -->
 | Command | Owner | Backend | Requires bash | Requires jq | Notes |
@@ -180,8 +197,8 @@ Phase 3 compatibility decision: keep `scripts/pack.sh` as the canonical git-chec
 | `status` | Node-owned | Project config/status reader | No | No | Reports project designation and local roots. |
 | `set-mode <mode>` | Node-owned | Project config writer | No | No | Preserves unrelated fields and uses the Node lock helper. |
 | `set-update-mode <mode>` | Node-owned | Project config writer | No | No | Preserves sibling `skill_updates` fields. |
-| `init` | Node-owned | Manifest plus lifecycle helpers | No | No | Installs global-scope manifest entries as project-local base skills and records `base_skills: true`. |
-| `init --global [args...]` | External script-backed | Packaged `init.sh` | Yes | Optional | Installs user-home global core skills from the package snapshot; strips `--global` and forwards remaining args to `init.sh`. |
+| `init` | Node-owned | Manifest plus lifecycle helpers | No | No | Installs base-scope manifest entries as project-local base skills and records `base_skills: true`. |
+| `uninstall-global` | Node-owned | Managed marker ownership reader | No | No | Removes legacy skillpacks-owned base installs from `~/.claude/skills` and `~/.codex/skills`; leaves unmanaged directories untouched. |
 | `install <name...>` | Node-owned | Manifest plus lifecycle helpers | No | No | Handles active packs, active skills, aliases, hibernated diagnostics, markers, hashes, and project config writes. |
 | `remove <name...>` | Node-owned | Manifest plus lifecycle helpers | No | No | Handles active pack removal, individual skill removal, and hibernated stale cleanup. |
 | `refresh` | Node-owned | Manifest plus lifecycle helpers | No | No | Recreates enabled base skills, packs, and individual skill roots from `.agents/project.json`. |
@@ -199,7 +216,6 @@ Phase 3 compatibility decision: keep `scripts/pack.sh` as the canonical git-chec
 | `recommend` | Shell-backed | Packaged `scripts/pack.sh recommend` | Yes | No | Uses existing repository-signal heuristics. |
 | `which <skill>` | Shell-backed | Packaged `scripts/pack.sh which` | Yes | Optional | `jq` improves individually enabled skill status; pack-level status has a grep/sed fallback. |
 | `install-deck <deck> [--full]` | Hybrid shell materialization | Node manifest resolver, then packaged `scripts/pack.sh install` | Yes | Yes | Deck metadata is Node-resolved, but installation still uses the compatibility install path. |
-| `init-global [args...]` | External script-backed | Packaged `init.sh` | Yes | Optional | Backward-compatible alias for `init --global`; `jq` preserves an existing global pin file when `--pin` updates it. |
 <!-- gskp-compatibility-matrix:end -->
 
 The CLI should print the same reload notice as `pack.sh` after install, remove, refresh, pin, and unpin.
@@ -251,7 +267,7 @@ Proposed shape:
   "schema_version": 1,
   "generated_at": "2026-06-08T00:00:00Z",
   "package": {
-    "name": "@glexcorp/gskp",
+    "name": "skillpacks",
     "version": "0.1.0"
   },
   "packs": [
@@ -310,7 +326,7 @@ Manifest consumers:
 
 There are two version layers:
 
-1. npm package semver, such as `@glexcorp/gskp@0.1.0`.
+1. npm package semver, such as `skillpacks@0.1.0`.
 2. skill frontmatter versions, such as `version: v0.4`.
 
 The approved granularity is skill-level, so skill frontmatter remains the user-facing pinning level. npm package semver is the transport snapshot.
@@ -318,14 +334,14 @@ The approved granularity is skill-level, so skill frontmatter remains the user-f
 User examples:
 
 ```bash
-npx @glexcorp/gskp@0.1.0 install business-discovery
-npx @glexcorp/gskp pin devtool-adoption v0.0
-npx @glexcorp/gskp doctor
+npx skillpacks@0.1.0 install business-discovery
+npx skillpacks pin devtool-adoption v0.0
+npx skillpacks doctor
 ```
 
 Important consequences:
 
-- `@glexcorp/gskp@0.1.0` determines which skill archive snapshots are available locally.
+- `skillpacks@0.1.0` determines which skill archive snapshots are available locally.
 - `pinned_versions` in `.agents/project.json` continues to select `archive/<version>/SKILL.md` inside the installed package.
 - A user who needs a skill archive not present in their installed npm package must upgrade the npm package or use the git checkout model.
 - Package releases should be cut after one or more skill changes are complete and verified; they should not require every edited skill to share a new npm version internally.
@@ -334,7 +350,7 @@ Important consequences:
 
 Phase 1 must not change these contracts:
 
-- `./init.sh` remains valid for local checkout users.
+- `npx skillpacks init` installs project-local base skills for both checkout and npm users.
 - `scripts/pack.sh` remains valid for local checkout users.
 - `.agents/project.json` keeps `project_type`, `enabled_packs`, `enabled_skills`, `pinned_versions`, `skill_updates`, `project_scopes`, `notes`, and `agent_mode`.
 - Generated `.claude/skills` and `.codex/skills` roots remain uncommitted consumer-project artifacts.
@@ -344,7 +360,7 @@ After the Phase 3 port, `scripts/pack.sh` remains a supported compatibility wrap
 
 ## Phase 4 Release-Readiness Notes
 
-Phase 4 prepares the package for a dry-run release only. It does not publish `gskp`, create npm tags, change package access, or replace the source-checkout setup path.
+Phase 4 prepares the package for a dry-run release only. It does not publish packages, create npm tags, change package access, or replace the source-checkout setup path.
 
 ### User Setup Paths
 
@@ -361,10 +377,10 @@ With the published npm package, npm users can install from the target project di
 
 ```bash
 cd ~/my-project
-npx @glexcorp/gskp install devtool
-npx @glexcorp/gskp install code-quality
-npx @glexcorp/gskp install-deck game-afps
-npx @glexcorp/gskp status
+npx skillpacks install devtool
+npx skillpacks install code-quality
+npx skillpacks install-deck game-afps
+npx skillpacks status
 ```
 
 Both paths write the same project-local contract: `.agents/project.json`, `.claude/skills/*`, and `.codex/skills/*`. The CLI session reload requirements are unchanged: Claude Code needs `/reload-skills`, `/clear`, or a restart depending on when the local roots appeared; Codex needs a fresh session if the `$` skill list remains stale.
@@ -374,8 +390,8 @@ Both paths write the same project-local contract: `.agents/project.json`, `.clau
 An existing project can move from a local checkout workflow to the npm package by keeping `.agents/project.json` committed and running:
 
 ```bash
-npx @glexcorp/gskp refresh
-npx @glexcorp/gskp doctor
+npx skillpacks refresh
+npx skillpacks doctor
 ```
 
 `refresh` recreates generated local skill roots from the package snapshot and the existing project designation. `doctor` then reports whether managed installs are current, stale, missing, unknown, or pinned.
@@ -384,18 +400,18 @@ Do not commit generated `.claude/skills/*` or `.codex/skills/*` roots during mig
 
 ### Version And Pinning Troubleshooting
 
-`@glexcorp/gskp@<semver>` is the transport snapshot. It determines which active skill files and `archive/<version>/SKILL.md` snapshots are present in the installed package.
+`skillpacks@<semver>` is the transport snapshot. It determines which active skill files and `archive/<version>/SKILL.md` snapshots are present in the installed package.
 
 Skill pins still use skill frontmatter versions:
 
 ```bash
-npx @glexcorp/gskp pin quality-sweep v0.0
-npx @glexcorp/gskp unpin quality-sweep
+npx skillpacks pin quality-sweep v0.0
+npx skillpacks unpin quality-sweep
 ```
 
 If a pin fails because an archive version is unavailable, the installed npm package does not contain that archived skill snapshot. Upgrade to a package version that includes the archive, or use a source checkout at a commit that contains it.
 
-Node-owned npm commands (`install`, `remove`, `refresh`, `doctor`, `prune`, `pin`, `unpin`, `status`, `list-packs`, `set-mode`, and `set-update-mode`) do not require `jq`. In the current `@glexcorp/gskp@0.1.0` release, `install-deck` still materializes through the packaged shell backend and therefore requires both `bash` and `jq`.
+Node-owned npm commands (`install`, `remove`, `refresh`, `doctor`, `prune`, `pin`, `unpin`, `status`, `list-packs`, `set-mode`, and `set-update-mode`) do not require `jq`. In the current `skillpacks@0.1.0` release, `install-deck` still materializes through the packaged shell backend and therefore requires both `bash` and `jq`.
 
 ### Alignment Convention Commands
 
@@ -410,14 +426,47 @@ node scripts/inject-tts.mjs --force alignment/example.html
 npm users can run the equivalent wrapped commands from the target repository:
 
 ```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
 ```
 
 The namespace keeps the two alignment workflows separate. `alignment bundles` generates or checks the bundled per-skill convention files (`ALIGNMENT-PAGE.md`) from `docs/alignment-page-convention.md`; `alignment pages audit` checks already-rendered active `alignment/*.html` pages. `alignment pages inject-tts` copies the packaged `scripts/alignment-tts-kokoro.js` asset into the target repo when needed before adding the script tag. `alignment verify` is mainly for this source checkout and exits with a clear message when a consumer repo does not include the focused alignment Vitest files.
 
+## Publishing
+
+Do not publish manually from `packages/skillpacks/build`. That directory is an intermediate source-package build, not the dual-package release boundary.
+
+Use the root release script:
+
+```bash
+./publish.sh patch
+./publish.sh minor
+./publish.sh 0.1.2
+./publish.sh --dry-run patch
+```
+
+Release rules:
+
+- The script requires a clean git working tree before it starts.
+- It bumps `packages/skillpacks/package.json` with `npm --workspace packages/skillpacks version <target> --no-git-tag-version`.
+- It runs `npm --workspace packages/skillpacks run test:node` and `npm run skillpacks:verify` before staging publish directories.
+- It stages two packages under `/tmp`, both generated from `packages/skillpacks/build`.
+- The staged `skillpacks` package and staged `@glexcorp/gskp` package must have identical versions and identical `bin` mappings.
+- It runs `scripts/prepublish-auth-check.mjs` inside each staged package before a real publish.
+- It publishes `skillpacks` first, then `@glexcorp/gskp --access public`.
+- It verifies both published package specs after a real publish.
+
+Every npm publish requires a new version. `skillpacks` and `@glexcorp/gskp` versions must stay identical.
+
+After a real publish, verification can also be run directly:
+
+```bash
+SKILLPACKS_PACKAGE_NAME=skillpacks SKILLPACKS_NPM_SPEC=skillpacks@latest npm run skillpacks:verify-published
+SKILLPACKS_PACKAGE_NAME=@glexcorp/gskp SKILLPACKS_NPM_SPEC=@glexcorp/gskp@latest npm run skillpacks:verify-published
+```
+
 ## Implementation Roadmap
 
 ### Phase 0 - Reservation And Preflight
@@ -426,8 +475,8 @@ Goal: prove the public name and package boundary before code changes.
 
 Tasks:
 
-- Confirm npm account access for publishing `gskp`.
-- Reserve or create the `@gskp` npm organization if future scoped packages are desired.
+- Confirm npm account access for publishing `skillpacks` and `@glexcorp/gskp`.
+- Reserve or create future pack scopes only if demand justifies package splitting.
 - Decide whether the first release should be private dry-run only or public `0.1.0`.
 - Confirm MIT license metadata and npm repository/bugs/homepage links.
 - Confirm `jq` remains a documented dependency for write commands in phase 1.
@@ -435,7 +484,7 @@ Tasks:
 
 Exit criteria:
 
-- `gskp` publish rights are confirmed.
+- `skillpacks` and `@glexcorp/gskp` publish rights are confirmed.
 - Package name collision risk is closed.
 - Tarball content policy is documented and testable.
 
@@ -445,11 +494,11 @@ Goal: publishable monolith package that delegates to current scripts.
 
 Tasks:
 
-- Add `packages/skillpacks/package.json` for `gskp`.
+- Add `packages/skillpacks/package.json` for `skillpacks`.
 - Add `packages/skillpacks/bin/skillpacks.mjs`.
 - Add `packages/skillpacks/src/cli/run-pack-script.mjs` or equivalent script dispatcher.
 - Implement command forwarding for existing `pack.sh` commands.
-- Implement `init-global` by invoking included `init.sh` or a small Node equivalent.
+- Implement project-local base `init` as a Node lifecycle helper.
 - Preserve cwd as the consumer project root for all project-local writes.
 - Add dependency checks for `bash` and `jq` with actionable messages.
 - Add package staging and `npm pack packages/skillpacks/build --dry-run --json --silent` verification.
@@ -513,7 +562,7 @@ Goal: prepare users for npm install without changing the old setup path.
 
 Tasks:
 
-- Update `README.md` with `npx @glexcorp/gskp` usage.
+- Update `README.md` with `npx skillpacks` usage.
 - Update `docs/QUICKSTART.md`, `docs/packs.md`, and `docs/decks.md`.
 - Add a migration note for users moving from git checkout to npm.
 - Add troubleshooting for npm package version vs skill-level pinning.
@@ -534,14 +583,14 @@ Tasks:
 
 - Verify working tree is clean except intended release changes.
 - Run package tests, tarball validation, and package metadata checks.
-- Run `npm publish --access public`.
-- Verify `npx @glexcorp/gskp@latest list` against the published package.
+- Run `./publish.sh patch` or another explicit version target.
+- Verify `npx skillpacks@latest list` and `npx @glexcorp/gskp@latest list` against the published packages.
 - Install into a fresh temp repo and verify one pack, one individual skill, and one deck.
 - Commit and push release docs and any package version changes.
 
 Exit criteria:
 
-- `gskp` is installable from npm.
+- `skillpacks` and `@glexcorp/gskp` are installable from npm at the same version.
 - A fresh project can install packs without cloning this repository.
 - Current git-checkout install path remains functional.
 
@@ -553,7 +602,7 @@ Tasks:
 
 - Track install usage and maintenance pain from the monolith package.
 - Identify "hot packs" that deserve scoped packages.
-- Use manifest data to generate `@gskp/<pack>` package metadata experimentally.
+- Use manifest data to generate future scoped pack package metadata experimentally.
 - Use deck package-list metadata to generate scoped package recommendations.
 - Use registry-style deck tags to support per-skill and category resolution.
 - Consider `@gskp/sdk` only after the manifest is stable and used by the CLI.
@@ -598,9 +647,9 @@ node /path/to/agentic-skills/packages/skillpacks/bin/skillpacks.mjs pin quality-
 Published-package checks:
 
 ```bash
-npx @glexcorp/gskp@latest list
-npx @glexcorp/gskp@latest install-deck ord
-npx @glexcorp/gskp@latest doctor
+npx skillpacks@latest list
+npx skillpacks@latest install-deck ord
+npx skillpacks@latest doctor
 ```
 
 ## Risks And Mitigations
@@ -611,8 +660,8 @@ npx @glexcorp/gskp@latest doctor
 | npm package accidentally includes task/history/prompt artifacts | Bloated or sensitive package | Use `files` whitelist plus `npm pack --dry-run` validation. |
 | `pack.sh` assumes a git checkout | npm install breaks | Run it from the packaged script path and add temp-repo tests. |
 | `jq` is missing | Shell-backed write paths fail | Node-owned `gskp` project commands no longer require `jq`; keep `jq` documented for git-checkout `scripts/pack.sh` write commands and `gskp install-deck` materialization. |
-| Skill-level pinning needs archives omitted from tarball | Pins break | Include skill-local `archive/**` while excluding global docs history. |
-| Existing git-checkout users regress | Adoption risk | Keep `init.sh` and `pack.sh` unchanged until Node parity is proven. |
+| Skill-level pinning needs archives omitted from tarball | Pins break | Include skill-local `archive/**` while excluding repo-wide docs history. |
+| Existing git-checkout users regress | Adoption risk | Keep `pack.sh` unchanged until Node parity is proven; base init is Node-owned and project-local via `npx skillpacks init`. |
 | CLI name conflicts with installed external `agentic-skills` package | User confusion | Use `gskp` as the only npm package and bin name. |
 
 ## Open Questions
@@ -621,7 +670,6 @@ These should be answered before first publish, not before starting phase 1:
 
 - Is `gskp` the final npm package owner identity, or should the public package be `@gskp/cli` after an organization is created?
 - Should `install-deck` remain a hybrid shell materialization path for the first public package, or should deck installation move fully to Node before publish?
-- Should `init-global` install only global core skills, or should it also offer an optional deck picker?
 - Should hibernated packs be excluded from the npm tarball entirely or included only to preserve explicit error messages?
 - Should package releases use `0.x` until several real consumer installs pass?
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@glexcorp/gskp",
-  "version": "0.1.1",
+  "version": "0.1.2",
   "description": "CLI and packaged markdown skill library for Claude Code and OpenAI Codex.",
   "type": "module",
   "bin": {
@@ -20,7 +20,7 @@
     "bin/",
     "src/",
     "dist/",
-    "global/",
+    "base/",
     "packs/",
     "scripts/pack.sh",
     "scripts/skill-links.sh",
@@ -40,8 +40,7 @@
     "README.md",
     "LICENSE",
     "AGENTS.md",
-    "CLAUDE.md",
-    "init.sh"
+    "CLAUDE.md"
   ],
   "keywords": [
     "ai",

package/packs/alignment-page-admin/claude/upgrade-alignment-pages/SKILL.md

@@ -33,7 +33,7 @@ Use this skill when a repository already has generated `alignment/*.html` review
    - If the user provided page paths, include only those paths after confirming they are inside the project-root `alignment/` directory.
 
 2. Load local standards:
-   - Read applicable local convention sources from `AGENTS.md`, `CLAUDE.md`, and active bundled `ALIGNMENT-PAGE.md` files found under `global/`, `packs/`, `.claude/skills/`, and `.codex/skills/`.
+   - Read applicable local convention sources from `AGENTS.md`, `CLAUDE.md`, and active bundled `ALIGNMENT-PAGE.md` files found under `base/`, `packs/`, `.claude/skills/`, and `.codex/skills/`.
    - Treat those local files as read-only standards. Do not fetch external standards.
    - Extract the current required HTML behaviors: dark-mode styling, inline approval gates, section feedback controls, local section feedback YAML, unified response YAML, copy fallback behavior, unanswered-question handling, archive-before-replace behavior, and diff/change highlighting for updates.
 

package/packs/alignment-page-admin/codex/upgrade-alignment-pages/SKILL.md

@@ -33,7 +33,7 @@ Use this skill when a repository already has generated `alignment/*.html` review
    - If the user provided page paths, include only those paths after confirming they are inside the project-root `alignment/` directory.
 
 2. Load local standards:
-   - Read applicable local convention sources from `AGENTS.md`, `CLAUDE.md`, and active bundled `ALIGNMENT-PAGE.md` files found under `global/`, `packs/`, `.claude/skills/`, and `.codex/skills/`.
+   - Read applicable local convention sources from `AGENTS.md`, `CLAUDE.md`, and active bundled `ALIGNMENT-PAGE.md` files found under `base/`, `packs/`, `.claude/skills/`, and `.codex/skills/`.
    - Treat those local files as read-only standards. Do not fetch external standards.
    - Extract the current required HTML behaviors: dark-mode styling, inline approval gates, section feedback controls, local section feedback YAML, unified response YAML, copy fallback behavior, unanswered-question handling, archive-before-replace behavior, and diff/change highlighting for updates.
 

package/packs/docs-health/claude/hygiene/SKILL.md

@@ -23,7 +23,7 @@ Read `CLAUDE.md` for project conventions. Read `docs/skills-reference.md` for th
 
 ### 2. Audit Skills (`skills` scope)
 
-For each skill directory in `global/claude/*/SKILL.md`, `global/codex/*/SKILL.md`, `packs/*/claude/*/SKILL.md`, and `packs/*/codex/*/SKILL.md`:
+For each skill directory in `base/claude/*/SKILL.md`, `base/codex/*/SKILL.md`, `packs/*/claude/*/SKILL.md`, and `packs/*/codex/*/SKILL.md`:
 
 **Frontmatter check:**
 - Has `name` field — matches directory name
@@ -71,9 +71,9 @@ Check expected project files exist based on project phase:
 ### 4. Audit Docs (`docs` scope)
 
 **Skills reference sync:**
-- Every global core directory has a corresponding entry in `docs/skills-reference.md`
+- Every base core directory has a corresponding entry in `docs/skills-reference.md`
 - Every pack directory is listed under its pack in `docs/skills-reference.md`
-- The global core table and pack skill lists are complete (no missing, no extras)
+- The base core table and pack skill lists are complete (no missing, no extras)
 
 **Required docs:**
 - `CLAUDE.md` exists at project root
@@ -124,7 +124,7 @@ Check expected project files exist based on project phase:
 
 Compare Claude and Codex directories within each root:
 
-- Every skill in `global/claude/` should have a corresponding `global/codex/<name>/SKILL.md`
+- Every skill in `base/claude/` should have a corresponding `base/codex/<name>/SKILL.md`
 - Every skill in `packs/<pack>/claude/` should have a corresponding `packs/<pack>/codex/<name>/SKILL.md`
 - Flag skills that exist in one but not the other
 - For skills that exist in both, check that the codex version has:
@@ -157,7 +157,7 @@ Only fix mechanical, unambiguous issues:
 - Add missing `argument-hint:` field (empty) to frontmatter
 - Fix `name` field to match directory name
 - Create missing Codex mirror in the matching root from the Claude version (copy frontmatter + intro, add TODO for Codex-specific content)
-- Add missing skill entries to the appropriate global core table or pack list in `docs/skills-reference.md`
+- Add missing skill entries to the appropriate base core table or pack list in `docs/skills-reference.md`
 - Add missing empty metadata scaffold only when the target generated-doc template explicitly requires metadata and the values can be left blank
 - Normalize duplicate blank lines around headings in generated docs when it is purely mechanical
 
@@ -178,16 +178,16 @@ Display directly to the user (no files written in audit mode):
 ## Hygiene Report — [scope]
 
 ### Errors (X)
-- **global/claude/foo/SKILL.md** — missing `version` field in frontmatter
+- **base/claude/foo/SKILL.md** — missing `version` field in frontmatter
 - **packs/business-discovery/claude/bar/SKILL.md** — directory name `bar` doesn't match frontmatter name `baz`
 
 ### Warnings (X)
 - **packs/example-pack/codex/example-skill/** — missing Codex mirror (exists in Claude only)
-- **docs/skills-reference.md** — `/hygiene` not listed in the global core table
+- **docs/skills-reference.md** — `/hygiene` not listed in the base core table
 - **research/icp.md** — missing `## Next Steps` section required by the research doc template
 
 ### Info (X)
-- **global/claude/ship/SKILL.md** — no `## Constraints` section (consider adding)
+- **base/claude/ship/SKILL.md** — no `## Constraints` section (consider adding)
 - **docs/architecture.md** — unknown hand-written doc; skipped strict generated-doc template checks
 
 ### Summary
@@ -201,8 +201,8 @@ In `fix` mode, prepend each fixed item with a checkmark:
 
 ```
 ### Fixed
-- [x] Added missing `argument-hint:` to global/claude/foo/SKILL.md
-- [x] Created mirror global/codex/hygiene/SKILL.md
+- [x] Added missing `argument-hint:` to base/claude/foo/SKILL.md
+- [x] Created mirror base/codex/hygiene/SKILL.md
 
 ### Remaining Errors (X)
 ...

package/packs/docs-health/codex/hygiene/SKILL.md

@@ -23,7 +23,7 @@ Read `CLAUDE.md` for project conventions. Read `docs/skills-reference.md` for th
 
 ### 2. Audit Skills (`skills` scope)
 
-For each skill directory in `global/claude/*/SKILL.md`, `global/codex/*/SKILL.md`, `packs/*/claude/*/SKILL.md`, and `packs/*/codex/*/SKILL.md`:
+For each skill directory in `base/claude/*/SKILL.md`, `base/codex/*/SKILL.md`, `packs/*/claude/*/SKILL.md`, and `packs/*/codex/*/SKILL.md`:
 
 **Frontmatter check:**
 - Has `name` field — matches directory name
@@ -72,9 +72,9 @@ Check expected project files exist based on project phase:
 ### 4. Audit Docs (`docs` scope)
 
 **Skills reference sync:**
-- Every global core directory has a corresponding entry in `docs/skills-reference.md`
+- Every base core directory has a corresponding entry in `docs/skills-reference.md`
 - Every pack directory is listed under its pack in `docs/skills-reference.md`
-- The global core table and pack skill lists are complete (no missing, no extras)
+- The base core table and pack skill lists are complete (no missing, no extras)
 
 **Required docs:**
 - `CLAUDE.md` exists at project root
@@ -125,7 +125,7 @@ Check expected project files exist based on project phase:
 
 Compare Claude and Codex directories within each root:
 
-- Every skill in `global/claude/` should have a corresponding `global/codex/<name>/SKILL.md`
+- Every skill in `base/claude/` should have a corresponding `base/codex/<name>/SKILL.md`
 - Every skill in `packs/<pack>/claude/` should have a corresponding `packs/<pack>/codex/<name>/SKILL.md`
 - Flag skills that exist in one but not the other
 - For skills that exist in both, check that the codex version has:
@@ -158,7 +158,7 @@ Only fix mechanical, unambiguous issues:
 - Add missing `argument-hint:` field (empty) to frontmatter
 - Fix `name` field to match directory name
 - Create missing Codex mirror in the matching root from the Claude version (copy frontmatter + intro, add TODO for Codex-specific content)
-- Add missing skill entries to the appropriate global core table or pack list in `docs/skills-reference.md`
+- Add missing skill entries to the appropriate base core table or pack list in `docs/skills-reference.md`
 - Add missing empty metadata scaffold only when the target generated-doc template explicitly requires metadata and the values can be left blank
 - Normalize duplicate blank lines around headings in generated docs when it is purely mechanical
 
@@ -179,16 +179,16 @@ Display directly to the user (no files written in audit mode):
 ## Hygiene Report — [scope]
 
 ### Errors (X)
-- **global/claude/foo/SKILL.md** — missing `version` field in frontmatter
+- **base/claude/foo/SKILL.md** — missing `version` field in frontmatter
 - **packs/business-discovery/claude/bar/SKILL.md** — directory name `bar` doesn't match frontmatter name `baz`
 
 ### Warnings (X)
 - **packs/example-pack/codex/example-skill/** — missing Codex mirror (exists in Claude only)
-- **docs/skills-reference.md** — `$hygiene` not listed in the global core table
+- **docs/skills-reference.md** — `$hygiene` not listed in the base core table
 - **research/icp.md** — missing `## Next Steps` section required by the research doc template
 
 ### Info (X)
-- **global/claude/ship/SKILL.md** — no `## Constraints` section (consider adding)
+- **base/claude/ship/SKILL.md** — no `## Constraints` section (consider adding)
 - **docs/architecture.md** — unknown hand-written doc; skipped strict generated-doc template checks
 
 ### Summary
@@ -202,8 +202,8 @@ In `fix` mode, prepend each fixed item with a checkmark:
 
 ```
 ### Fixed
-- [x] Added missing `argument-hint:` to global/claude/foo/SKILL.md
-- [x] Created mirror global/codex/hygiene/SKILL.md
+- [x] Added missing `argument-hint:` to base/claude/foo/SKILL.md
+- [x] Created mirror base/codex/hygiene/SKILL.md
 
 ### Remaining Errors (X)
 ...