Guardrail·Productivity & Workflow·v2.0.0

ck — Context Keeper

Persistent per-project memory for Claude Code.

You say
Buy it · $99 Read it before you buy $99 Written by affaan-m · unverified publisher
Context cost
1.2k tokensestimated from the bundle, loaded when it triggers
Bundle
1 file · 4.9 kBtext throughout, nothing executable
Licence
MITpaid listing
Last change
v2.0.0
Servers it uses
Noneruns standalone

What it does

Persistent per-project memory for Claude Code. Auto-loads project context on session start, tracks sessions with git activity, and writes to native memory. Commands run deterministic Node.js scripts — behavior is consistent across model versions. Use when a project needs context to survive across Claude Code sessions instead of being re-explained each time.

Installed, it changes the agent in these ways.

What this skill changes about the agent is not written down here yet. The listing was collected from its source, and the description is in its own SKILL.md.

Guardrail

Constrains what the agent is allowed to do.

productivity

The skill itself

This is the whole product. A skill is instructions the model reads, so there is nothing behind the listing you cannot see first — the front matter loads with every session, and the body below it loads when the skill triggers.

SKILL.md4.9 kB · 149 lines
--- name: ck description: Persistent per-project memory for Claude Code. Auto-loads project context on session start, tracks sessions with git activity, and writes to native memory. Commands run deterministic Node.js scripts — behavior is consistent across model versions. Use when a project needs context to survive across Claude Code sessions instead of being re-explained each time. metadata: version: 2.0.0 origin: community author: sreedhargs89 repo: https://github.com/sreedhargs89/context-keeper ---
11# ck — Context Keeper
12
13You are the **Context Keeper** assistant. When the user invokes any /ck:* command,
14run the corresponding Node.js script and present its stdout to the user verbatim.
15Scripts live at: ~/.claude/skills/ck/commands/ (expand ~ with $HOME).
16
17---
18
19## Data Layout
20
21```
22~/.claude/ck/
23├── projects.json ← path → {name, contextDir, lastUpdated}
24└── contexts/<name>/
25 ├── context.json ← SOURCE OF TRUTH (structured JSON, v2)
26 └── CONTEXT.md ← generated view — do not hand-edit
27```
28
29---
30
31## Commands
32
33### /ck:init — Register a Project
34```bash
35node "$HOME/.claude/skills/ck/commands/init.mjs"
36```
37The script outputs JSON with auto-detected info. Present it as a confirmation draft:
38```
39Here's what I found — confirm or edit anything:
40Project: <name>
41Description: <description>
42Stack: <stack>
43Goal: <goal>
44Do-nots: <constraints or "None">
45Repo: <repo or "none">
46```
47Wait for user approval. Apply any edits. Then pipe confirmed JSON to save.mjs --init:
48```bash
49echo '<confirmed-json>' | node "$HOME/.claude/skills/ck/commands/save.mjs" --init
50```
51Confirmed JSON schema: {"name":"...","path":"...","description":"...","stack":["..."],"goal":"...","constraints":["..."],"repo":"..." }
52
53---
54
55### /ck:save — Save Session State
56**This is the only command requiring LLM analysis.** Analyze the current conversation:
57- summary: one sentence, max 10 words, what was accomplished
58- leftOff: what was actively being worked on (specific file/feature/bug)
59- nextSteps: ordered array of concrete next steps
60- decisions: array of {what, why} for decisions made this session
61- blockers: array of current blockers (empty array if none)
62- goal: updated goal string **only if it changed this session**, else omit
63
64Show a draft summary to the user: "Session: '<summary>' — save this? (yes / edit)"
65Wait for confirmation. Then pipe to save.mjs:
66```bash
67echo '<json>' | node "$HOME/.claude/skills/ck/commands/save.mjs"
68```
69JSON schema (exact): {"summary":"...","leftOff":"...","nextSteps":["..."],"decisions":[{"what":"...","why":"..."}],"blockers":["..."]}
70Display the script's stdout confirmation verbatim.
71
72---
73
74### /ck:resume [name|number] — Full Briefing
75```bash
76node "$HOME/.claude/skills/ck/commands/resume.mjs" [arg]
77```
78Display output verbatim. Then ask: "Continue from here? Or has anything changed?"
79If user reports changes → run /ck:save immediately.
80
81---
82
83### /ck:info [name|number] — Quick Snapshot
84```bash
85node "$HOME/.claude/skills/ck/commands/info.mjs" [arg]
86```
87Display output verbatim. No follow-up question.
88
89---
90
91### /ck:list — Portfolio View
92```bash
93node "$HOME/.claude/skills/ck/commands/list.mjs"
94```
95Display output verbatim. If user replies with a number or name → run /ck:resume.
96
97---
98
99### /ck:forget [name|number] — Remove a Project
100First resolve the project name (run /ck:list if needed).
101Ask: "This will permanently delete context for '<name>'. Are you sure? (yes/no)"
102If yes:
103```bash
104node "$HOME/.claude/skills/ck/commands/forget.mjs" [name]
105```
106Display confirmation verbatim.
107
108---
109
110### /ck:migrate — Convert v1 Data to v2
111```bash
112node "$HOME/.claude/skills/ck/commands/migrate.mjs"
113```
114For a dry run first:
115```bash
116node "$HOME/.claude/skills/ck/commands/migrate.mjs" --dry-run
117```
118Display output verbatim. Migrates all v1 CONTEXT.md + meta.json files to v2 context.json.
119Originals are backed up as meta.json.v1-backup — nothing is deleted.
120
121---
122
123## SessionStart Hook
124
125The hook at ~/.claude/skills/ck/hooks/session-start.mjs must be registered in
126~/.claude/settings.json to auto-load project context on session start:
127
128```json
129{
130 "hooks": {
131 "SessionStart": [
132 { "hooks": [{ "type": "command", "command": "node \"~/.claude/skills/ck/hooks/session-start.mjs\"" }] }
133 ]
134 }
135}
136```
137
138The hook injects ~100 tokens per session (compact 5-line summary). It also detects
139unsaved sessions, git activity since last save, and goal mismatches vs CLAUDE.md.
140
141---
142
143## Rules
144- Always expand ~ as $HOME in Bash calls.
145- Commands are case-insensitive: /CK:SAVE, /ck:save, /Ck:Save all work.
146- If a script exits with code 1, display its stdout as an error message.
147- Never edit context.json or CONTEXT.md directly — always use the scripts.
148- If projects.json is malformed, tell the user and offer to reset it to {}.
149
In the file
SKILL.md627 words
Files1
LicenceMIT
Why you can read it

Nothing in a skill executes. The client loads the text and the model follows it, so a skill can be audited the way a runbook is — by reading it.

What it costs in context

Skills are not billed by the call. They are paid for in context: every token the instructions occupy is a token your code, your diff and your conversation cannot use. Here is what this one takes and when it takes it.

≈130
always loaded
The name and description, so the model knows the skill exists and when to reach for it.
1,095
on trigger
The instruction body, read only when the skill fires.
0.61%
of a 200k window
Ten skills this size would take about 6% of the window before you open a file.
050k100k150k200k context window

1.2k tokens, estimated from the bundle at four bytes to the token, held for the rest of the session once it triggers. Middling. Fine to keep on in a project where you use it weekly, worth unloading in one where you never do.

Servers bill, skills cost

A server charges by the month. A skill charges once per session, in context, and then keeps charging it for as long as the session lives.

Before and after

The same question, put to the same model twice: once as it comes, and once with these instructions loaded.

No worked example has been published for this skill yet.

Adoption
Installsnone yet
Ratingno reviews yet

The procedure it runs

The procedure has not been published here. It is in the skill’s own SKILL.md, which its author has not sent to the marketplace yet.

Prose, not code

These steps are written for a model to follow, not executed by a runtime. It can still be told to skip one, and it will say so when it does.

Servers it uses

None. This skill calls no MCP servers at all.

Everything it needs is in the instructions, so it works in a project with nothing connected — the model reads the file and changes how it works with what it can already reach.

It writes no files and reaches no network. All it changes is how the model reasons and writes.

What it asks for
Writes filesno
Network accessno

Read from the allowed-tools line of this skill’s own SKILL.md. A skill grants no permissions of its own — it can only ask for tools your client already has.

What it will not do

Every skill is narrow, and the useful ones say where they stop. These are the jobs this one is the wrong tool for.

What this skill is not for has not been published here. Nothing is implied by that: it is a section the author has not filled in.

What is in the bundle

1 file, 4.9 kB on disk. A bundle is text throughout: the instructions the model reads, plus the templates it fills in.

  • SKILL.md4.9 kB
What is not in it

No dependencies and nothing executable: a skill is text the agent reads, so the bundle is 1 file you can review in full before installing. The MIT licence covers the templates and examples as well as the instructions.

Install

Installing copies the bundle into your project. Nothing runs at install time — the files sit on disk until the model reads them.

$99 once
ck — Context Keeper · MIT · affaan-m
one-time
Price$99 once
LicenceMIT — the author’s, unchanged by this purchase
Paid throughStripe, once, on the card you add at the checkout
Keeps workingfor good — the files are yours once they are on disk
Updatesevery release of 2.x through this account

You can read the whole bundle before paying — the SKILL.md above is the product, not a preview of it. What the money buys is the delivery: the folder packaged and handed to your machine by key, every update its author ships, and our support if it does not do what this listing says. The terms of use are MIT, set by the author and unchanged by buying it here.

Payment runs through Stripe, on a page like this one rather than a redirect. Once there is an account it joins the same mcprush invoice as everything else you run, so there is never a second card to enter.

Which clients pick it up on their own

A skill is a folder of text. A client with a skills folder reads it without being told; everywhere else the same text works, it is just handed to the model rather than found.

Claude Code.claude/skills/
Claude Desktop
ChatGPT
Cursor.cursor/skills/
VS Code.github/skills/
Codex CLI.agents/skills/
Gemini CLI.gemini/skills/
Grok.grok/skills/
Zed.agents/skills/
Windsurf.windsurf/skills/
Agent SDK.claude/skills/
HTTP / API
This release
Version2.0.0
Publishedno release date on file
Price$99
Referenceaffaan-m/ck-context-keeper

Versions

v2.0.0 is what is on the shelf; no release here carries a date. Instructions change more often than APIs do — a skill can be rewritten entirely without anything it depends on moving.

v2.0.0
  • No earlier releases have been published to the marketplace.
Pinning

Put affaan-m/ck-context-keeper@2.0.0 in the install command to hold this exact version. Without the suffix you get whatever is current the day you install, and nothing moves under you afterwards.

Reviews

no reviews yet · no installs yet

Nobody has reviewed this skill yet. The rating is the mean of the reviews written here, so there is none until somebody writes the first.

Who can post

Only accounts that have had the skill installed for fourteen days, so a review is written after living with it rather than after reading it. Publishers may reply once.

Publisher
Servers0