wiki-history-ingest

Name: wiki-history-ingest
Author: ar9av

github.com/ar9avProductivity3.6k3.2k installsUpdated 2d ago

About wiki-history-ingest

wiki-history-ingest routes agent history sources to the matching ingest skill. It handles history only and does not replace wiki-ingest for documents.

Key features

01Routes to six source-specific ingest skills
02Infers the source from context
03Requests clarification when the source is ambiguous
04Separates agent history from document ingestion

Use cases

01Ingest Claude or Codex conversations
02Choose a workflow from Copilot or Pi paths
03Clarify an uncertain history source

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/ar9av/obsidian-wiki --skill wiki-history-ingest

After installing, type/wiki-history-ingestin Claude Code to confirm it loaded.

Details

From the project README

Unified History Ingest Router

This is a thin router for history sources only. It does not replace wiki-ingest for documents.

Subcommands

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

Routing Rules

If the user explicitly says claude, copilot, codex, hermes, openclaw, or pi, route directly.
If the user provides a path/source:
- ~/.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-ingest
If ambiguous, ask one short clarification:
- "Should I ingest claude, copilot, codex, hermes, openclaw, or pi history?"

Execution Contract

After routing, execute the destination skill's workflow exactly.
Do not duplicate destination logic in this file.
Leave manifest/index/log update semantics to the destination skill.

UX Convention

Use wiki-ingest for documents/content sources
Use wiki-history-ingest for agent history sources

Examples:

/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

Comments

Markdown supported

Details

Author: ar9av
Repository: ar9av/obsidian-wiki
Category: Productivity
Installs: 3,188
GitHub stars: 3,633

Report

More skills

All skills

lark-base

open.feishu.cn

823.2k

Operate on Feishu Base: create tables, fields, records, and views; handle statistics, formulas/lookups, forms, dashboards, app mode (BaseApp/AppMode pages and components), Workspace directories, workflows, role permissions, and the template center (Base template categories, lists, and search). Use when encountering Base/multidimensional tables/bitable, BaseApp/AppMode, or /base/ or /app/ links. Do not use lark-apps for BaseApp; route file import/export to lark-drive and authentication/authorization to lark-shared.

lark-drive

open.feishu.cn

823.2k

Feishu cloud storage (Drive): manage Drive files and folders, including uploads/downloads, folder creation, copying/moving/deleting, viewing metadata, checking permission settings, comments/permissions/subscriptions, titles, versions, Feishu document security labels (secure labels), and local file imports. Use when users need to organize Drive folders, handle cloud storage resource URLs/tokens, identify link types/actual tokens/titles, or import Word/Markdown/Excel/CSV/PPTX/.base as docx/sheet/bitable/slides. Route doubao.com cloud storage URLs/tokens by resource path and token too; do not fall back to WebFetch. Not responsible for: editing document content (use lark-doc), spreadsheet/Base table data operations (use lark-sheets/lark-base), knowledge space node/member management (use lark-wiki), or native Markdown file read/write/patch/diff (use lark-markdown).

lark-shared

open.feishu.cn

822.9k

Use for lark-cli setup/auth tasks: auth login/status/logout, user vs bot identity, business-domain permissions (--domain, including all/docs/drive), missing scopes, revoking authorization, or handling _notice JSON.

lark-im

open.feishu.cn

822.3k

Feishu instant messaging: send and receive messages and manage group chats. Send and reply to messages, search chat history, manage group members, upload and download images and files, manage emoji reactions, send urgent notifications in-app/by SMS/by phone, send and handle Interactive Cards, and listen for card button callbacks (card.action.trigger). Use when users need to send messages, view or search chat history, download chat files, view group members, search groups, create group or topic chats, manage marker data, manage Feed pins (add/remove/search pinned conversations), manage tag data, or handle card callbacks.