CtrlK
BlogDocsLog inGet started
Tessl Logo

hermes-history-ingest

Ingest Hermes agent history into the Obsidian wiki. Use this skill when the user wants to mine their past Hermes sessions for knowledge, import their ~/.hermes folder, extract insights from previous Hermes conversations, or says things like "process my Hermes history", "add my Hermes memories to the wiki", "ingest ~/.hermes", or "what have I worked on in Hermes". Also triggers when the user mentions Hermes memories, Hermes sessions, ~/.hermes/memories, or Hermes skill logs.

70

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

75%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-organized, actionable ingest workflow with a clear step sequence and a properly used reference file. It scores solidly across dimensions but loses the top mark to duplicated privacy guidance and a missing explicit post-write verification step.

Suggestions

Consolidate the privacy guidance — it appears both as Step 3's 'Critical privacy filter' and as the trailing 'Privacy and Compliance' section — into one location to trim tokens.

Add an explicit post-write verification step (e.g., re-read one sampled new/updated page to confirm summary/frontmatter/provenance rendered correctly) to close the batch-write validation gap.

Move the inlined JSONL envelope shapes and manifest JSON block into references/hermes-data-format.md, leaving the body as a tighter overview that points to the reference.

DimensionReasoningScore

Conciseness

Mostly lean and assumes Claude's competence (no explaining what Obsidian/JSONL is), with concrete steps and code; held back from 5 by duplicated privacy guidance (Step 3 'Critical privacy filter' and the trailing 'Privacy and Compliance' section).

4 / 5

Actionability

Provides copy-paste-ready bash (QMD refresh), concrete manifest/log JSON, file paths, and routing rules; minor gaps remain where config resolution is deferred to another skill and memory parsing is inherently instructional.

4 / 5

Workflow Clarity

Clear sequenced workflow (Before You Start → Steps 1–6) with checkpoints (delta summary, manifest dedup, privacy filter, manifest/log recording, QMD verify); the batch-write path lacks an explicit post-write verification of vault content, so it does not reach 5.

4 / 5

Progressive Disclosure

Good structure with a well-signaled one-level-deep reference ('See references/hermes-data-format.md for field-level notes and extraction guidance') that genuinely holds the deferred detail; the body still inlines a fair amount of schema/manifest detail that keeps it just short of the clean overview anchor.

4 / 5

Total

16

/

20

Passed

Description

95%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, well-targeted description that clearly states what the skill does and gives rich, natural trigger phrases. The only minor weakness is that the action verbs are slightly abstract and overlapping rather than granularly distinct.

DimensionReasoningScore

Specificity

Names the domain and several concrete actions ('Ingest Hermes agent history', 'mine their past Hermes sessions for knowledge', 'import their ~/.hermes folder', 'extract insights'), but the verbs overlap and are less granular than the comprehensive 5-anchor.

4 / 5

Completeness

Explicitly answers both 'what' ('Ingest Hermes agent history into the Obsidian wiki') and 'when' ('Use this skill when...') with concrete trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

Comprehensive natural trigger phrases a user would actually say — 'process my Hermes history', 'add my Hermes memories to the wiki', 'ingest ~/.hermes', 'what have I worked on in Hermes' — plus path/synonym variants like '~/.hermes/memories' and 'Hermes skill logs'.

5 / 5

Distinctiveness Conflict Risk

Occupies a clear Hermes-specific niche with distinct triggers tied to '~/.hermes' and 'Hermes sessions/memories', making conflict with other skills minimal.

5 / 5

Total

19

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
Ar9av/obsidian-wiki
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.