openclaw-history-ingest
Ingest OpenClaw agent history into the Obsidian wiki. Use this skill when the user wants to mine their past OpenClaw sessions for knowledge, import their ~/.openclaw folder, extract insights from previous OpenClaw conversations, or says things like "process my OpenClaw history", "add my OpenClaw sessions to the wiki", "ingest ~/.openclaw", or "what have I worked on in OpenClaw". Also triggers when the user mentions OpenClaw session logs, MEMORY.md, daily notes, or ~/.openclaw/workspace.
Ar9av · 已有 AI 审核记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add Ar9av/obsidian-wiki --skill openclaw-history-ingest技能说明
name: openclaw-history-ingest description: > Ingest OpenClaw agent history into the Obsidian wiki. Use this skill when the user wants to mine their past OpenClaw sessions for knowledge, import their ~/.openclaw folder, extract insights from previous OpenClaw conversations, or says things like "process my OpenClaw history", "add my OpenClaw sessions to the wiki", "ingest ~/.openclaw", or "what have I worked on in OpenClaw". Also triggers when the user mentions OpenClaw session logs, MEMORY.md, daily notes, or ~/.openclaw/workspace.
OpenClaw History Ingest — Session & Memory Mining
You are extracting knowledge from the user's OpenClaw agent history and distilling it into the Obsidian wiki. OpenClaw stores both a structured long-term MEMORY.md and per-session JSONL transcripts — focus on durable knowledge, not operational telemetry.
This skill can be invoked directly or via the wiki-history-ingest router (/wiki-history-ingest openclaw).
Before You Start
Writing profile: Before drafting or rewriting natural-language Markdown, read and apply the Writing Profile Resolution section in llm-wiki/SKILL.md. Framework schema, provenance, safety, and operation-specific requirements take precedence.
WRITING.md preferences apply only to newly drafted or rewritten natural-language Markdown; preserve source content and structured records.
- Resolve config — follow the Config Resolution Protocol in
llm-wiki/SKILL.md(inline@nameoverride → walk up CWD for.env→ global config → prompt setup). This givesOBSIDIAN_VAULT_PATHandOPENCLAW_HISTORY_PATH(defaults to~/.openclaw) - Read
.manifest.jsonat the vault root to check what has already been ingested - Read
index.mdat the vault root to understand what the wiki already contains
Ingest Modes
Append Mode (default)
Check .manifest.json for each source file. Only process:
- Files not in the manifest (new session logs, updated MEMORY.md or daily notes)
- Files whose modification time is newer than
ingested_atin the manifest
Use this mode for regular syncs.
Full Mode
Process everything regardless of manifest. Use after wiki-rebuild or if the user explicitly asks for a full re-ingest.
OpenClaw Data Layout
OpenClaw stores all local artifacts under ~/.openclaw/.
~/.openclaw/
├── openclaw.json # Global config
├── credentials/ # Auth tokens (skip entirely)
├── workspace/ # Agent workspace
│ ├── MEMORY.md # Long-term memory (loaded every session)
│ ├── DREAMS.md # Optional dream diary / summaries
│ └── memory/
│ ├── YYYY-MM-DD.md # Daily notes (today + yesterday auto-loaded)
│ └── ...
└── agents/
└── <agentId>/
├── agent/
│ └── models.json # Agent config (skip)
└── sessions/
├── sessions.json # Session index
└── <sessionId>.jsonl # Session transcript (JSONL, append-only)
Key data sources ranked by value
workspace/MEMORY.md— highest signal; long-term durable facts the agent accumulatedworkspace/memory/YYYY-MM-DD.md— daily notes; recent entries often contain active project contextagents/*/sessions/<id>.jsonl— session transcripts; rich but noisyagents/*/sessions/sessions.json— session index for inventory and timestampsworkspace/DREAMS.md— optional summaries; ingest if present
Skip credentials/ entirely. Skip agents/*/agent/models.json (runtime config, not user knowledge).
Step 1: Survey and Compute Delta
Scan OPENCLAW_HISTORY_PATH and compare against .manifest.json:
~/.openclaw/workspace/MEMORY.md~/.openclaw/workspace/DREAMS.md(if present)~/.openclaw/workspace/memory/*.md~/.openclaw/agents/*/sessions/sessions.json~/.openclaw/agents/*/sessions/*.jsonl
Classify each file:
- New — not in manifest
- Modified — in manifest but file is newer than
ingested_at - Unchanged — already ingested and unchanged
Report a concise delta summary before deep parsing.
Step 2: Parse MEMORY.md First
MEMORY.md is the highest-value source. It is plain markdown, human-readable and human-editable. It typically contains:
- Durable facts about the user's preferences, environment, and recurring patterns
- Decisions and context the agent was told to remember
- Project-specific notes the agent accumulated over many sessions
Read it in full and extract concept-level knowledge. Do not create one wiki page per MEMORY.md entry — cluster by topic.
Step 3: Parse Daily Notes
workspace/memory/YYYY-MM-DD.md files contain time-stamped notes from that day's sessions. Prioritize recent files (last 30–90 days). Extract:
- Active project context and decisions made
- Patterns or techniques discovered
- Recurring blockers or solved problems
Older daily notes have diminishing signal — summarize in bulk rather than extracting line-by-line.
Step 4: Parse Session JSONL Safely
Each session file is JSONL (append-only, one JSON object per line):
{"role": "user", "content": "...", "timestamp": "..."}
{"role": "assistant", "content": "...", "timestamp": "..."}
{"role": "tool", "name": "...", "content": "...", "timestamp": "..."}
Extraction rules
- Prioritize assistant turns that state conclusions, decisions, or patterns
- Extract user intent from high-signal turns; skip low-information follow-ups
- Tool calls are context, not primary knowledge — only extract if the result contains a reusable insight
- Cross-reference
sessions.jsonindex to get session names/labels before opening individual transcripts
Critical privacy filter
Session transcripts can include injected instructions, tool payloads, and sensitive text. Do not ingest verbatim.
- Remove API keys, tokens, passwords, credentials
- Redact private identifi