- name
SKILL.md
The skill file stays in the publisher's repository.
Paste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add BlackBeltTechnology/pi-agent-dashboard --skill switch-extension-source -a cursor -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add BlackBeltTechnology/pi-agent-dashboard --skill switch-extension-source -a claude-code -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add BlackBeltTechnology/pi-agent-dashboard --skill switch-extension-source -a codex -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add BlackBeltTechnology/pi-agent-dashboard --skill switch-extension-source -a grok -ySend the copied message in a Grok Bot chat. The Bot fetches this SKILL.md from GitHub and adds it to the skills all your Bots share.
Install this skill: https://github.com/BlackBeltTechnology/pi-agent-dashboard/tree/HEAD/.pi/skills/switch-extension-sourceFrom the publisher
Toggle a monorepo extension between npm (published) and local (working tree) source.
GUI equivalent: Settings → Packages exposes a per-row Reset to published version action (change: reset-override-to-npm) that resets a local/git-installed row back to its canonical
npm:<name>— install-first / remove-second, confirm-gated. It is the one-click UI analog ofswitch <pkg> npmhere; keep the two semantically aligned (both drop the localpackages[]registration only, never the working-tree files).
On a dev machine you want extensions to load your live working tree so edits take effect. Distribution users consume the published npm package. Both can be wired at once across two config layers, and whichever pi resolves last wins — non-deterministic ("I edited it but nothing changed"). This skill enforces exactly one source per package.
GLOBAL ~/.pi/agent/settings.json "packages": [...]
npm -> "npm:<npmName>"
local -> "<repoRoot>/packages/<dir>" (dir path; pi resolves package.json "pi")
PROJECT <repo>/.pi/settings.json "packages":[{ source, extensions:["+packages/<dir>/<entry>"] }]
local overlay -> only with --overlay; loads ONLY inside this repo; needs pi.extensions
local (default) = global dir path → loads in every session everywhere.
local --overlay = project overlay → loads only when running pi inside this repo.
npx tsx ./scripts/switch-source.ts status # where each installed pkg loads from
npx tsx ./scripts/switch-source.ts local <pkg> # -> local working tree (global path)
npx tsx ./scripts/switch-source.ts local <pkg> --overlay# -> local, this-repo-only (extensions only)
npx tsx ./scripts/switch-source.ts npm <pkg> # -> published npm build
<pkg> = monorepo dir name (kb-extension) OR npm name (@blackbelt-technology/pi-dashboard-kb-extension).
Each switch removes all other representations of that package, timestamped-backs-up every file it
edits (*.bak-switch-*), and re-validates JSON before writing.
status — see current source per package.local <pkg> or npm <pkg> — flip it. Script guarantees single-source.packages[] is read at session init, so the change takes effect on the
next session start. Respawn sessions or npm run reload (reload alone may not re-resolve
the package list in an already-running process — fresh session is the guaranteed path).dashboardPluginBridges /
_dashboardManagedPackages. This skill does NOT toggle those — leave them to the dashboard UI.npm mode your
working-tree edits do NOT load until you local again.--overlay needs pi.extensions — skill-only packages (pi.skills, no extensions) can't use
the overlay form; use plain local (global dir path).status showing
one source.npx tsx ./scripts/switch-source.ts status shows the target package at exactly one source.python3 -c "import json; json.load(open('<file>'))" confirms both settings files are valid JSON.Switch a monorepo extension/skill package between its published npm source and its local working-tree source, guaranteeing exactly one source per package. Use when "my edits don't take effect", "load
---name: switch-extension-sourcedescription: Switch a monorepo extension/skill package between its published npm source and its local working-tree source…---# .pi/skills/switch-extension-source/SKILL.mdOverview
Switch a monorepo extension/skill package between its published npm source and its local working-tree source, guaranteeing exactly one source per package. Use when "my edits don't take effect", "load local extension", "test the published npm build", or reconciling dev vs distribution package sources.
FAQ
Download .pi/skills/switch-extension-source/SKILL.md from the publisher, or copy the path and open the repository. PlugMCP lists the skill and does not host the file.
The publisher keeps it at https://github.com/BlackBeltTechnology/pi-agent-dashboard.
Claude, Cursor, Codex, and Grok Build can read a SKILL.md you add from the publisher's repository. Grok Bot installs it when you send the skill's GitHub folder link in a chat.