@skill-map/cli 0.64.1 → 0.66.0

package/dist/cli/tutorial/sm-tutorial/SKILL.md

@@ -305,7 +305,7 @@ the `__PROVIDER__` token and skip kinds the provider does not claim.
      (`harness-built` for `connect-harness`, `harness-connected` for
      `daily-loop`).
   3. Provision the lens: the seeded portfolio has a root `AGENTS.md`
-     (the `openai`/Codex marker) next to `.claude/`, but `openai` is
+     (the `codex`/Codex marker) next to `.claude/`, but `codex` is
      experimental (ships disabled), so auto-detect ignores it and a plain `sm init`
      resolves the `claude` lens with no prompt. Run `sm init`, then
      `sm scan`. (If `.skill-map/` already exists, just `sm scan`.)

package/dist/cli/tutorial/sm-tutorial/references/_core.md

@@ -260,16 +260,16 @@ on-disk convention:
 |----------------|-------------------|-----------------------------|--------------------------------------------------------|
 | `claude`       | `.claude/`        | `agent`, `command`, `skill` | `CLAUDECODE=1` OR `AI_AGENT` starts with `claude-code` |
 | `agent-skills` | `.agents/skills/` | `skill` only (vendor-neutral; also the on-disk home for Google's Antigravity CLI, which replaced the Gemini CLI on 2026-05-19 and adopted this open standard) | experimental (ships disabled; `sm tutorial --experimental` to offer it) |
-| `openai`       | `.codex/`         | `agent` (`.codex/agents/*.toml`) | experimental (ships disabled by default) |
+| `codex`       | `.codex/`         | `agent` (`.codex/agents/*.toml`) | experimental (ships disabled by default) |
 
 **Decision logic, applied silently during pre-flight**: the tutorial
-demonstrates the `claude` provider only. `agent-skills` and `openai`
+demonstrates the `claude` provider only. `agent-skills` and `codex`
 are **experimental** (ship disabled by default) and are not selectable
 here, so there is no runtime to detect or opt into.
 
 1. `provider = claude`, `<provider_dir> = .claude`, kinds =
    `{agent, command, skill}`. Always.
-2. Do NOT offer Antigravity / agent-skills / openai as an alternative,
+2. Do NOT offer Antigravity / agent-skills / codex as an alternative,
    and do NOT ask the tester which runtime hosts them. If a tester
    says they use another runtime, acknowledge it briefly and explain
    that those providers are experimental, the tutorial demos `claude`
@@ -291,7 +291,7 @@ not claim, and report the adjusted `nodeCount` plus the `skipped`
 list in their summary. Today `provider` is always `claude`, so the
 narration uses `.claude/` throughout; the `--provider` plumbing stays
 wired so the coming-soon providers (`agent-skills` / Antigravity,
-`openai`) drop in later without a narrative rewrite. The campaign
+`codex`) drop in later without a narrative rewrite. The campaign
 cross-link chapters target `claude` today (see the reality check
 below).
 

package/dist/cli/tutorial/sm-tutorial/references/part-plugins.md

@@ -70,7 +70,7 @@ Mark `tour-1-intro: done`.
 >    Decides what kind each `.md` file is. The `claude` provider,
 >    for instance, walks `.claude/` and types each file it finds
 >    (agent, command, or skill).
->    Examples: `claude`, `antigravity`, `openai`, `agent-skills`.
+>    Examples: `claude`, `antigravity`, `codex`, `agent-skills`.
 >
 > 🔍 **extractor**
 >    Reads a node's body and emits structured findings (links,
@@ -184,7 +184,7 @@ Mark `tour-3-explore: done`.
 >
 > - What plugins, extensions, and the six kinds are.
 > - Five plugins ship pre-installed (`claude`, `antigravity`,
->   `openai`, `agent-skills`, `core`).
+>   `codex`, `agent-skills`, `core`).
 > - How to list, inspect, diagnose, and toggle extensions from
 >   the CLI (and the same lives in the UI).
 >

package/dist/cli/tutorial/sm-tutorial/references/part-project-kickoff.md

@@ -29,9 +29,9 @@ pre-flight, so the tester sees only the portfolio. If anything demo
 lingers, mention it once and move on.
 
 **Context (agent, do not narrate the plumbing): the lens.** This
-project has a root `AGENTS.md` (the `openai`/Codex marker) sitting next
+project has a root `AGENTS.md` (the `codex`/Codex marker) sitting next
 to the `.claude/` folder (the `claude` marker, where the tutorial skill
-itself lives). `openai` is **experimental** (ships disabled), though, so auto-detect
+itself lives). `codex` is **experimental** (ships disabled), though, so auto-detect
 ignores its marker and `sm init` resolves the lens to `claude`
 silently, exactly like the prologue: only `claude` is selectable today,
 so there is no ambiguity and no prompt. Do not promise the tester a

package/dist/cli/tutorial/sm-tutorial/references/part-settings.md

@@ -146,7 +146,7 @@ Expected: the scan prints a line like `Auto-detected activeProvider
 .skill-map/settings.json`, and `get` then reports `claude`. The lens
 is just a key in `settings.json`, persisted like any other setting.
 
-> Other lenses exist in the engine (`openai` for Codex,
+> Other lenses exist in the engine (`codex` for Codex,
 > `agent-skills`, `antigravity`), but they are **experimental** (ship
 > disabled by default): today we demo the `claude` lens only. The idea to keep is
 > the one above, one project reads through exactly one provider at a