Agent skill

Ck

Persistent per-project memory for Claude Code (Context Keeper) driven by deterministic Node.js /ck commands: init, save, resume, info, list, forget, and v1-to-v2 migrate, plus a SessionStart hook…

MITAuto-check passedAgent Workflows

Install Ck

skills CLI

$ npx skills add affaan-m/ECC --skill ck -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install affaan-m/ECC ck --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/affaan-m/ECC.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/ck .claude/skills/ck && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "ck" agent skill from https://github.com/affaan-m/ECC/tree/main/skills/ck into .claude/skills/ck/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ck", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/affaan-m/ECC/tree/main/skills/ck

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add affaan-m/ECC --skill ck -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install affaan-m/ECC ck --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/affaan-m/ECC.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/ck .agents/skills/ck && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "ck" agent skill from https://github.com/affaan-m/ECC/tree/main/skills/ck into .agents/skills/ck/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ck", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add affaan-m/ECC --skill ck -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install affaan-m/ECC ck --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/affaan-m/ECC.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/ck .cursor/skills/ck && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "ck" agent skill from https://github.com/affaan-m/ECC/tree/main/skills/ck into .cursor/skills/ck/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ck", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/affaan-m/ECC.git --path skills/ck

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add affaan-m/ECC --skill ck -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install affaan-m/ECC ck --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/affaan-m/ECC.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/ck .gemini/skills/ck && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "ck" agent skill from https://github.com/affaan-m/ECC/tree/main/skills/ck into .gemini/skills/ck/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ck", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install affaan-m/ECC ck

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add affaan-m/ECC --skill ck -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/affaan-m/ECC.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/ck .github/skills/ck && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "ck" agent skill from https://github.com/affaan-m/ECC/tree/main/skills/ck into .github/skills/ck/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ck", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add affaan-m/ECC --skill ck -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install affaan-m/ECC ck --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/affaan-m/ECC.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/ck .opencode/skills/ck && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "ck" agent skill from https://github.com/affaan-m/ECC/tree/main/skills/ck into .opencode/skills/ck/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ck", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: ck
GitHub stars: 277k
Used in: 1 other repo
Token cost: ~1.2k tokens
SKILL.md length: 384 words
Files: 10
Skills in repo: 683
Repo updated: Oct 11, 2026
First seen: Oct 9, 2026
Licence: MIT

At a glance

Persistent per-project memory for Claude Code (Context Keeper) driven by deterministic Node.js /ck commands: init, save, resume, info, list, forget, and v1-to-v2 migrate, plus a SessionStart hook…

Context must survive across sessions
SKILL.md covers Data Layout, Commands, SessionStart Hook and Rules
Runs JavaScript scripts from its folder; calls node
Saving session state with next steps and decisions

What it does

Ck is an agent skill from affaan-m/ECC. Persistent per-project memory for Claude Code (Context Keeper) driven by deterministic Node.js /ck commands: init, save, resume, info, list, forget, and v1-to-v2 migrate, plus a SessionStart hook that injects a compact project brief. Use when context must survive across sessions, saving session state with next steps and decisions, resuming where a previous session left off, or picking up a project without re-explaining it.

Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 11 other files.

It sits in Agent Workflows, covering Session handoff and Agent memory. It works with Node.js. The repository describes itself as: The agent harness performance optimization system. Skills, instincts, memory, security, and research-first development for Claude Code, Codex, Opencode, Cursor and beyond. The licence is MIT.

When your agent uses it

Context must survive across sessions
Saving session state with next steps and decisions
Resuming where a previous session left off
Picking up a project without re-explaining it

Example prompts

“/ck”

Requirements

Node.js

What it can do on your machine

Read from SKILL.md and the folder at commit 2d515e4. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships script files (JavaScript), which the agent can run.
Shell commands in SKILL.md call:
- node
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Ck loads about 1.2k tokens when it runs. Until then it costs about 107 tokens; SKILL.md has 384 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~107
When it runs · the whole SKILL.md, loaded when a task matches: ~1.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from affaan-m/ECC at commit 2d515e4, republished under its MIT licence (© affaan-m). 384 words, ~1,238 tokens.

Download SKILL.mdSave it as .claude/skills/ck/SKILL.md (or your agent's skills folder). This skill also uses 9 other files; get the full folder from GitHub.

name: ck
description: Persistent per-project memory for Claude Code (Context Keeper) driven by deterministic Node.js /ck commands: init, save, resume, info, list, forget, and v1-to-v2 migrate, plus a SessionStart hook that injects a compact project brief. Use when context must survive across sessions, saving session state with next steps and decisions, resuming where a previous session left off, or picking up a project without re-explaining it.
metadata.version: 2.0.0
metadata.origin: community
author: sreedhargs89
repo: https://github.com/sreedhargs89/context-keeper

ck — Context Keeper

You are the Context Keeper assistant. When the user invokes any /ck:* command, run the corresponding Node.js script and present its stdout to the user verbatim. Scripts live at: ~/.claude/skills/ck/commands/ (expand ~ with $HOME).

Data Layout

~/.claude/ck/
├── projects.json              ← path → {name, contextDir, lastUpdated}
└── contexts/<name>/
    ├── context.json           ← SOURCE OF TRUTH (structured JSON, v2)
    └── CONTEXT.md             ← generated view — do not hand-edit

Commands

`/ck:init` — Register a Project

bash

node "$HOME/.claude/skills/ck/commands/init.mjs"

The script outputs JSON with auto-detected info. Present it as a confirmation draft:

Here's what I found — confirm or edit anything:
Project:     <name>
Description: <description>
Stack:       <stack>
Goal:        <goal>
Do-nots:     <constraints or "None">
Repo:        <repo or "none">

Wait for user approval. Apply any edits. Then pipe confirmed JSON to save.mjs --init:

bash

echo '<confirmed-json>' | node "$HOME/.claude/skills/ck/commands/save.mjs" --init

Confirmed JSON schema: {"name":"...","path":"...","description":"...","stack":["..."],"goal":"...","constraints":["..."],"repo":"..." }

`/ck:save` — Save Session State

This is the only command requiring LLM analysis. Analyze the current conversation:

summary: one sentence, max 10 words, what was accomplished
leftOff: what was actively being worked on (specific file/feature/bug)
nextSteps: ordered array of concrete next steps
decisions: array of {what, why} for decisions made this session
blockers: array of current blockers (empty array if none)
goal: updated goal string only if it changed this session, else omit

Show a draft summary to the user: "Session: '<summary>' — save this? (yes / edit)" Wait for confirmation. Then pipe to save.mjs:

bash

echo '<json>' | node "$HOME/.claude/skills/ck/commands/save.mjs"

JSON schema (exact): {"summary":"...","leftOff":"...","nextSteps":["..."],"decisions":[{"what":"...","why":"..."}],"blockers":["..."]} Display the script's stdout confirmation verbatim.

`/ck:resume [name|number]` — Full Briefing

bash

node "$HOME/.claude/skills/ck/commands/resume.mjs" [arg]

Display output verbatim. Then ask: "Continue from here? Or has anything changed?" If user reports changes → run /ck:save immediately.

`/ck:info [name|number]` — Quick Snapshot

bash

node "$HOME/.claude/skills/ck/commands/info.mjs" [arg]

Display output verbatim. No follow-up question.

`/ck:list` — Portfolio View

bash

node "$HOME/.claude/skills/ck/commands/list.mjs"

Display output verbatim. If user replies with a number or name → run /ck:resume.

Show full SKILL.md (159 more words)Show less

`/ck:forget [name|number]` — Remove a Project

First resolve the project name (run /ck:list if needed). Ask: "This will permanently delete context for '<name>'. Are you sure? (yes/no)" If yes:

bash

node "$HOME/.claude/skills/ck/commands/forget.mjs" [name]

Display confirmation verbatim.

`/ck:migrate` — Convert v1 Data to v2

bash

node "$HOME/.claude/skills/ck/commands/migrate.mjs"

For a dry run first:

bash

node "$HOME/.claude/skills/ck/commands/migrate.mjs" --dry-run

Display output verbatim. Migrates all v1 CONTEXT.md + meta.json files to v2 context.json. Originals are backed up as meta.json.v1-backup — nothing is deleted.

SessionStart Hook

The hook at ~/.claude/skills/ck/hooks/session-start.mjs must be registered in ~/.claude/settings.json to auto-load project context on session start:

json

{
  "hooks": {
    "SessionStart": [
      { "hooks": [{ "type": "command", "command": "node \"~/.claude/skills/ck/hooks/session-start.mjs\"" }] }
    ]
  }
}

The hook injects ~100 tokens per session (compact 5-line summary). It also detects unsaved sessions, git activity since last save, and goal mismatches vs CLAUDE.md.

Rules

Always expand ~ as $HOME in Bash calls.
Commands are case-insensitive: /CK:SAVE, /ck:save, /Ck:Save all work.
If a script exits with code 1, display its stdout as an error message.
Never edit context.json or CONTEXT.md directly — always use the scripts.
If projects.json is malformed, tell the user and offer to reset it to {}.

Files

SKILL.md and 9 other files in skills/ck of affaan-m/ECC.

SKILL.md
commands/forget.mjs
commands/info.mjs
commands/init.mjs
commands/list.mjs
commands/migrate.mjs
commands/resume.mjs
commands/save.mjs
commands/shared.mjs
hooks/session-start.mjs

Open the folder on GitHubat commit 2d515e4

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in affaan-m/ECC, which our catalogue first saw on October 9, 2026.

Sidiora-Labs/centra-llm-agentsprotocol/skills/ck

Compare with similar skills

Ck next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Ck compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Ck this skillaffaan-m/ECC	277k	1 repos	~1.2k	Automated safety check: Pass	MIT	today
Beads Task Memorygastownhall/beads	28k	—	~1.2k	Automated safety check: Pass	MIT	today
Session History Searchslopus/happy	24k	—	~3.1k	Automated safety check: Pass	MIT	today
Memori Long-Term MemoryMemoriLabs/Memori	17k	—	~2k	Automated safety check: Notes	Custom licence	8 days ago
agentmemory Setup and Diagnosticsrohitg00/agentmemory	29k	—	~1k	Automated safety check: Notes	Apache-2.0	yesterday
Coding Agent Session Findercode-yeongyu/oh-my-openagent	70k	—	~2.8k	Automated safety check: Pass	Custom licence	today

Similar skills

Beads Task Memory
gastownhall/beads
Tracks multi-session work with dependencies in the bd issue tracker so the agent can find ready tasks and recover its context after conversation compaction.
28k GitHub stars~1.2k tokensUpdated today
Agent WorkflowsAuto-check passed
Session History Search
slopus/happy
Searches past Claude Code, Codex and Cursor sessions and summarizes what was worked on, tried or decided, using extraction scripts instead of reading raw logs.
24k GitHub stars~3.1k tokensUpdated today
Agent WorkflowsAuto-check passed
Memori Long-Term Memory
MemoriLabs/Memori
Connects Claude Code to Memori Cloud for long-term memory, recalling stored context before substantive replies and saving new context afterward.
17k GitHub stars~2k tokensUpdated 8 days ago
Agent WorkflowsAuto-check: notes
agentmemory Setup and Diagnostics
rohitg00/agentmemory
Sets up and troubleshoots a local agentmemory install, covering the MCP connection, environment variables, ports, authentication and optional feature flags.
29k GitHub stars~1k tokensUpdated yesterday
Agent WorkflowsAuto-check: notes
Coding Agent Session Finder
code-yeongyu/oh-my-openagent
Finds, reads and reconstructs past coding-agent sessions across Codex, Claude, OpenCode, Senpi and many other local agent logs.
70k GitHub stars~2.8k tokensUpdated today
Agent WorkflowsAuto-check passed
Memori MCP Memory Usage
MemoriLabs/Memori
Teaches an MCP-connected agent when and how to call Memori's recall, summary, compaction, augmentation, feedback and quota tools to keep context across sessions.
17k GitHub stars~3.8k tokensUpdated 8 days ago
Agent WorkflowsAuto-check passed

Questions about Ck

What does Ck do?

Persistent per-project memory for Claude Code (Context Keeper) driven by deterministic Node.js /ck commands: init, save, resume, info, list, forget, and v1-to-v2 migrate, plus a SessionStart hook…. Ck is an agent skill from affaan-m/ECC.js /ck commands: init, save, resume, info, list, forget, and v1-to-v2 migrate, plus a SessionStart hook that injects a compact project brief.

When should I use Ck?

Ck fits situations like: context must survive across sessions; saving session state with next steps and decisions; resuming where a previous session left off; picking up a project without re-explaining it.

How do I install Ck in Claude Code?

Run `npx skills add affaan-m/ECC --skill ck -a claude-code`. Or copy the skill folder (skills/ck in affaan-m/ECC) into .claude/skills/ck in your project. Claude Code loads it when a task matches its description.

How do I install Ck in Codex?

Run `npx skills add affaan-m/ECC --skill ck -a codex`. Or copy the skill folder (skills/ck in affaan-m/ECC) into .agents/skills/ck in your project. Codex loads it when a task matches its description.

Can I use Ck in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add affaan-m/ECC --skill ck -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/ck, .gemini/skills/ck, .github/skills/ck and .opencode/skills/ck in your project.

What does Ck need to run?

Going by SKILL.md and its folder, Ck needs JavaScript for the scripts in its folder and the command-line tools its instructions call (node). Our summary lists: Node.js.

Does Ck access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Ck safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Ck use?

Ck is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Ck use?

About 1.2k tokens (SKILL.md is roughly 5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Ck?

Skills that share tags, products or a category with Ck: Beads Task Memory (gastownhall/beads, 28k stars), Session History Search (slopus/happy, 24k stars), Memori Long-Term Memory (MemoriLabs/Memori, 17k stars) and agentmemory Setup and Diagnostics (rohitg00/agentmemory, 29k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Ck?

affaan-m (a GitHub user) maintains it in affaan-m/ECC, which has 276,673 GitHub stars. The repository holds 683 skills in this directory. The repository was last updated on October 11, 2026.

Source: affaan-m/ECC on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Ck

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

ck — Context Keeper

Data Layout

Commands

/ck:init — Register a Project

/ck:save — Save Session State

/ck:resume [name|number] — Full Briefing

/ck:info [name|number] — Quick Snapshot

/ck:list — Portfolio View

/ck:forget [name|number] — Remove a Project

/ck:migrate — Convert v1 Data to v2

SessionStart Hook

Rules

Files

Used in 1 other repository

Compare with similar skills

Similar skills

More from affaan-m/ECC

Related

Questions about Ck

`/ck:init` — Register a Project

`/ck:save` — Save Session State

`/ck:resume [name|number]` — Full Briefing

`/ck:info [name|number]` — Quick Snapshot

`/ck:list` — Portfolio View

`/ck:forget [name|number]` — Remove a Project

`/ck:migrate` — Convert v1 Data to v2