hermes-diagnostic-review

Review Hermes session history read-only to detect recurring mistakes and propose improvements.

58|6|Updated Jul 19, 2026
One-click install
npx skills add https://github.com/AtlasOmnia/hermes-custom-pack --skill hermes-diagnostic-review-atlasomnia
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: hermes-diagnostic-review
Source: https://github.com/AtlasOmnia/hermes-custom-pack/tree/main/skills/hermes-diagnostic-review
Command: npx skills add https://github.com/AtlasOmnia/hermes-custom-pack --skill hermes-diagnostic-review-atlasomnia

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Recurring mistakes, failed tool calls, and re-fixed work hide inside long Hermes session histories, and manually auditing them is slow and error-prone. This Skill performs a structured, read-only diagnostic review of recent sessions and turns the findings into a suggestion-only report with proposed reusable skills. ## Core Features & Use Cases - Read-only session mining: Uses session_search exclusively to browse, filter, and expand sessions without touching raw transcript files or databases. - Signal classification rubric: Classifies findings as Critical or Watch using fingerprints and a promotion rule (confirmed Critical, or 3+ distinct sessions within a 7-day window). - Human-gated output: Produces a compact report with redacted evidence, coverage limits, and proposed skills; nothing is ever applied automatically. - Use Case: Ask for a review of the last 7 days of sessions to find which tool calls keep failing, then receive a report of recurring failure fingerprints plus suggested new skills to prevent them. ## Quick Start Review my recent Hermes sessions from the last 7 days for recurring mistakes and failed tool calls, and suggest improvements.

Frequently Asked Questions about hermes-diagnostic-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review my Hermes session history for recurring mistakes?▼

Ask for a diagnostic review of a time window such as the last 7 days. The review uses session_search to browse and filter sessions, records failure signals per session, and emits a report classifying each finding as Critical or Watch.

How do I find failed tool calls in past Hermes sessions?▼

Run session_search with a query and set role_filter to include tool output, which surfaces errored or timed-out tool calls. Expand matches with session_id and around_message_id to read the surrounding context.

Does the diagnostic review change my skills or config automatically?▼

No. The review is strictly read-only and suggestion-only; it never edits skills, memory, config, cron jobs, or repositories. Every proposal requires explicit user approval before any change is made.

When does a repeated mistake become a proposed improvement?▼

A signal is promoted only if it is a confirmed Critical incident or the same fingerprint appears in at least three distinct sessions within an inclusive seven-day window. Everything else stays on the Watch list.

Is reviewing session history private if my data is local?▼

Not necessarily. Recalled session content enters the active model context and may be sent to a remote provider, so the review discloses this and asks for consent before inspecting sensitive history, or you can use a local model.

When should I not use the diagnostic review skill?▼

Do not use it for pruning, exporting, or backing up session history, which belongs to hermes-session-maintenance, or for evaluating Hermes's own costs and architecture, which belongs to hermes-self-evaluation.