ccm-loadlisted

Load cc-memory for this project — verify the plugin is globally enabled, ensure the project's .ccm/ directory is initialized, and report end-to-end health. The cc-memory equivalent of "make sure I'm wired up here".
skymanbp/cc-memory · ★ 6 · AI & Automation · score 78

Install: claude install-skill skymanbp/cc-memory

## /ccm-load — Load cc-memory into this project Run this once in any new project to confirm cc-memory is **active**, the project's `.ccm/` is initialized, and PROGRESS.md/MEMORY.md are generated. Idempotent — safe to re-run. ### What this skill does This skill covers **activation and project bootstrap** — the things no other entry point does. Ongoing diagnostics belong to `/cc-mem status`; the two are deliberately disjoint (see the table at the end of this file). 1. **Verify activation, PER INSTALL LAYOUT.** The two shipped layouts are activated by *different* mechanisms, so one check cannot serve both: - **marketplace / dev checkout** — `~/.claude/settings.json` `enabledPlugins["cc-memory@cc-memory"]=true`, root from `extraKnownMarketplaces.cc-memory` **or** `plugins/installed_plugins.json` (a `/plugin marketplace add <github-repo>` install has no local path), hooks declared by `<root>/hooks/hooks.json`. - **standalone / `.exe` installer** — never appears in `enabledPlugins` at all. `ui/installer.py:_merge_into_settings` writes **only** the `hooks` key, so activation means `settings.json["hooks"]` registers cc-memory for all five events; the tree it lays down is **flat**. Either layout activated ⇒ **proceed to bootstrap**. Nothing activated ⇒ print the fix for the layout this machine actually has (never tell an `.exe` user to add a marketplace — they have no repo). The rule is mirrored from `cc_memory/cli/mem.py`'s