← ClaudeAtlas

editing-skillslisted

Use when adding, editing, publishing, or debugging why a change isn't live in any mattstack-connected skill surface -- the mattstack plugin, a team pack (acme), or a compiled/vendored pipeline verb built with `rt skills compile` -- e.g. "add a mattstack skill", "why isn't my skill or pipeline change showing up", "rt skills compile / check", "update the work orchestrator", or any change under mattstack-skills, a teams/<team> pack, or a shared work/review engine.
m4ttstack/skills · ★ 0 · Code & Development · score 72
Install: claude install-skill m4ttstack/skills
# Editing and Publishing Estate Skills Skills load from a **versioned plugin cache** (`<config>/plugins/cache/<marketplace>/<plugin>/<version>/`), never from the source repo. A source edit is invisible until you bump the plugin version, run the update, and restart the session. Same-commit version bumps are the convention (see any pack bump in git history). What the update puts in the cache differs by estate: a team pack's update copies the pack's whole working tree, untracked files and `.worktrees/` included, so prune stray worktrees before a bump; the mattstack plugin's update clones the checkout's committed `main`, so an uncommitted edit or an untracked file never reaches the cache. The team pack is a _directory-source_ marketplace, so a loaded pack skill's reported base dir often points at the SOURCE path, not the cache copy. Don't read that as "it loads from source": the versioned cache is still what a fresh session loads, and the bump/update/restart rule above still applies. The source path in the base dir is a convenience, not the live surface. The mattstack plugin is a _url-source_ entry (a `file://` URL to the checkout), so its base dir is the cache clone itself. ## The two estates | | Team pack (acme) | mattstack plugin