hermes-self-evaluation

Audits Hermes session history, skills, and costs to generate evidence-backed optimization reports.

115|9|Updated Aug 5, 2026
One-click install
npx skills add https://github.com/AtlasOmnia/donna-starter --skill hermes-self-evaluation-atlasomnia
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hermes-self-evaluation
Source: https://github.com/AtlasOmnia/donna-starter/tree/main/skills/hermes/hermes-self-evaluation
Command: npx skills add https://github.com/AtlasOmnia/donna-starter --skill hermes-self-evaluation-atlasomnia

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Hermes deployments accumulate session data, skills, cron jobs, and costs over time, but there is no built-in way to systematically audit that history and turn it into concrete optimization recommendations. This Skill gathers live evidence from the session database and skill library, then produces either a direct review or a structured analyst prompt for an external model. ## Core Features & Use Cases - Session store analysis: Queries ~/.hermes/state.db for usage statistics by source, model, cost, and recurring task patterns. - Runaway session diagnostics: Diagnoses a specific session that hit tool-call guardrails, ignored stop instructions, or replayed stale tool calls after compaction. - Analyst prompt generation: Composes a self-contained, structured prompt that an external model can use to audit the deployment, saved to a known file location. - Evidence-first validation: Separates observed symptoms from confirmed root causes and verifies that proposed configuration changes actually exist before recommending them. - Use Case: After noticing rising token costs, ask for a system audit; the Skill aggregates session statistics, maps the skill library, and writes a prioritized findings report with evidence and expected impact. ## Quick Start Ask the assistant to audit your Hermes setup by analyzing session history, skill usage, and token costs, then produce a prioritized list of optimization recommendations.

Frequently Asked Questions about hermes-self-evaluation

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

FAQPage Schema
How do I audit my Hermes Agent session history and costs?

Query the sessions table in ~/.hermes/state.db to aggregate usage by source, model, and estimated cost. The Skill provides starter SQL for session counts, token totals, longest sessions, and repeated task titles, then compiles results into a structured report.

How do I diagnose a Hermes session that ran too long or ignored stop instructions?

Collect the session metadata, role counts, tool-call patterns, and log markers like max_iterations_reached or context compaction events. Repeated exact tool-call IDs are a strong signal of stale replay after restore, which is distinct from ordinary high tool volume.

Can I have another AI model evaluate my Hermes setup?

Yes. The Skill composes a self-contained analyst prompt with data locations, usage statistics, skill library structure, and analysis dimensions, saved to a file you can feed to any external model. Match prompt length to the target model's context window.

Does the Hermes audit modify my configuration or session data?

No. Self-checks are strictly read-only: they inspect schemas, databases, logs, and configuration but never restart services, prune sessions, consolidate memory, or change settings. Recommendations are surfaced with evidence for manual review.

Why might cost data be missing for some Hermes sessions?

The estimated_cost_usd column is only populated when the billing provider was reachable during the session. Local-model sessions often show $0.00, so missing cost values should be reported as a caveat rather than proof the usage was free.