Repository navigation
Conversation
Enabling basic-memory@basicmachines-co now brings the canonical memory-* skills as /basic-memory:memory-*, so no machine needs a separate `npx skills add`. skills/ stays the single source of truth. - scripts/sync_plugin_skills.py copies every skills/memory-* directory (resources included) into plugins/claude-code/skills/, except the CI-only memory-ci-capture prompt. `--check` reports drift. - validate_claude_plugin.py runs that drift check, so package-check-claude-code and the Consolidated Packages CI job fail on a hand-edited copy or an unsynced skills/ change. - Committed copies, not symlinks: Claude Code dereferences a symlink into the rest of a git-hosted marketplace, but skips it for the plugin-local marketplace and local-path installs, and Windows checkouts without symlink support break it. - bm-setup no longer runs `npx skills add`; it offers to remove untracked standalone memory-* copies that would now appear twice. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Signed-off-by: Drew Cain <groksrc@gmail.com>
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Signed-off-by: Drew Cain <groksrc@gmail.com>
|
nice! |
|
Closing for now. Since this was opened, main gained shared-skill distribution (#1737: the |
|
Picking this back up as a note for later. No release or version bump waits on it. What prompted it
Where the "plugins don't bundle skills" rule came fromfc8ac86 (2026-05-28, for #866) made Claude Code setup run Options for the two repo plugins
Version bumpsEvery bundled option ties skill updates to plugin releases. The directory plugin already works this way: a skill change reaches Codex and ChatGPT users only after a new upload (now 3.0.3). For the repo plugins, check whether Claude Code and Codex refresh a git-marketplace plugin without a version change. If they don't, a skill fix needs a plugin version bump, which Deferred for now. |
Summary
Enabling
basic-memory@basicmachines-conow brings the canonicalmemory-*skills as/basic-memory:memory-*, so a machine gets them from the plugin alone instead of a separatenpx skills add.skills/stays the single source of truth.scripts/sync_plugin_skills.pycopies everyskills/memory-*directory, resources included, intoplugins/claude-code/skills/. It leaves the plugin's ownbm-*skills alone and removes stalememory-*copies.--checkreports drift. It follows the same pattern assync_memory_schemas.py.validate_claude_plugin.pyruns the check. That makesjust package-check-claude-codeand the Consolidated Packages / Claude Code marketplace CI job fail on a hand-edited copy or on askills/change that was never synced.skills/**is already in that workflow's path filter, and this PR adds the sync script to it.bm-setupno longer runsnpx skills add. Instead it offers to remove standalonememory-*copies left by an earliernpxinstall, which would otherwise show up twice. It skips anything tracked in git.skills/README, DEVELOPMENT, and CLAUDE (sync step), root README, AGENTS.md, and both changelogs.Included / excluded
Bundled (14): capture, continue, curate, defrag, ingest, lifecycle, literary-analysis, metadata-search, notes, onboarding (with
references/andevals/), reflect, research, schema, tasks.Excluded:
memory-ci-capture. It is the machine prompt forbm ci publish, it returns only AgentSynthesis JSON, and it is not in theskills/README.mdcatalog. It is listed inEXCLUDED_SKILLS, so any newmemory-*skill is bundled automatically.Why committed copies rather than symlinks
According to the Claude Code docs (plugin loading, and "Share files within a marketplace with symlinks"), a marketplace install copies only the plugin directory into the cache:
skills/memory-x -> ../../../skills/memory-xwould work for the rootbasicmachines-comarketplace.plugins/claude-code/.claude-plugin/marketplace.json(source./).Real copies plus a drift check work on every install path.
Names
memory-*andbm-*don't overlap, and a test enforces that. Plugin skills are namespaced asbasic-memory:<name>, so a standalonememory-notesdoesn't conflict, but it does duplicate. Some skills overlap in function, and their descriptions may compete when Claude picks a skill:bm-checkpoint/memory-captureandbm-orient/memory-continue.Verification
just package-check-claude-code: validator passes, andclaude plugin validate . --strictpassesclaude plugin validate . --strict(root marketplace) andplugins/claude-code/.claude-plugin/plugin.json --strict: passjust package-check-skills(15 skills) andjust package-check-codex: passuv run pytest tests/test_plugin_skill_bundle.py tests/test_codex_plugin_package.py tests/test_claude_plugin_hooks.py tests/test_update_versions.py tests/cli/test_install_claude_code.py plugins/claude-code/hooks --no-cov: 68 passedjust lint,just typecheck(with themilvusextra synced),ruff format --check .: cleanCLAUDE_CONFIG_DIR, ranclaude plugin marketplace add basicmachines-co/basic-memory#feat/plugin-memory-skillsand thenclaude plugin install basic-memory@basicmachines-co. The cache (.../basic-memory/0.23.2/skills/) held all 8bm-*and all 14memory-*directories, including the onboardingreferences/andevals/. Aclaude -p --plugin-dir <cache>session listedbasic-memory:memory-*for all 14.Rollout note
plugin.jsonpins"version": "0.23.2", so existing installs keep their cached copy until the version changes. The bundle reaches users with the nextjust release(v0.24.0), which bumps the plugin manifests. After that, users get it on/plugin marketplace update basicmachines-coorclaude plugin update, or automatically if they turned on auto-update for this marketplace. Auto-update is off by default for third-party marketplaces.🤖 Generated with Claude Code