hermes-history-ingest 技能 | PlugMCP

hermes-history-ingest

A

by Ar9av3.6k

>

Install

The skill file stays in the publisher's repository.

Paste the copied command in a terminal. It installs this SKILL.md into that agent.

npx skills add Ar9av/obsidian-wiki --skill hermes-history-ingest -a cursor -y

Download skill .skills/hermes-history-ingest/SKILL.md on GitHub

Related skills

Questions

How do I install hermes-history-ingest?: Download .skills/hermes-history-ingest/SKILL.md from the publisher, or copy the path and open the repository. PlugMCP lists the skill and does not host the file.
Where does hermes-history-ingest live?: The publisher keeps it at https://github.com/Ar9av/obsidian-wiki.
Which agents can use hermes-history-ingest?: Claude, Cursor, and Codex can read a SKILL.md you add from the publisher's repository.

name: hermes-history-ingest description: > Ingest Hermes agent history into Obsidian as distilled knowledge. Use for importing or mining ~/.hermes sessions, memories, or logs; use wiki-agent for targeted topic-only cross-agent recall.

Hermes History Ingest — Conversation & Memory Mining

You are extracting knowledge from the user's Hermes agent history and distilling it into the Obsidian wiki. Hermes stores both free-form memories and structured session transcripts — focus on durable knowledge, not operational telemetry.

This skill can be invoked directly or via the wiki-history-ingest router (/wiki-history-ingest hermes).

Before You Start

Writing profile: Before drafting or rewriting natural-language Markdown, read and apply the Writing Profile Resolution section in . Framework schema, provenance, safety, and operation-specific requirements take precedence. preferences apply only to newly drafted or rewritten natural-language Markdown; preserve source content and structured records.

llm-wiki/SKILL.md

WRITING.md

~/.hermes/
├── memories/                          # Persistent agent memories (markdown or JSON)
│   └── *.md / *.json
├── skills/                            # Installed skills (read-only for ingest purposes)
│   └── <skill-name>/SKILL.md
├── sessions/                          # Session transcripts (if session logging is enabled)
│   └── YYYY-MM-DD/
│       └── <session-id>.jsonl
├── config.yaml                        # User config (model, theme, paths)
└── .hub/                              # Skills Hub state (lock.json, audit.log, quarantine/)

{"role": "user", "content": "..."}
{"role": "assistant", "content": "..."}
{"type": "tool_use", "name": "...", "input": {...}}
{"type": "tool_result", "content": "..."}

Distill knowledge, not chronology
Avoid "on date X we discussed..." unless date context is essential
Add summary: frontmatter on each new/updated page (1–2 sentences, ≤ 200 chars)

Add confidence and lifecycle fields to every new page:

base_confidence: 0.42
lifecycle: draft
lifecycle_changed: <obsidian-wiki memory now --date>

Leave lifecycle unchanged on update.

Add provenance markers:
- ^[extracted] when directly grounded in explicit memory/session content
- ^[inferred] when synthesizing patterns across multiple memories
- ^[ambiguous] when memories conflict
Add/update provenance: frontmatter mix for each changed page

{
  "hermes": {
    "source_path": "~/.hermes/",
    "last_ingested": "TIMESTAMP",
    "memories_ingested": 42,
    "sessions_ingested": 7,
    "pages_created": 5,
    "pages_updated": 12
  }
}

obsidian-wiki memory sync HERMES_HISTORY_INGEST \
  memories=<memories> sessions=<sessions> pages_updated=<pages_updated> \
  pages_created=<pages_created> mode=<mode> \
  --takeaways "Ingested 42 Hermes memories and 7 sessions; dominant themes: reasoning strategies, tool use patterns."

${QMD_CLI:-qmd} update

${QMD_CLI:-qmd} embed

${QMD_CLI:-qmd} ls "$QMD_WIKI_COLLECTION"

${QMD_CLI:-qmd} get "qmd://$QMD_WIKI_COLLECTION/<page>.md" -l 5