---
name: cplugs-publish-mechanics
description: Concrete cplugs marketplace publish steps live in claude_skill_owl/docs/DEPLOY.md (spt-claude-code only needs the skeleton subset)
metadata: 
  node_type: memory
  type: reference
  originSessionId: ce7ce158-107f-4da4-a203-cea98da80b27
---

The concrete **how-to-publish-to-cplugs** mechanics live in the sister project:
`C:\Users\decid\Documents\projects\claude_skill_owl\docs\DEPLOY.md` (+ `docs/DEPLOY.ps1`).

Covers: marketplace one-time setup (clone `SaberMage/cplugs` → `~/.claude/plugins/marketplaces/cplugs`,
register in `known_marketplaces.json`), per-bump copy-to-`$MARKET`/commit+push, cache sync into
`~/.claude/plugins/cache/cplugs/<plugin>/<version>`, pointer flip via `claude plugin install <p>@cplugs`
(NEVER hand-patch `installed_plugins.json`), `/reload-plugins`, and the gotchas (legacy manual-install
dir → "/plugin not installed"; don't `rm -rf` the cache tree mid-handoff).

**spt-claude-code caveat:** owl's DEPLOY.md ships the FULL binary plugin (owl.exe + seamless-handoff +
cache-prune). spt-claude-code's cplugs target is the THIN SKELETON ONLY (skill skeletons, hooks.json,
SessionStart bootstrap, plugin.json — NO binary; binary+manifest ride the spt-core adapter registry,
spt-conducted). So take only the skeleton subset; SKIP the binary-sync / handoff / cache-prune machinery.
spt-claude-code's own `docs/RELEASE-RUNBOOK.md` has the what/when (two targets, signing-delegated-to-spt)
but abstracts these mechanics. Relayed to perri 2026-06-14. See [[spt-claude-code-next]].