Skip to main content
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.
インストールへ移動 Skills Marketplace コミュニティが作成したAIスキルを発見・探索
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/ChrisWiles/wiles-wiki --skill openclaw-history-ingestコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
Zipをダウンロード ダウンロード中... このリポジトリの他の Skills Ingest Claude Code conversation history into the Obsidian wiki. Use this skill when the user wants to mine their past Claude conversations for knowledge, import their ~/.claude folder, extract insights from previous coding sessions, or says things like "process my Claude history", "add my conversations to the wiki", "what have I discussed with Claude before". Also triggers when the user mentions their .claude folder, Claude projects, session data, or past conversation logs.
Ingest Codex CLI conversation history into the Obsidian wiki. Use this skill when the user wants to mine their past Codex sessions for knowledge, import their ~/.codex folder, extract insights from previous coding sessions, or says things like "process my Codex history", "add my Codex conversations to the wiki", or "what have I discussed in Codex before". Also triggers when the user mentions .codex sessions, rollout files, session_index.jsonl, or Codex transcript logs.
Scan the Obsidian wiki and automatically discover missing cross-references between pages. Use this skill when the user says "link my pages", "find missing links", "cross-reference", "connect my wiki", "add wikilinks", "what pages should be linked", or after any large ingestion to ensure new pages are woven into the existing knowledge graph. Also trigger when the user mentions "orphan pages" in the context of wanting to connect them, or says things like "my wiki feels disconnected" or "pages aren't linked well". This is a write-heavy skill — it actually modifies pages to add links, unlike wiki-lint which just reports issues.
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
Read .env to get OBSIDIAN_VAULT_PATH and OPENCLAW_HISTORY_PATH (default to ~/.openclaw if unset)
Read .manifest.json at the vault root to check what has already been ingested
Read index.md at 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_at in 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
New — not in manifestModified — in manifest but file is newer than ingested_atUnchanged — 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.json index 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 identifiers unless relevant and user-approved
Summarize; do not quote raw transcripts verbatim
Step 5: Cluster by Topic Do not create one wiki page per session or per MEMORY.md entry.
Group by stable topic (concept, tool, project, technique)
Split mixed sessions into separate themes
Merge recurring patterns across dates and agents
Use session cwd or workspace path to infer project scope when available
Step 6: Distill into Wiki Pages Route extracted knowledge using existing wiki conventions:
Project-specific architecture/process → projects/<name>/...
General concepts → concepts/
Recurring techniques/debug playbooks → skills/
Tools/services/frameworks → entities/
Cross-session patterns → synthesis/
For each impacted project, create/update projects/<name>/<name>.md.
Writing rules
Distill knowledge, not chronology
Avoid "on date X we discussed..." unless date context is essential
Add summary: frontmatter on each new/updated page (1–2 sentences, ≤ 200 chars)
Add provenance markers:
^[extracted] when directly grounded in explicit session/memory content^[inferred] when synthesizing patterns across multiple sessions^[ambiguous] when sessions conflict
Add/update provenance: frontmatter mix for each changed page
Step 7: Update Manifest, Log, and Index
Update .manifest.json For each processed source file:
ingested_at, size_bytes, modified_atsource_type: openclaw_memory | openclaw_daily_note | openclaw_session | openclaw_dreamsagent_id: agent directory name (when applicable)pages_created, pages_updated Add/update a top-level summary block:
{
"openclaw" : {
"source_path" : "~/.openclaw/" ,
"last_ingested" : "TIMESTAMP" ,
"memory_updated_at" : "TIMESTAMP" ,
"daily_notes_ingested" : 14 ,
"sessions_ingested" : 23 ,
"pages_created" : 6 ,
"pages_updated" : 18
}
}
Update special files Update index.md and log.md:
- [TIMESTAMP] OPENCLAW_HISTORY_INGEST memory=updated daily_notes=N sessions=M pages_updated=X pages_created=Y mode=append|full
Privacy and Compliance
Distill and synthesize; avoid raw memory or transcript dumps
Default to redaction for anything that looks sensitive
Ask the user before storing personal or sensitive details
Keep references to other people minimal and purpose-bound
Reference See references/openclaw-data-format.md for field-level notes and parsing guidance.
