This entry duplicates how-it-works, which is the one we list in search.

how-it-works

Explain how claude-mem captures observations, when memory injection kicks in, and where data lives.

Skill by longhang2004

IndexedMIT

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/longhang2004-how-it-works

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

About

Explain how claude-mem captures observations, when memory injection kicks in, and where data lives. Use when the user asks "how does claude-mem work?" or "what is this thing doing?".

Use cases: data

Reviews

Write a review

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions: not checked yet.

What's inside

Skill name: how-it-works
Description: Explain how claude-mem captures observations, when memory injection kicks in, and where data lives. Use when the user asks "how does claude-mem work?" or "what is this thing doing?".
License: MIT
Instructions: 19 lines in SKILL.md · view on GitHub

Files (2)

SKILL.md
onboarding-explainer.md

SKILL.md (first lines)

# How claude-mem works

## What it does

Every Read, Edit, and Bash that Claude makes turns into a compressed observation. Observations get summarized at session end. Relevant ones get auto-injected into future prompts so the next session starts with context from the last one — no re-explaining the codebase, no re-discovering decisions.

## When it kicks in

Memory injection starts on your second session in a project.

The first session in a fresh project seeds memory; subsequent sessions receive auto-injected context for relevant past work. Run `/learn-codebase` if you want to front-load the entire repo into memory in a single pass (~5 minutes, optional).

## Where data lives

Everything stays in ~/.claude-mem on this machine.

Nothing leaves your machine except calls to whichever AI provider you configured for compression (Claude / OpenRouter / Gemini). The SQLite database, vector index, logs, and settings all live under that directory and are removed cleanly on `npx claude-mem uninstall`.

From longhang2004/Tenvyr, MIT.

Signals

Stars: 0
Forks: 0
Open issues: 0
Last commit (this folder): Jul 28, 2026 (3 months ago)

From GitHub (fetched Oct 24, 2026).

Details

License: MIT
Repository: github.com/longhang2004/Tenvyr
First seen: Oct 24, 2026
Last checked: Oct 24, 2026
Source: GitHub github-graphql

Same skill elsewhere

Copies of this SKILL.md published by others; search shows only one of them.

0.879score
how-it-works
thedotmack
Explain how claude-mem captures observations, when memory injection kicks in, and where data lives.
SkillAFreshness: A★ 102.8KClaude Code +9