agentleFS
catlog22catlog22/Claude-Code-Workflow/.claude/skills/memory-capture/SKILL.md

memory-capture

Skill2.1k starsChanged 7 months agoMITArchived repositoryView on GitHub

Unified memory capture with routing - session compact or quick tips. Triggers on "memory capture", "compact session", "save session", "quick tip", "memory tips", "记录", "压缩会话".

4 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Single Phase Execution: Only ONE phase executes per invocation - never both

    line 90
  2. Distinctive:

    Absolute Paths: All file paths in output must be absolute

    line 92

“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Memory Capture Skill

Unified memory capture skill that routes to two execution modes:

  • Compact: Compress full session memory into structured text for recovery
  • Tips: Quick note-taking for ideas, snippets, and insights

Architecture Overview

┌─────────────────────────────────────────────────────┐
│  Memory Capture (Router)                            │
│  → Parse input → Detect mode → Route to phase       │
└───────────────┬─────────────────────────────────────┘
                │
        ┌───────┴───────┐
        ↓               ↓
  ┌───────────┐   ┌───────────┐
  │  Compact  │   │   Tips    │
  │  (Phase1) │   │  (Phase2) │
  │  Full     │   │  Quick    │
  │  Session  │   │  Note     │
  └─────┬─────┘   └─────┬─────┘
        │               │
        └───────┬───────┘
                ↓
        ┌───────────────┐
        │  core_memory  │
        │   (import)    │
        └───────────────┘

Execution Flow

Step 1: Parse Input & Route

Detect execution mode from user input:

Auto-Route Rules (priority order):

SignalRouteExamples
Keyword: compact, session, 压缩, recovery, 保存会话→ Compact"compact current session"
Keyword: tip, note, 记录, 快速→ Tips"记录一个想法"
Has --tag or --context flags→ Tips"note content" --tag bug
Short text (<100 chars) + no session keywords→ Tips"Remember to use Redis"
Ambiguous or no arguments→ AskUserQuestion/memory-capture

When ambiguous, use AskUserQuestion:

Question: "选择记忆捕获模式"
Options:
  1. Compact - 压缩当前完整会话记忆(用于会话恢复)
  2. Tips - 快速记录一条笔记/想法/提示

Step 2: Execute Selected Phase

Based on routing result, read and execute the corresponding phase:

  • Compact mode → Ref: phases/01-compact.md
  • Tips mode → Ref: phases/02-tips.md

Phase Reference Documents (read on-demand when phase executes):

ModeDocumentPurpose
Compactphases/01-compact.mdFull session memory compression and structured export
Tipsphases/02-tips.mdQuick note-taking with tags and context

Step 3: Save via core_memory

Both phases converge on the same storage mechanism:

mcp__ccw-tools__core_memory({
  operation: "import",
  text: structuredText  // Generated by the selected phase
})

Core Rules

  1. Single Phase Execution: Only ONE phase executes per invocation - never both
  2. Content Faithful: Phase files contain full execution detail - follow them verbatim
  3. Absolute Paths: All file paths in output must be absolute
  4. No Summarization: Compact mode preserves complete plan verbatim - never abbreviate
  5. Speed Priority: Tips mode should be fast - minimal analysis overhead

Input Processing

Compact Mode Input

  • Optional: "session description" as supplementary context
  • Example: /memory-capture compact or /memory-capture "completed auth module"

Tips Mode Input

  • Required: <note content> - the tip/note text
  • Optional: --tag <tag1,tag2> for categorization
  • Optional: --context <context> for related code/feature reference
  • Example: /memory-capture tip "Use Redis for rate limiting" --tag config

Data Flow

User Input
    │
    ├─ [compact detected] → Read phases/01-compact.md
    │                        → Analyze session → Generate structured text
    │                        → core_memory import → Report Recovery ID
    │
    └─ [tips detected] → Read phases/02-tips.md
                         → Parse args → Gather context → Generate tip text
                         → core_memory import → Confirm with ID + tags

Error Handling

ErrorAction
core_memory import failsRetry once, then report error with structured text for manual save
No session context (compact)Warn user, generate with available info
Empty note content (tips)Ask user to provide content via AskUserQuestion
Ambiguous routingDefault to AskUserQuestion - never guess

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.