ck: Context Keeper
Give Muse persistent per-project memory with ck (Context Keeper): deterministic /ck commands to init, save, resume, list, and forget project contexts, plus a SessionStart hook that injects a compact brief.
- What
- Give Muse persistent per-project memory with ck (Context Keeper): deterministic /ck commands to init, save, resume, list, and forget project contexts, plus a SessionStart hook that injects a compact brief.
- Cost
- Free
- Needs
- Use "ck: Context Keeper" with your Muse.
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor: ck (Context Keeper), a community skill by sreedhargs89 (MIT, from github.com/sreedhargs89/context-keeper) listed here via affaan-m/ECC, that gives Muse persistent per-project memory driven by deterministic Node.js scripts instead of vibes. The data layout is simple: a projects.json registry and per-project contexts with context.json as the source of truth plus a generated CONTEXT.md view you never hand-edit. The command set covers the whole lifecycle: /ck:init registers a project with auto-detected name, description, stack, goal, constraints, and repo, presented as a confirmation draft before saving; /ck:save is the only command requiring LLM analysis, distilling the session into a summary, where it left off, next steps, decisions with reasons, blockers, and a goal update only if it changed, shown as a draft for approval before writing; /ck:resume gives a full briefing and asks whether anything changed; /ck:info gives a quick snapshot; /ck:list gives a portfolio view; /ck:forget asks for explicit confirmation before permanently deleting a context; /ck:migrate converts v1 data to v2 with backups kept. A SessionStart hook injects a compact five-line brief at about 100 tokens per session and detects unsaved sessions, git activity since the last save, and goal mismatches against CLAUDE.md. By sreedhargs89, listed here with credit to its creator. From the affaan-m/ECC repository (MIT). Honest caveats: the Node scripts must be installed at ~/.claude/skills/ck/commands/ for any of this to work; never edit context.json or CONTEXT.md directly, always use the scripts. Skill Harbor never reviews the code, review it yourself before use.
Version:
Install
Copy the install package below, then paste it into MuseThe install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Use "ck: Context Keeper" with your Muse. Prerequisites: Node.js installed, and the ck scripts from https://github.com/sreedhargs89/context-keeper placed at ~/.claude/skills/ck/commands/ (plus the SessionStart hook registered in ~/.claude/settings.json for auto-loading). 1. Open the skill: https://github.com/affaan-m/ECC/blob/main/skills/ck/SKILL.md and copy the full SKILL.md text. 2. Paste it into a chat with Muse and add: "Run /ck:init for my current project, then confirm the detected details with me." 3. Use /ck:save at the end of each session and /ck:resume when starting a new one on the same project. Tip: only /ck:save requires LLM analysis; all other commands are deterministic script runs. Safety: a skill is plain-text instructions; it runs nothing by itself. Review generated commands before running them.
Saved to your recent installs. Find it anytime on /connect.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.