Skip to content
cccskills
FreePublished on GitHub

wiki-history-ingest

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.

OriginalShow the original description

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.

Run score Not tested

See how to install

Good for

  • Requesting a history import without knowing the specialist skill name
  • Selecting a history importer by agent name
  • Identifying the importer from a history folder or file
  • Clarifying which agent's history to import

Files included (1)

  • SKILL.md2.3 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

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:

SubcommandRoute To
claudeclaude-history-ingest
copilotcopilot-history-ingest
codexcodex-history-ingest
hermeshermes-history-ingest
openclawopenclaw-history-ingest
pipi-history-ingest
autoinfer from context using rules below

Routing Rules

  1. If the user explicitly says claude, copilot, codex, hermes, openclaw, or pi, route directly.
  2. 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
  3. 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

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

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.

  • Preserve project decisions from past Claude sessions
  • Turn debugging conversations into reusable notes
  • Document workflows found in desktop audit logs
Ar9av/obsidian-wiki3.6KUpdated Oct 21, 2026

code-understand

FreeSummary

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.

  • Understanding an unfamiliar module before editing
  • Finding callers of a function
  • Assessing the impact of changed files
Ar9av/obsidian-wiki3.6KUpdated Oct 21, 2026

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.

  • Turning Codex conversations into reusable wiki knowledge
  • Adding only new or changed session history
  • Consolidating recurring debugging techniques across sessions
Ar9av/obsidian-wiki3.6KUpdated Oct 21, 2026

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.

  • Preserve design decisions from past Copilot conversations
  • Combine debugging knowledge across multiple sessions
  • Add knowledge from new or updated sessions
Ar9av/obsidian-wiki3.6KUpdated Oct 21, 2026

cross-linker

FreeSummary

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.

  • Connect newly imported pages to existing wiki content
  • Turn unlinked mentions of page names into references
  • Find disconnected pages and project filing candidates
Ar9av/obsidian-wiki3.6KUpdated Oct 21, 2026

daily-update

FreeSummary

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.

  • Refresh a wiki each morning
  • Check for changed or missing source files
  • Set up daily maintenance and terminal reminders
Ar9av/obsidian-wiki3.6KUpdated Oct 21, 2026

See all skills by Ar9av

Report a problem with this skill