wiki-history-ingest

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.

3,177
installs: 0 up / 0 down, score 0.00
votes: 3,606
repo stars
Updated: 1 month ago
In the catalog since: 1 Oct 2026
From: ar9av/obsidian-wiki

Get it through your agent npx skills add ar9av/obsidian-wiki@wiki-history-ingest

Skill instructions

Rendered from the published SKILL.md, 53 lines.

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

Get it through your agent

Call the Graph-of-Skills MCP server's retrieve_skill_bundle tool and it returns this skill's text inside your budget.

{
  "tool": "retrieve_skill_bundle",
  "arguments": {
    "query": "wiki-history-ingest"
  }
}

New to this? Set up Graph-of-Skills or get a free key. The text on this page comes from its authors: how skills are sourced and what we check. If none fits your task, your agent can write a skill for your own library. To keep a skill from your own library on a machine, see how to install one of your skills.

Share on X Share on LinkedIn Share on Bluesky Share on Hacker News

Share on Reddit

Source

Source repository ar9av/obsidian-wiki
Listing on skills.sh

From ar9av/obsidian-wiki via skills.sh

Related skills

wiki-ingest
Ingest new documents, raw text, folders, or URLs into the Obsidian wiki as distilled, linked knowledge. Use for general wiki ingestion when no more specific ingest skill applies, including processing _raw/ staged content.
3,631 installs
cross-linker
Find and add missing cross-references between wiki pages. Use when pages are disconnected or after large ingestion. This modifies pages to add links; use wiki-lint for report-oriented structural auditing.
3,282 installs
karpathy-llm-wiki
Use when building or maintaining a personal LLM-powered knowledge base. Triggers: ingesting sources into a wiki, querying wiki knowledge, linting wiki quality, 'add to wiki', 'what do I know about', or any mention of 'LLM wiki' or 'Karpathy wiki'.
8,146 installs
firecrawl-knowledge-ingest
Export documentation portals, help centers and API reference sites into local markdown or JSON with Firecrawl browser, including pages that render with JavaScript, hide content behind collapsible navigation or paginate. Use when the user wants a docs site, help center or support knowledge base saved as files, even without an explicit request to scrape.
31,332 installs
ljg-travel
Deep travel research workflow for museums and ancient architecture. Input a city name, auto-generates structured knowledge document (org-mode) + portable reference cards (PNG). Covers historical background, museum highlights, archaeological significance, and architectural heritage. Use when user says '旅行研究', '博物馆功课', '古建功课', 'travel research', '出发前功课', or provides a city name with intent to do deep cultural travel preparation.
5,979 installs

More from ar9av/obsidian-wiki

llm-wiki
Explain and apply the foundational LLM Wiki architecture and knowledge-management strategy. Use for setup, architecture, schema, or organization decisions; operational ingest/query/lint work uses dedicated skills.
4,092 installs
wiki-ingest
Ingest new documents, raw text, folders, or URLs into the Obsidian wiki as distilled, linked knowledge. Use for general wiki ingestion when no more specific ingest skill applies, including processing _raw/ staged content.
3,631 installs
wiki-setup
Initialize or repair an Obsidian wiki vault's required structure and configuration. Use for new-vault setup, .env/config creation, reconfiguration, or broken setup recovery.
3,582 installs
wiki-query
Search and synthesize answers from the compiled Obsidian wiki, including cited and multi-hop answers. Use for questions about existing wiki knowledge or fast index-only lookups, and for challenge requests ("challenge this", "argue against X", "poke holes in my plan") that look for the vault's own evidence against a plan. Supports named-vault routing such as wiki-query @work; not for ingesting new sources.
3,550 installs
wiki-lint
Audit wiki health: broken links, orphans, contradictions, stale content, lifecycle and tag issues. Use for maintenance or health checks. Default is report-only; use wiki-dedup for page-identity merges.
3,509 installs

Content is provided as published by its creators; you are responsible for how you use it.

To request removal, use the contact form.