wiki-history-ingest
Skill3 starsChanged 13 days agoMITView on GitHub
Unified wiki-history-ingest entrypoint for conversation/session sources. Use this when the user says "/wiki-history-ingest claude", "/wiki-history-ingest hermes", or asks to ingest agent history without naming the underlying skill. This router dispatches to the specialized history skill.
1 other project uses a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- Ar9av/obsidian-wikiedited, first seen Nov 8, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 1
- Ar9av/obsidian-wiki★ 3.7k50% same
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository30 other files it gives its agents.
- claude-history-ingestSkill
- cross-linkerSkill
- daily-updateSkill
- graph-colorizeSkill
- hermes-history-ingestSkill
- impl-validatorSkill
- llm-wikiSkill
- memory-bridgeSkill
- skill-creatorSkill
- tag-taxonomySkill
- vault-skill-factorySkill
- wiki-agentSkill
- wiki-captureSkill
- wiki-context-packSkill
- wiki-dashboardSkill
- wiki-dedupSkill
- wiki-digestSkill
- wiki-exportSkill
- wiki-importSkill
- wiki-ingestSkill
- wiki-lintSkill
- wiki-querySkill
- wiki-rebuildSkill
- wiki-researchSkill
- wiki-setupSkill
- wiki-stage-commitSkill
- wiki-statusSkill
- wiki-switchSkill
- wiki-synthesizeSkill
- wiki-updateSkill
The file
We split this skill into the rules it gives an agent
10 rules. About 0 are common, 4 are distinctive, and 6 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.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 15
If the user invokes /wiki-history-ingest <target> (or equivalent text command), dispatch directly:
- Very specific: line 25
If the user explicitly says claude or hermes, route directly.
- Distinctive: line 26
If the user provides a path/source:
- Distinctive: line 29
If ambiguous, ask one short clarification:
- Very specific: line 31
If the user names an agent with no matching skill installed (e.g.
- Distinctive: line 37
After routing, execute the destination skill's workflow exactly.
- Distinctive: line 38
Do not duplicate destination logic in this file.
- Very specific: line 39
Leave manifest/index/log update semantics to the destination skill.
- Very specific: line 43
Use wiki-ingest for documents/content sources
- Very specific: line 44
Use wiki-history-ingest for agent history sources
≈ “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.
Files
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 |
hermes | hermes-history-ingest |
auto | infer from context using rules below |
Routing Rules
- If the user explicitly says
claudeorhermes, route directly. - If the user provides a path/source:
~/.claudeor Claude memory/session JSONL artifacts ->claude-history-ingest~/.hermes,HERMES_HOME, or Hermes memories/session artifacts ->hermes-history-ingest
- If ambiguous, ask one short clarification:
- "Should I ingest
claudeorhermeshistory?"
- "Should I ingest
- If the user names an agent with no matching skill installed (e.g.
copilot,codex,openclaw,pi), say the corresponding history-ingest skill is not installed and fall back towiki-ingeston the raw export files instead.
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-ingestfor documents/content sources - Use
wiki-history-ingestfor agent history sources
Examples:
/wiki-history-ingest claude/wiki-history-ingest hermes$wiki-history-ingest claude(agents that use$skillinvocation)
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
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.