@glexcorp/gskp 0.1.1 → 0.1.2

package/packs/skill-dev/claude/create-agentic-skill/archive/v0.1/SKILL.md

@@ -0,0 +1,91 @@
+---
+name: create-agentic-skill
+description: Create or update a repo-managed skill inside this agentic-skills checkout under global/claude and optionally global/codex, then validate, commit, and push it
+type: execution
+version: v0.1
+argument-hint: <skill-name> [description] [--claude-only|--codex-only|--mirror]
+---
+
+# Create Agentic Skill
+
+Use this skill when the user wants to add or update a skill in the `agentic-skills` repository itself. This is the repo-managed counterpart to `create-local-skill`, which writes experimental user-local skills under `~/.claude/skills` or `~/.codex/skills`.
+
+## Process
+
+1. **Confirm repository context.**
+   - Verify the current repo is `agentic-skills` by checking for `init.sh`, `global/claude/`, and `global/codex/`.
+   - If the current repo is not `agentic-skills`, stop and ask for the checkout path.
+   - Inspect `git status --short` and identify unrelated dirty files before editing.
+
+2. **Resolve skill identity.**
+   - Parse `<skill-name>` as kebab-case.
+   - Parse the description when provided; otherwise ask for a one-line description.
+   - Default to creating both `global/claude/<skill-name>/SKILL.md` and `global/codex/<skill-name>/SKILL.md` when the skill should exist for both agents.
+   - Honor `--claude-only`, `--codex-only`, or `--mirror`.
+   - If a local-only workflow is requested, route to `create-local-skill` instead.
+
+3. **Check for conflicts.**
+   - Refuse to overwrite an existing unrelated skill without explicit user approval.
+   - If updating an existing skill, read the current `SKILL.md` and preserve its purpose unless the user asked for a rewrite.
+   - Check for stale old names when the task is a rename, and move directories rather than duplicating the skill.
+
+4. **Draft the skill.**
+   - Follow repo frontmatter conventions:
+     - `name`
+     - `description`
+     - `type`
+     - `version`
+     - optional `argument-hint`
+   - For Claude skills, use `## Process` when that matches existing Claude conventions.
+   - For mirrored Codex skills, include `Invoke as \`$<skill-name>\`.` after the title.
+   - Include clear workflow/process, output, and constraints sections.
+   - Prefer durable procedure over one-off project notes.
+
+5. **Apply correction lessons when relevant.**
+   - If the skill is being created because of a user correction, update `tasks/lessons.md` with the mistake pattern and prevention rule.
+   - Keep the lesson specific enough to prevent recurrence.
+
+6. **Handle benchmark coverage.**
+   - For every new shared skill or material behavior update, update `tests/harness/bench-coverage.ts` in the same shipping boundary.
+   - Add or register a deterministic custom setup under `tests/layer4/setups/` when local fixtures can exercise the skill without credentials, external services, paid actions, production deploys, or unsafe account state.
+   - When adding or materially updating a custom setup, include a deterministic quality rubric when practical. Score local fixture facts, concrete file/command references, expected next-route handoffs, specificity, and forbidden fabrications as appropriate for the skill.
+   - If output quality cannot be scored reliably from local fixtures, record an explicit blocked/deferred quality note in the setup or coverage review instead of adding a weak subjective rubric.
+   - If deterministic local coverage is not safe yet, record an explicit `blocked` row with `blocked_reason` and `next_command`.
+   - Use `/targeted-skill-builder <skill-name> benchmark coverage` when the coverage work needs a focused follow-up before the skill can ship.
+   - Run `pnpm --dir tests bench:coverage` after updating the matrix.
+
+7. **Validate.**
+   - Read back the new or updated `SKILL.md` files.
+   - Run search checks for old skill names, missing `version:`, missing Codex invocation lines in Codex skills, and accidental writes under `~/.claude/skills` or `~/.codex/skills`.
+   - Run `pnpm --dir tests bench:coverage` and any focused setup tests changed for the new benchmark row.
+   - If any tracked `SKILL.md` or `PACK.md` was created, deleted, renamed, or changed in behavior or metadata, refresh the Skills Showcase data before shipping:
+     - `node apps/skills-showcase/scripts/generate-skills-showcase-data.mjs`
+     - `node apps/skills-showcase/scripts/generate-skills-showcase-github-data.mjs`
+     - `apps/skills-showcase/scripts/validate-skills-showcase-data.sh`
+   - Review curated showcase copy, catalog grouping, workflow animation text, and proof receipts when the skill change could affect the public website. Update the relevant site files or explicitly record why no curated website copy changed.
+   - Confirm unrelated dirty files remain unstaged.
+
+8. **Commit and push.**
+   - Stage only intended repo-managed skill files, generated showcase assets, and directly related docs or lesson updates.
+   - Commit on the repository primary branch (`main` when present, otherwise `master`) with a concise conventional commit message.
+   - Push the branch.
+   - Do not stage unrelated user changes.
+
+## Output
+
+- **Skill**: name and target paths created or updated
+- **Mode**: Claude, Codex, or mirrored
+- **Validation**: checks run and result
+- **Git**: commit hash and pushed branch
+- **Next Work**: exact follow-up, or `none` only when there is no useful follow-up
+
+## Constraints
+
+- Do not write to `~/.claude/skills` or `~/.codex/skills`; that is `create-local-skill`.
+- Do not update README or generated references when they already have unrelated unstaged edits unless the user explicitly asks to include them.
+- Do not create pack-local skills unless the user asks for a pack path.
+- Do not leave repo-managed skill changes uncommitted or unpushed unless the user explicitly says not to ship.
+
+## Default Shipping Contract
+
+Follow the shared shipping contract convention in CLAUDE.md.

package/packs/skill-dev/claude/create-agentic-skill/archive/v0.2/SKILL.md

@@ -0,0 +1,91 @@
+---
+name: create-agentic-skill
+description: Create or update a repo-managed skill inside this agentic-skills checkout under base/claude and optionally base/codex, then validate, commit, and push it
+type: execution
+version: v0.2
+argument-hint: <skill-name> [description] [--claude-only|--codex-only|--mirror]
+---
+
+# Create Agentic Skill
+
+Use this skill when the user wants to add or update a skill in the `agentic-skills` repository itself. This is the repo-managed counterpart to `create-local-skill`, which writes experimental user-local skills under `~/.claude/skills` or `~/.codex/skills`.
+
+## Process
+
+1. **Confirm repository context.**
+   - Verify the current repo is `agentic-skills` by checking for `init.sh`, `base/claude/`, and `base/codex/`.
+   - If the current repo is not `agentic-skills`, stop and ask for the checkout path.
+   - Inspect `git status --short` and identify unrelated dirty files before editing.
+
+2. **Resolve skill identity.**
+   - Parse `<skill-name>` as kebab-case.
+   - Parse the description when provided; otherwise ask for a one-line description.
+   - Default to creating both `base/claude/<skill-name>/SKILL.md` and `base/codex/<skill-name>/SKILL.md` when the skill should exist for both agents.
+   - Honor `--claude-only`, `--codex-only`, or `--mirror`.
+   - If a local-only workflow is requested, route to `create-local-skill` instead.
+
+3. **Check for conflicts.**
+   - Refuse to overwrite an existing unrelated skill without explicit user approval.
+   - If updating an existing skill, read the current `SKILL.md` and preserve its purpose unless the user asked for a rewrite.
+   - Check for stale old names when the task is a rename, and move directories rather than duplicating the skill.
+
+4. **Draft the skill.**
+   - Follow repo frontmatter conventions:
+     - `name`
+     - `description`
+     - `type`
+     - `version`
+     - optional `argument-hint`
+   - For Claude skills, use `## Process` when that matches existing Claude conventions.
+   - For mirrored Codex skills, include `Invoke as \`$<skill-name>\`.` after the title.
+   - Include clear workflow/process, output, and constraints sections.
+   - Prefer durable procedure over one-off project notes.
+
+5. **Apply correction lessons when relevant.**
+   - If the skill is being created because of a user correction, update `tasks/lessons.md` with the mistake pattern and prevention rule.
+   - Keep the lesson specific enough to prevent recurrence.
+
+6. **Handle benchmark coverage.**
+   - For every new shared skill or material behavior update, update `tests/harness/bench-coverage.ts` in the same shipping boundary.
+   - Add or register a deterministic custom setup under `tests/layer4/setups/` when local fixtures can exercise the skill without credentials, external services, paid actions, production deploys, or unsafe account state.
+   - When adding or materially updating a custom setup, include a deterministic quality rubric when practical. Score local fixture facts, concrete file/command references, expected next-route handoffs, specificity, and forbidden fabrications as appropriate for the skill.
+   - If output quality cannot be scored reliably from local fixtures, record an explicit blocked/deferred quality note in the setup or coverage review instead of adding a weak subjective rubric.
+   - If deterministic local coverage is not safe yet, record an explicit `blocked` row with `blocked_reason` and `next_command`.
+   - Use `/targeted-skill-builder <skill-name> benchmark coverage` when the coverage work needs a focused follow-up before the skill can ship.
+   - Run `pnpm --dir tests bench:coverage` after updating the matrix.
+
+7. **Validate.**
+   - Read back the new or updated `SKILL.md` files.
+   - Run search checks for old skill names, missing `version:`, missing Codex invocation lines in Codex skills, and accidental writes under `~/.claude/skills` or `~/.codex/skills`.
+   - Run `pnpm --dir tests bench:coverage` and any focused setup tests changed for the new benchmark row.
+   - If any tracked `SKILL.md` or `PACK.md` was created, deleted, renamed, or changed in behavior or metadata, refresh the Skills Showcase data before shipping:
+     - `node apps/skills-showcase/scripts/generate-skills-showcase-data.mjs`
+     - `node apps/skills-showcase/scripts/generate-skills-showcase-github-data.mjs`
+     - `apps/skills-showcase/scripts/validate-skills-showcase-data.sh`
+   - Review curated showcase copy, catalog grouping, workflow animation text, and proof receipts when the skill change could affect the public website. Update the relevant site files or explicitly record why no curated website copy changed.
+   - Confirm unrelated dirty files remain unstaged.
+
+8. **Commit and push.**
+   - Stage only intended repo-managed skill files, generated showcase assets, and directly related docs or lesson updates.
+   - Commit on the repository primary branch (`main` when present, otherwise `master`) with a concise conventional commit message.
+   - Push the branch.
+   - Do not stage unrelated user changes.
+
+## Output
+
+- **Skill**: name and target paths created or updated
+- **Mode**: Claude, Codex, or mirrored
+- **Validation**: checks run and result
+- **Git**: commit hash and pushed branch
+- **Next Work**: exact follow-up, or `none` only when there is no useful follow-up
+
+## Constraints
+
+- Do not write to `~/.claude/skills` or `~/.codex/skills`; that is `create-local-skill`.
+- Do not update README or generated references when they already have unrelated unstaged edits unless the user explicitly asks to include them.
+- Do not create pack-local skills unless the user asks for a pack path.
+- Do not leave repo-managed skill changes uncommitted or unpushed unless the user explicitly says not to ship.
+
+## Default Shipping Contract
+
+Follow the shared shipping contract convention in CLAUDE.md.

package/packs/skill-dev/claude/create-local-skill/CHANGELOG.md

@@ -1,5 +1,9 @@
 # Changelog
 
+## v0.2 - 2026-06-13
+
+- Upstream-safety note references `npx skillpacks uninstall-global` instead of the removed `init.sh --uninstall`.
+
 ## v0.1 - 2026-05-30
 
 - Tightened post-creation skill visibility guidance to distinguish Claude Code `/reload-skills`, `/clear`, and restart fallback behavior from Codex fresh CLI session fallback.

package/packs/skill-dev/claude/create-local-skill/SKILL.md

@@ -2,7 +2,7 @@
 name: create-local-skill
 description: Scaffold a new user-local skill in ~/.claude/skills (and optionally ~/.codex/skills), then offer to promote it to a personal fork of agentic-skills
 type: execution
-version: v0.1
+version: v0.2
 argument-hint: <skill-name> [description]
 ---
 
@@ -10,7 +10,7 @@ argument-hint: <skill-name> [description]
 
 Scaffold a new **user-local** skill directly into `~/.claude/skills/<name>/` (and optionally `~/.codex/skills/<name>/`) so the user can experiment without touching the upstream agentic-skills repo. At the end, offer to **promote** the skill by copying it into their personal fork of agentic-skills.
 
-Write **real directories**, not managed roots back to the shared repo. `init.sh --uninstall` only removes repo-managed skill installs whose source lives inside agentic-skills, so user-authored skills are untouched by upstream sync.
+Write **real directories**, not managed roots back to the shared repo. `npx skillpacks uninstall-global` only removes skillpacks-owned skill installs whose source lives inside agentic-skills, so user-authored skills are untouched by upstream sync.
 
 ## Process
 
@@ -23,7 +23,7 @@ Write **real directories**, not managed roots back to the shared repo. `init.sh
 2. **Validate the target path:**
    - Target is `$HOME/.claude/skills/<name>`.
    - If the path already exists:
-     - If it is a **symlink** pointing into an agentic-skills repo (`readlink` contains `agentic-skills/global/` or `agentic-skills/packs/`), refuse — this would shadow a repo-managed skill. Tell the user to choose a different name.
+     - If it is a **symlink** pointing into an agentic-skills repo (`readlink` contains `agentic-skills/base/` or `agentic-skills/packs/`), refuse — this would shadow a repo-managed skill. Tell the user to choose a different name.
      - If it is a **real directory or a user-owned symlink**, ask before overwriting.
 
 3. **Write the Claude SKILL.md** at `~/.claude/skills/<name>/SKILL.md`:
@@ -70,9 +70,9 @@ Write **real directories**, not managed roots back to the shared repo. `init.sh
      - Clone this repo and `git remote set-url origin <their-repo-url>` to repoint pushes.
    - Verify the path exists and is a git repo (`git -C <path> rev-parse --show-toplevel`).
    - Copy the scaffolded skill into:
-     - `<fork>/global/claude/<name>/` (and `<fork>/global/codex/<name>/` if a Codex version was created), **or**
+     - `<fork>/base/claude/<name>/` (and `<fork>/base/codex/<name>/` if a Codex version was created), **or**
      - `<fork>/personal/claude/<name>/` if the user wants to keep personal skills segregated from upstream-syncable dirs. Ask which.
-   - If the skill is promoted into a fork's `global/` or `packs/` tree, also update that fork's `tests/harness/bench-coverage.ts` and add either a deterministic custom setup under `tests/layer4/setups/` or an explicit blocked row with `blocked_reason` and `next_command`.
+   - If the skill is promoted into a fork's `base/` or `packs/` tree, also update that fork's `tests/harness/bench-coverage.ts` and add either a deterministic custom setup under `tests/layer4/setups/` or an explicit blocked row with `blocked_reason` and `next_command`.
    - For promoted custom setups, include a deterministic quality rubric when practical, or record why quality scoring is blocked/deferred instead of adding a subjective rubric.
    - Recommend `pnpm --dir tests bench:coverage` before the promoted skill is committed.
    - Show the `git status` in the fork and suggest a commit message like `feat(skill): add <name>`. Do **not** commit or push automatically — leave that to the user.
@@ -81,7 +81,7 @@ Write **real directories**, not managed roots back to the shared repo. `init.sh
 
 ## Notes
 
-- Never write into this repo's `global/` or `packs/` directories from this skill. Target paths are always under `$HOME/.claude/skills`, `$HOME/.codex/skills`, or an explicitly-supplied personal fork path.
+- Never write into this repo's `base/` or `packs/` directories from this skill. Target paths are always under `$HOME/.claude/skills`, `$HOME/.codex/skills`, or an explicitly-supplied personal fork path.
 - Do not create documentation files beyond `SKILL.md` unless the user asks.
 - If the user wants version control for their personal skills without a full fork, suggest `git init` inside a sibling directory and symlinking from `~/.claude/skills/<name>` — but default to the simpler "real directory in `~/.claude/skills`" flow.
 

package/packs/skill-dev/claude/create-local-skill/archive/v0.1/SKILL.md

@@ -0,0 +1,91 @@
+---
+name: create-local-skill
+description: Scaffold a new user-local skill in ~/.claude/skills (and optionally ~/.codex/skills), then offer to promote it to a personal fork of agentic-skills
+type: execution
+version: v0.1
+argument-hint: <skill-name> [description]
+---
+
+# Create Local Skill
+
+Scaffold a new **user-local** skill directly into `~/.claude/skills/<name>/` (and optionally `~/.codex/skills/<name>/`) so the user can experiment without touching the upstream agentic-skills repo. At the end, offer to **promote** the skill by copying it into their personal fork of agentic-skills.
+
+Write **real directories**, not managed roots back to the shared repo. `init.sh --uninstall` only removes repo-managed skill installs whose source lives inside agentic-skills, so user-authored skills are untouched by upstream sync.
+
+## Process
+
+1. **Parse `$ARGUMENTS`** for `<skill-name>` and optional description. If missing, ask the user for:
+   - Skill name (kebab-case, e.g. `my-skill`)
+   - One-line description (used in the frontmatter `description` field — it is how the assistant decides when to invoke the skill, so be specific)
+   - Type (`execution`, `analysis`, `workflow`, etc. — default `execution`)
+   - Whether to also create a Codex version in `~/.codex/skills/<name>/` (default yes)
+
+2. **Validate the target path:**
+   - Target is `$HOME/.claude/skills/<name>`.
+   - If the path already exists:
+     - If it is a **symlink** pointing into an agentic-skills repo (`readlink` contains `agentic-skills/base/` or `agentic-skills/packs/`), refuse — this would shadow a repo-managed skill. Tell the user to choose a different name.
+     - If it is a **real directory or a user-owned symlink**, ask before overwriting.
+
+3. **Write the Claude SKILL.md** at `~/.claude/skills/<name>/SKILL.md`:
+
+   ```markdown
+   ---
+   name: <name>
+   description: <description>
+   type: <type>
+   version: v0.0
+   ---
+
+   # <Title>
+
+   <1-2 sentence purpose statement.>
+
+   ## When to use
+
+   - <trigger 1>
+   - <trigger 2>
+
+   ## Process
+
+   1. <step>
+   2. <step>
+   3. <step>
+
+   ## Output
+
+   <what the skill produces>
+   ```
+
+4. **Optionally mirror to Codex** at `~/.codex/skills/<name>/SKILL.md` with the Codex invocation convention (`Invoke as $<name>.`). Match the format of existing `~/.codex/skills/*/SKILL.md` files.
+
+5. **Report the result:** show the created paths and remind the user of the runner-specific reload path. Claude Code should 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 should start a fresh Codex CLI session if the `$` skill list remains stale.
+
+6. **Offer to promote.** Ask:
+
+   > "Would you like to promote this skill to your personal fork of agentic-skills? (y/n)"
+
+   If yes:
+   - Ask for the path to their personal fork (e.g. `~/projects/tools/agentic-skills-personal`). If they don't have one, explain the options:
+     - Fork `agentic-skills` on GitHub and `git clone` it.
+     - Clone this repo and `git remote set-url origin <their-repo-url>` to repoint pushes.
+   - Verify the path exists and is a git repo (`git -C <path> rev-parse --show-toplevel`).
+   - Copy the scaffolded skill into:
+     - `<fork>/base/claude/<name>/` (and `<fork>/base/codex/<name>/` if a Codex version was created), **or**
+     - `<fork>/personal/claude/<name>/` if the user wants to keep personal skills segregated from upstream-syncable dirs. Ask which.
+   - If the skill is promoted into a fork's `base/` or `packs/` tree, also update that fork's `tests/harness/bench-coverage.ts` and add either a deterministic custom setup under `tests/layer4/setups/` or an explicit blocked row with `blocked_reason` and `next_command`.
+   - For promoted custom setups, include a deterministic quality rubric when practical, or record why quality scoring is blocked/deferred instead of adding a subjective rubric.
+   - Recommend `pnpm --dir tests bench:coverage` before the promoted skill is committed.
+   - Show the `git status` in the fork and suggest a commit message like `feat(skill): add <name>`. Do **not** commit or push automatically — leave that to the user.
+
+7. **Safety note to surface:** pushing to the upstream agentic-skills repo requires write access. A plain clone without write access will be rejected at the remote; a fork pushes to the user's own repo. There is no path by which this skill can push a user's experimental skill to the shared upstream.
+
+## Notes
+
+- Never write into this repo's `base/` or `packs/` directories from this skill. Target paths are always under `$HOME/.claude/skills`, `$HOME/.codex/skills`, or an explicitly-supplied personal fork path.
+- Do not create documentation files beyond `SKILL.md` unless the user asks.
+- If the user wants version control for their personal skills without a full fork, suggest `git init` inside a sibling directory and symlinking from `~/.claude/skills/<name>` — but default to the simpler "real directory in `~/.claude/skills`" flow.
+
+## Default Shipping Contract
+
+Follow the shared shipping contract convention in CLAUDE.md.
+

package/packs/skill-dev/claude/skill-interview/SKILL.md

@@ -20,7 +20,7 @@ Use this skill when the user wants to create or substantially redesign a skill b
    - If the user wants an experimental personal skill under `~/.claude/skills`, plan for `/create-local-skill`; otherwise default to repo-managed `/create-agentic-skill`.
 
 2. **Gather local evidence before probing.**
-   - Search for overlapping skills in the active skill list and repository paths such as `global/codex/`, `global/claude/`, and `packs/*/{codex,claude}/`.
+   - Search for overlapping skills in the active skill list and repository paths such as `base/codex/`, `base/claude/`, and `packs/*/{codex,claude}/`.
    - Read the closest existing skill contracts and any relevant `tasks/lessons.md` entries before asking detailed questions.
    - If an existing skill already covers the request, explain the overlap and ask whether the user wants an update, alias, narrower variant, or new skill.
 
@@ -89,10 +89,10 @@ Use this skill when the user wants to create or substantially redesign a skill b
 
 After writing the brief and interview log, recommend exactly one next command:
 
-- `/create-agentic-skill <skill-name>` for repo-managed global skills.
+- `/create-agentic-skill <skill-name>` for repo-managed base skills.
 - `/create-local-skill <skill-name>` for personal local-only skills.
 - `/targeted-skill-builder <existing-skill> <gap>` when the interview found that an existing skill should be updated instead of creating a new skill.
-- `/pack` or a pack-local creation route when the skill belongs inside a project-local pack rather than global skills.
+- `/pack` or a pack-local creation route when the skill belongs inside a project-local pack rather than base skills.
 
 Output exactly two lines beyond the normal report:
 

package/packs/skill-dev/claude/targeted-skill-builder/CHANGELOG.md

@@ -1,5 +1,9 @@
 # Changelog
 
+## v0.4 - 2026-06-13
+
+- Validation and reload steps use `npx skillpacks refresh` instead of the removed `./init.sh`.
+
 ## v0.3 - 2026-06-09
 
 - Updated Skills Showcase refresh commands to use app-owned generator and validator paths after the workspace split.

package/packs/skill-dev/claude/targeted-skill-builder/SKILL.md

@@ -2,7 +2,7 @@
 name: targeted-skill-builder
 description: Build or update one specific skill from a concrete workflow gap, correction, or repeated bad recommendation
 type: execution
-version: v0.3
+version: v0.4
 argument-hint: "[workflow gap, correction, skill name, or capability request]"
 ---
 
@@ -33,7 +33,7 @@ This is intentionally narrower than `/analyze-sessions`. Do not scan all Claude/
    - If examples are needed, ask for them or run a tightly scoped history query limited by path, skill name, date range, or exact phrase.
    - Do not scan all session history unless explicitly requested.
 5. Search existing skills for overlap before creating anything:
-   - Search `global/claude`, `global/codex`, `packs`, and project-local `.claude/skills` or `.codex/skills` when present.
+   - Search `base/claude`, `base/codex`, `packs`, and project-local `.claude/skills` or `.codex/skills` when present.
    - Compare name, description, workflow, and next-step routing behavior.
    - If an existing skill substantially covers the job, recommend updating that skill instead of adding a duplicate.
 6. Decide the smallest durable fix:
@@ -42,7 +42,7 @@ This is intentionally narrower than `/analyze-sessions`. Do not scan all Claude/
    - Reusable prompt/template: choose this when the behavior is too situational or not stable enough for a skill.
    - No repository change: choose this when the request is already covered and only needs a usage note.
 7. Resolve the destination:
-   - Default new shared Claude/Codex skills to this repository: `/Users/georgele/projects/tools/agentic-skills/global/claude/<name>/SKILL.md` and `/Users/georgele/projects/tools/agentic-skills/global/codex/<name>/SKILL.md`.
+   - Default new shared Claude/Codex skills to this repository: `/Users/georgele/projects/tools/agentic-skills/base/claude/<name>/SKILL.md` and `/Users/georgele/projects/tools/agentic-skills/base/codex/<name>/SKILL.md`.
    - If the current session is not in the agentic-skills repository and the user wants to audit or amend an existing shared skill, do not edit a local copy. Provide a concise prompt for the user to run from `/Users/georgele/projects/tools/agentic-skills` with the target skill path and requested adjustment.
    - Use user-local `~/.claude/skills` or `~/.codex/skills` only when the user explicitly asks for a personal/local skill.
 8. If creating or updating a repository skill:
@@ -59,7 +59,7 @@ This is intentionally narrower than `/analyze-sessions`. Do not scan all Claude/
    - Store it only when the user asks for a file or the current repo has an obvious prompt/template location.
    - Otherwise output the reusable prompt directly.
 10. Run validation after repository skill changes:
-    - `./init.sh`
+    - `npx skillpacks refresh` (recreate project-local base/pack skill installs from the changed sources)
     - `./scripts/skill-deps.sh --broken`
     - `./scripts/skill-versions.sh --missing`
     - `./scripts/skill-next-step-routing.sh --missing`
@@ -84,7 +84,7 @@ Produce a concise report with:
 - Existing-skill overlap findings.
 - Files created or changed, if any, including generated showcase assets when skill metadata or behavior changed.
 - Validation results.
-- Reload note: after `./init.sh`, tell the user the runner-specific reload path. Claude Code should 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 should start a fresh Codex CLI session if the `$` skill list remains stale.
+- Reload note: after `npx skillpacks refresh`, tell the user the runner-specific reload path. Claude Code should 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 should start a fresh Codex CLI session if the `$` skill list remains stale.
 
 When an external project session needs an existing shared skill amended, output a prompt like:
 

package/packs/skill-dev/claude/targeted-skill-builder/archive/v0.3/SKILL.md

@@ -0,0 +1,116 @@
+---
+name: targeted-skill-builder
+description: Build or update one specific skill from a concrete workflow gap, correction, or repeated bad recommendation
+type: execution
+version: v0.3
+argument-hint: "[workflow gap, correction, skill name, or capability request]"
+---
+
+# Targeted Skill Builder
+
+Use this skill when the user wants a narrow, durable workflow improvement from the current prompt or conversation: a concrete problem, user correction, repeated bad recommendation, or capability gap that may deserve a new skill, an existing-skill update, or a reusable prompt/template.
+
+This is intentionally narrower than `/analyze-sessions`. Do not scan all Claude/Codex history by default. Treat broad session analysis as optional evidence only when the user explicitly asks for it. Use `/session-triage` first when one immediate issue, correction, repo incident, or suspected skill failure still needs verification before a skill change is designed.
+
+## Process
+
+1. Read `tasks/lessons.md` first when it exists. Extract only correction patterns relevant to the user's current request.
+2. Identify the narrow workflow gap:
+   - Problem or correction.
+   - Triggering context from the current prompt/conversation.
+   - Bad recommendation or missing capability to prevent.
+   - Desired future behavior.
+3. Ask for the intended output unless the user already made it explicit:
+   - New skill.
+   - Update existing skill.
+   - Reusable prompt/template only.
+   - Unsure, recommend.
+4. Gather only targeted evidence:
+   - Use the current prompt and conversation context first.
+   - Read a named skill file when provided.
+   - Inspect user-provided files or paths when provided.
+   - Route to `/session-triage` when the user wants investigation of one immediate issue or the available evidence is not enough to verify the correction.
+   - If examples are needed, ask for them or run a tightly scoped history query limited by path, skill name, date range, or exact phrase.
+   - Do not scan all session history unless explicitly requested.
+5. Search existing skills for overlap before creating anything:
+   - Search `base/claude`, `base/codex`, `packs`, and project-local `.claude/skills` or `.codex/skills` when present.
+   - Compare name, description, workflow, and next-step routing behavior.
+   - If an existing skill substantially covers the job, recommend updating that skill instead of adding a duplicate.
+6. Decide the smallest durable fix:
+   - New skill: choose this only when no existing skill owns the workflow and the behavior is repeatable.
+   - Existing skill update: choose this when the fix is a missing branch, constraint, evidence gate, or routing correction inside an existing workflow.
+   - Reusable prompt/template: choose this when the behavior is too situational or not stable enough for a skill.
+   - No repository change: choose this when the request is already covered and only needs a usage note.
+7. Resolve the destination:
+   - Default new shared Claude/Codex skills to this repository: `/Users/georgele/projects/tools/agentic-skills/base/claude/<name>/SKILL.md` and `/Users/georgele/projects/tools/agentic-skills/base/codex/<name>/SKILL.md`.
+   - If the current session is not in the agentic-skills repository and the user wants to audit or amend an existing shared skill, do not edit a local copy. Provide a concise prompt for the user to run from `/Users/georgele/projects/tools/agentic-skills` with the target skill path and requested adjustment.
+   - Use user-local `~/.claude/skills` or `~/.codex/skills` only when the user explicitly asks for a personal/local skill.
+8. If creating or updating a repository skill:
+   - Follow existing frontmatter conventions: `name`, specific `description`, `type`, `version`, and `argument-hint` when useful.
+   - Keep `SKILL.md` concise and operational.
+   - Include clear trigger conditions, process steps, outputs, constraints, and next-step routing for mutation-capable skills.
+   - Mirror Codex when shared behavior is expected, and add Codex `agents/openai.yaml`.
+   - Update `tests/harness/bench-coverage.ts` for every new repository skill or material skill behavior update.
+   - Add/register a deterministic custom setup under `tests/layer4/setups/` when practical, or record an explicit blocked row with `blocked_reason` and `next_command` when coverage depends on unsafe or external conditions.
+   - For custom setup work, include a deterministic output-quality rubric when practical. Prefer fixture fact coverage, concrete file/command references, expected next-route handoffs, specificity checks, reference traits, and forbidden-fabrication checks over broad prose judgments.
+   - If deterministic quality scoring is not reliable for the skill, record the blocked/deferred quality rationale in the setup review notes or coverage follow-up instead of shipping only silent hard assertions.
+   - Update skill discovery docs and routing docs only when the new or changed skill must be discoverable or routed by other skills.
+9. If writing a reusable prompt/template only:
+   - Store it only when the user asks for a file or the current repo has an obvious prompt/template location.
+   - Otherwise output the reusable prompt directly.
+10. Run validation after repository skill changes:
+    - `./init.sh`
+    - `./scripts/skill-deps.sh --broken`
+    - `./scripts/skill-versions.sh --missing`
+    - `./scripts/skill-next-step-routing.sh --missing`
+    - `pnpm --dir tests bench:coverage`
+    - Focused layer1 benchmark setup tests when `tests/harness/bench-coverage.ts`, `tests/harness/bench-setups.ts`, or `tests/layer4/setups/` changed.
+    - If any tracked `SKILL.md` or `PACK.md` behavior or metadata changed, refresh the Skills Showcase data:
+      - `node apps/skills-showcase/scripts/generate-skills-showcase-data.mjs`
+      - `node apps/skills-showcase/scripts/generate-skills-showcase-github-data.mjs`
+      - `apps/skills-showcase/scripts/validate-skills-showcase-data.sh`
+    - Review curated showcase copy, catalog grouping, workflow animation text, and proof receipts when the skill change could affect the public website; update those files or record why no curated website copy changed.
+    - Targeted `rg` checks for the behavior being changed.
+    - `git diff --check`
+11. Update `tasks/todo.md` review notes with validation results.
+12. Commit and push per the repository contract when tracked files changed.
+
+## Output
+
+Produce a concise report with:
+
+- Decision: new skill, existing-skill update, reusable prompt/template, or no repository change.
+- Evidence used and evidence intentionally skipped.
+- Existing-skill overlap findings.
+- Files created or changed, if any, including generated showcase assets when skill metadata or behavior changed.
+- Validation results.
+- Reload note: after `./init.sh`, tell the user the runner-specific reload path. Claude Code should 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 should start a fresh Codex CLI session if the `$` skill list remains stale.
+
+When an external project session needs an existing shared skill amended, output a prompt like:
+
+```text
+From /Users/georgele/projects/tools/agentic-skills, run targeted-skill-builder for:
+- Target skill: <path or skill name>
+- Problem: <concrete correction or workflow gap>
+- Desired change: <specific behavior>
+- Evidence: <small scoped files/examples>
+- Preferred output: update existing skill
+```
+
+## Constraints
+
+- Prefer the smallest durable workflow fix.
+- Do not create a broad meta-skill when a precise skill, existing-skill update, or reusable prompt solves the problem.
+- Do not route every idea to `/spec-interview`; use `/feature-interview` when the planning destination is uncertain.
+- Treat broad `/analyze-sessions` work as optional evidence for recurrence and trend analysis, not the default workflow.
+- Use `/session-triage` for one immediate issue, correction, repo incident, or suspected skill failure that needs verification before building or updating a skill.
+- Do not read unrelated history, projects, or private files for examples without user direction.
+- Do not create or modify GitHub Actions workflows.
+
+## Alignment Page
+
+When this skill produces durable deliverables (research, specs, plans, reports, prototypes, or any document output), build a full-depth HTML alignment page following `ALIGNMENT-PAGE.md` in this skill's directory. Output: `alignment/targeted-skill-builder-{topic}.html`.
+
+## Default Shipping Contract
+
+Follow the shared shipping contract convention in CLAUDE.md.

package/packs/skill-dev/codex/create-agentic-skill/CHANGELOG.md

@@ -1,5 +1,13 @@
 # Changelog
 
+## v0.3 - 2026-06-13
+
+- Repo-verification check no longer looks for the removed `init.sh`; it now checks for `base/codex/`, `base/claude/`, and `packages/skillpacks/`.
+
+## v0.2 - 2026-06-13
+
+- Renamed authoring paths from `global/{claude,codex}` to `base/{claude,codex}` following the global→base directory migration.
+
 ## v0.1 - 2026-06-09
 
 - Updated Skills Showcase refresh commands to use app-owned generator and validator paths after the workspace split.

package/packs/skill-dev/codex/create-agentic-skill/SKILL.md

@@ -1,8 +1,8 @@
 ---
 name: create-agentic-skill
-description: Create or update a repo-managed skill inside this agentic-skills checkout under global/codex and optionally global/claude, then validate, commit, and push it
+description: Create or update a repo-managed skill inside this agentic-skills checkout under base/codex and optionally base/claude, then validate, commit, and push it
 type: execution
-version: v0.1
+version: v0.3
 argument-hint: "<skill-name> [description] [--codex-only|--claude-only|--mirror]"
 ---
 
@@ -15,14 +15,14 @@ Use this skill when the user wants to add or update a skill in the `agentic-skil
 ## Process
 
 1. **Confirm repository context.**
-   - Verify the current repo is `agentic-skills` by checking for `init.sh`, `global/codex/`, and `global/claude/`.
+   - Verify the current repo is `agentic-skills` by checking for `base/codex/`, `base/claude/`, and `packages/skillpacks/`.
    - If the current repo is not `agentic-skills`, stop and ask for the checkout path.
    - Inspect `git status --short` and identify unrelated dirty files before editing.
 
 2. **Resolve skill identity.**
    - Parse `<skill-name>` as kebab-case.
    - Parse the description when provided; otherwise ask for a one-line description.
-   - Default to creating both `global/codex/<skill-name>/SKILL.md` and `global/claude/<skill-name>/SKILL.md` when the skill should exist for both agents.
+   - Default to creating both `base/codex/<skill-name>/SKILL.md` and `base/claude/<skill-name>/SKILL.md` when the skill should exist for both agents.
    - Honor `--codex-only`, `--claude-only`, or `--mirror`.
    - If a local-only workflow is requested, route to `$create-local-skill` instead.