agentleFS
Sign inStart free
Ar9avAr9av/obsidian-wiki/skills/wiki-history-ingest/SKILL.md

wiki-history-ingest

Skill3.7k starsChanged 10 days agoMITView on GitHub

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.

1 other project uses a version of this, 1 of them edited.

Adopted by

Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data

Week of Sep 13: 0 new projectsWeek of Sep 20: 0 new projectsWeek of Sep 27: 0 new projectsWeek of Oct 4: 0 new projectsWeek of Oct 11: 0 new projectsWeek of Oct 18: 0 new projectsWeek of Oct 25: 0 new projectsWeek of Nov 1: 0 new projects
Sep 2026Oct 2026Nov 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read: only 0 in all, so this is a hint, not a trend.

Most recently taken up by

Who's talking about Ar9av/obsidian-wiki

The biggest 5 of 27 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 27

Talked about on GitHub and Bluesky (27 times).

On GitHub · 25

20 more on GitHub

On Bluesky · 2

The file

We split this skill into the rules it gives an agent

9 rules. About 0 are common, 4 are distinctive, and 5 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 5

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    If the user invokes /wiki-history-ingest <target> (or equivalent text command), dispatch directly:

    line 13
  2. Very specific:

    If the user explicitly says claude, copilot, codex, hermes, openclaw, or pi, route directly.

    line 27
  3. Distinctive:

    If the user provides a path/source:

    line 28
  4. Distinctive:

    If ambiguous, ask one short clarification:

    line 35
  5. Distinctive:

    After routing, execute the destination skill's workflow exactly.

    line 40
  6. Distinctive:

    Do not duplicate destination logic in this file.

    line 41
  7. Very specific:

    Leave manifest/index/log update semantics to the destination skill.

    line 42
  8. Very specific:

    Use wiki-ingest for documents/content sources

    line 46
  9. Very specific:

    Use wiki-history-ingest for agent history sources

    line 47

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free