Claude 助手
- 作者仓库星标 62
- 作者更新于 实时读取
- 作者仓库 skills
- 领域
- 通用
- 兼容 Agent
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- 信任分
- 88 / 100 · 社区维护
- 作者 / 版本 / 许可
- @TerminalSkills · 未声明 license
- Token 消耗评级
- 低消耗
- 接入复杂程度
- 需简单配置
- 是否需要外部 API Key
- 需要 · Vendor-specific
- 兼容的系统
- macOS · Linux · Windows
- 底层运行要求
- 无特殊要求
- 文件与系统权限
-
- 只读
- 允许写入 / 修改
- 网络行为
- 允许外网请求
- 安装命令数
- 26 条
档案由构建时根据 SKILL.md 与安装命令自动衍生,可能与作者实际意图存在差异。
需要注意: 未限定 allowed-tools,默认拥有全部工具权限。
---
name: claude-mem
description: >- Claude Code forgets everything between sessions. Two open-source tools solve this by automati…
category: 通用
runtime: 无特殊运行时
---
# claude-mem 输出预览
## PART A: 任务判断
- 适用问题:通用任务拆解、检查和交付。
- 输入要求:目标材料、限制条件、期望输出和验收方式。
- 证据边界:围绕“Overview / Instructions / Option A: claude-mem (Local AI Compression)”读取原文规则,不把推断写成作者承诺。
## PART B: 执行结果
- **01** 任务判断:确认你的需求是否属于通用任务拆解、检查和交付,并标出输入、限制和预期结果。
- **02** 执行计划:优先按“Overview / Instructions / Option A: claude-mem (Local AI Compression)”拆成步骤,说明每一步会读取什么、修改什么、产出什么。
- **03** 交付结果:给出可复制的命令、文件改动、检查清单或内容草稿,并说明如何继续迭代。
- **04** 风险边界:结合 读取文件、写入/修改文件、会按任务需要访问外部网络、需要准备 Vendor-specific API Key 给出执行前确认项。
## Running Rules
- 读取文件、写入/修改文件;会按任务需要访问外部网络;需要准备 Vendor-specific API Key。
- 先小样例验证,再放大到真实任务。
- 交付时同时给结果、检查口径和下一步迭代建议。 原文出现了 `/plugin` 这类斜杠命令;如果你的 Agent 支持命令触发,优先用命令开场,再补充目标和边界。
告诉 Agent 目标文件或材料、期望结果、不可改范围、是否允许联网或执行命令。本 Skill 的权限画像是:读取文件、写入/修改文件。
先用一个小任务确认它会围绕“Overview / Instructions / Option A: claude-mem (Local AI Compression)”工作;涉及文件或命令时,先看 diff、日志、预览或测试结果。
检查最终产物是否包含明确结果、必要证据和下一步动作;如果输出泛泛而谈,就补充输入、边界和验收标准后重跑。
---
name: claude-mem
description: >- Claude Code forgets everything between sessions. Two open-source tools solve this by automati…
category: 通用
source: TerminalSkills/skills
---
# claude-mem
## 什么时候使用
- claude-mem 是一个通用扩展技能,按 SKILL 适合处理通用任务拆解、检查、交付和复盘,核心价值是把输入、判断、执行、验证和交付边界固定下来,避免 Agent 泛泛回答。 把任务拆成可执行、可检查、可继续迭代的步骤;使用前要准…
- 面向通用任务拆解、检查和交付,优先处理能明确输入、步骤和验收标准的工作。
## 需要提供什么
- 目标材料、目录范围、期望结果和不可改动内容。
- 是否允许联网、执行命令、读写文件或调用外部服务。
## 执行规则
- 围绕「Overview / Instructions / Option A: claude-mem (Local AI Compression)」组织步骤,不把推断写成作者事实。
- 读取文件、写入/修改文件;会按任务需要访问外部网络;需要准备 Vendor-specific API Key。
- 先跑小样例,确认结果可检查后再扩大任务范围。
## 输出要求
- 给出最终产物、关键证据、验证方式和下一步动作。
- 信息不足时标记 unknown,不编造命令、平台或依赖。 作者原文负责流程事实;仓库文件负责来源和命令;流狐只补充适用场景、限制和质量判断。
skill "claude-mem" {
输入层 -> 用户目标 + 目标文件 + 禁止范围 + 验收标准
上下文层 -> Overview / Instructions / Option A: claude-mem (Local AI Compression)
规则层 -> SKILL.md 触发条件 / 执行顺序 / 输出格式
运行层 -> 无特殊运行时 | 读取文件、写入/修改文件 | 会按任务需要访问外部网络
安全层 -> 需要准备 Vendor-specific API Key + 小任务验证 + diff / 日志复核
输出层 -> 可复制结果 + 检查清单 + 下一步迭代
} Claude Code Persistent Memory
Overview
Claude Code forgets everything between sessions. Two open-source tools solve this by automatically capturing context and injecting it into future sessions:
- claude-mem — captures session activity, compresses it with AI, injects relevant memories on next session. Lightweight, local-first.
- Claude Subconscious — a background Letta agent that watches sessions, builds up memory over time, and whispers guidance back. Cloud or self-hosted.
Both eliminate the need to re-explain context when returning to a project.
Instructions
Option A: claude-mem (Local AI Compression)
GitHub: thedotmack/claude-mem
Setup
npm install -g claude-mem
cd your-project
claude-mem init
claude-mem setup-hooks
This creates .claude-mem/ with config, compressed memories, and an index. Hooks auto-capture after each session and auto-inject before the next.
How It Works
- Capture — hooks into Claude Code session, records interactions
- Compress — AI summarizes session into structured memory (decisions, code changes, learnings)
- Store — compressed memories saved to
.claude-mem/directory - Retrieve — on new session, relevant memories injected into context
Commands
claude-mem capture # Capture current session
claude-mem inject # Inject memories into context
claude-mem search "auth flow" # Semantic search through memories
claude-mem list # List all memories
claude-mem stats # Show memory stats
claude-mem compress # Reduce storage for old memories
Configuration
{
"compression": {
"model": "claude-sonnet-4-20250514",
"strategy": "smart"
},
"inject": {
"maxMemories": 10,
"relevanceThreshold": 0.7,
"strategy": "semantic"
}
}
Strategies: smart (AI picks what's important), full (captures everything), minimal (only decisions and errors).
Option B: Claude Subconscious (Letta Background Agent)
GitHub: letta-ai/claude-subconscious
Setup
/plugin marketplace add letta-ai/claude-subconscious
/plugin install claude-subconscious@claude-subconscious
export LETTA_API_KEY="your-api-key"
Get your API key from app.letta.com. Or self-host:
pip install letta
letta server --port 8283
export LETTA_BASE_URL="http://localhost:8283"
Modes
| Mode | Behavior | Token Cost |
|---|---|---|
whisper (default) |
Short guidance before each prompt | Low |
full |
Full memory blocks + message history | Higher |
off |
Disabled | None |
Which to Choose
| claude-mem | Claude Subconscious | |
|---|---|---|
| Storage | Local files (.claude-mem/) | Letta cloud or self-hosted |
| Cost | Uses your Claude API for compression | Requires Letta API key (free tier) |
| Latency | Near-zero (local) | ~1-2s per whisper |
| Memory style | Compressed session summaries | Continuous learning agent |
| Best for | Local-first, privacy-sensitive | Rich cross-session context |
Examples
Example 1: Session Continuity with claude-mem
# Session 1: Work on auth module
$ claude-mem stats
Memories: 12 | Storage: 45KB | Last capture: 2 hours ago
# Session 2: Return to project — auto-injected context
# Claude already knows: "You implemented JWT auth with RS256, refresh tokens in Redis"
Example 2: Architecture Recall with Subconscious
After discussing a REST-to-GraphQL migration, you start a new session:
[subconscious] Last session you decided to switch from REST to GraphQL for the
user service. Migration is 60% done — resolvers for User and Project are complete,
Order and Payment still need conversion. You preferred code-first schema with TypeGraphQL.
Guidelines
- Pair with CLAUDE.md — use CLAUDE.md for static project context, persistent memory for dynamic decisions
- One tool per project — don't run both claude-mem and Subconscious simultaneously
- For claude-mem: set
relevanceThresholdhigher (0.8+) if too much context is injected - For Subconscious:
whispermode gives 90% of the value at lower token cost - Add
.claude-mem/memories/to.gitignorefor private projects - Memory quality depends on session length — short sessions produce less useful memories
先判断是否适合
作者设计意图
作者的方法与取舍
边界和复核