Route requests to import AI-agent history into a wiki to the appropriate specialist skill. It identifies the source from an agent name or history path, and asks a short question when the intended source is unclear.
中文简介正在准备中。当前显示英语简介。
Route generic agent-history ingestion requests to the appropriate specialized history-ingest skill. Use when the user asks to ingest AI-agent history without directly selecting the underlying agent-specific skill.
实测评分 未实测
查看安装方法安装前可以查看交给 AI 代理的指令内容。
This is a thin router for history sources only. It does not replace wiki-ingest for documents.
If the user invokes /wiki-history-ingest <target> (or equivalent text command), dispatch directly:
| Subcommand | Route To |
|---|---|
claude | claude-history-ingest |
copilot | copilot-history-ingest |
codex | codex-history-ingest |
hermes | hermes-history-ingest |
openclaw | openclaw-history-ingest |
pi | pi-history-ingest |
auto | infer from context using rules below |
claude, copilot, codex, hermes, openclaw, or pi, route directly.~/.claude or Claude memory/session JSONL artifacts -> claude-history-ingest~/.copilot, session-store.db, VS Code copilot-chat transcripts -> copilot-history-ingest~/.codex or rollout/session index artifacts -> codex-history-ingest~/.hermes or Hermes memories/session artifacts -> hermes-history-ingest~/.openclaw or OpenClaw MEMORY.md/session JSONL artifacts -> openclaw-history-ingest~/.pi/agent/sessions or Pi session JSONL artifacts -> pi-history-ingestclaude, copilot, codex, hermes, openclaw, or pi history?"wiki-ingest for documents/content sourceswiki-history-ingest for agent history sourcesExamples:
/wiki-history-ingest claude/wiki-history-ingest copilot/wiki-history-ingest codex/wiki-history-ingest hermes/wiki-history-ingest openclaw/wiki-history-ingest pi$wiki-history-ingest claude (agents that use $skill invocation)$wiki-history-ingest copilot还没有评价。欢迎分享你的使用感受。
无需登录即可发表。欢迎分享使用感受、提问，或说明在哪些环境下无法运行。
还没有评论。来写第一条吧。
Extract reusable knowledge from Claude Code conversations, memory files, and desktop agent audit logs. Organize findings by topic in Obsidian, preserving source attribution and distinguishing project details from patterns shared across projects.
中文简介正在准备中。当前显示英语简介。
Explore an unfamiliar codebase before editing it. Produce a ranked map of important files, functions, callers, and dependencies, with source locations and evidence types to guide code reading and assess the likely impact of changes.
中文简介正在准备中。当前显示英语简介。
Extract reusable knowledge from Codex CLI conversation and session logs, then organize it into topic-based Obsidian wiki pages. Combine insights across sessions, process new or changed files, and remove sensitive information rather than copying raw transcripts.
中文简介正在准备中。当前显示英语简介。
Turn GitHub Copilot CLI and VS Code conversation history into topic-based Obsidian wiki pages. Extract decisions, debugging approaches, and project knowledge from summaries, conversations, and saved notes, processing only new or changed sessions by default.
中文简介正在准备中。当前显示英语简介。
Find missing references between wiki pages using names, aliases, shared tags, and project context. Add links in the text or a related section, record relationship types, and report confidence levels and pages that remain disconnected.
中文简介正在准备中。当前显示英语简介。
Maintain an Obsidian wiki by checking source freshness, updating its index and activity summary, and recording maintenance status. Set up a daily 9 AM schedule and optional terminal reminders for overdue updates.
中文简介正在准备中。当前显示英语简介。