hermes-history-ingest

To ingest agent session transcripts into an Obsidian wiki, this skill mines memories and session data from ~/.hermes and routes distilled insights into wiki pages. It automatically merges new information into existing pages to build a coherent knowledge graph without duplicating data.

Converting Hermes memories into durable knowledge involves extracting session data from ~/.hermes and applying provenance tagging to fit wiki conventions. This process transforms scattered agent memories into citeable, permanent knowledge graph entries within your Obsidian vault.

Yes, you can redact sensitive information when syncing Hermes history to your wiki. The ingestion process includes built-in redaction capabilities and applies provenance markers to maintain privacy and traceability while routing memories and session transcripts into Obsidian.

The Hermes history ingest process supports both delta syncs and append/full ingest modes. This allows you to control the scope of ingestion, whether you are incrementally adding new session memories or performing a complete historical data transfer into your wiki.

You should use provenance tagging during Hermes session ingestion whenever you need to maintain strict traceability of distilled knowledge. It automatically marks the source of memories and session transcripts to ensure all insights routed into the Obsidian wiki remain auditable and citeable.

If Hermes memories are duplicating in the wiki after ingestion, you may need to utilize the merge functionality. The skill is designed to merge new insights into existing Obsidian pages to build a coherent knowledge graph without duplicating data, ensuring clean delta syncs.