setup
/memory-kit:setup — adopt the kit in an existing repository
The plugin ships behaviour; the repository owns the state. This skill creates that state — always asking before the first write, and never touching files the repo already has.
Running without a user who can answer (a headless or -p run)? Then "offer" means skip and
report: take the documented default where one exists, install nothing that the skill marks as
opt-in, and finish with a list of what was deliberately not installed and what question is still
open. Never invent a preference on the user's behalf and never present a skipped step as done.
Running under a host other than Claude Code (Codex and others load this skill too)?
${CLAUDE_PLUGIN_ROOT} will not expand there — resolve every plugin path in this skill
relative to this SKILL.md file's own location (../../ is the plugin root), and skip the
Claude-Code-only steps (settings.json keys, /context) with a one-line note.