hermes - 💡(How to fix) Fix Hermes in saving narratives of routine one-off actions and queries and saving them as skills.md. These should not be saved as skills [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
NousResearch/hermes-agent#12812Fetched 2026-04-20 12:16:51
View on GitHub
Comments
0
Participants
1
Timeline
1
Reactions
0
Author
Participants
Timeline (top)
renamed ×1

Code Example

---
    name: openrouter-billing-investigate
    description: Investigate unexpected OpenRouter charges by analyzing gateway logs for fallback patterns...
    ---
    
    # OpenRouter Billing Investigate
    
    ## Context
    We looked at ~/Logs/gateway.log to find fallback usage on April 18.
    The agent ran terminal commands to grep for "openrouter" and "billing".
    
    ## What we found
    - There were 86 calls to Gemini-Flash for auxiliary tasks.
    - There were 10 fallback calls to MiniMax.
    - Total estimated cost was 5 cents.
RAW_BUFFERClick to expand / collapse

❯ i wanted to REPORT AN ISSUE I am encoutering that I am not sure others have seen.. Agent skill creation seems to lack a quality filter. It has been saving narrative summaries of one-time troubleshooting as reusable skills. For example, I was setting up the NousRouter which was a one time setup that had a small hiccup I was discussing wiith the agent. Two days later when my Danual (it's a dynamic manual I made to track changes and updates to skills and commands etc) was reviewing updates I see that it was created as a new skill in skill.md . I have many examples of this...................................Here is an example of what is occurring.

This skill called "openrouter-billing-investigate" was created after we simply looked at your logs one time to answer the question: "Why did I get a weird bill?"

**The SKILL.md file contains:**

```yaml
---
name: openrouter-billing-investigate
description: Investigate unexpected OpenRouter charges by analyzing gateway logs for fallback patterns...
---

# OpenRouter Billing Investigate

## Context
We looked at ~/Logs/gateway.log to find fallback usage on April 18.
The agent ran terminal commands to grep for "openrouter" and "billing".

## What we found
- There were 86 calls to Gemini-Flash for auxiliary tasks.
- There were 10 fallback calls to MiniMax.
- Total estimated cost was 5 cents.
```

**Why this is broken:**
1.  **It's a diary entry, not a tool.** It records *what we found today*, not *how to investigate billing generally*.
2.  **It will mislead the agent later.** If you ask in 6 months, "How do I check my billing?", the agent might load this file, see "86 calls to Gemini," and think that is a *hard-coded fact* about your system, rather than a one-time observation.
3.  **It is static.** Real logic belongs in a script (like the `danual` scanner), not in a skill that just says "we looked at logs."

Another example is **`browser-engine-selection`**, which is just a text summary of a conversation we had about whether "cloud" or "local" browsers are better. It contains no instructions, just an opinionated summary of that specific chat.

extent analysis

TL;DR

Implement a quality filter for agent skill creation to prevent saving one-time troubleshooting narratives as reusable skills.

Guidance

  • Review the agent skill creation process to identify why narrative summaries of one-time troubleshooting are being saved as reusable skills.
  • Consider adding a validation step to ensure that skills contain actionable instructions or reusable logic, rather than just descriptive text.
  • Evaluate the use of templates or guidelines for creating skills to help agents distinguish between one-time troubleshooting and reusable skills.
  • Assess the potential for automating the review and filtering of skills to prevent incorrect or misleading information from being saved.

Example

No code snippet is provided as the issue is more related to process and content creation rather than code.

Notes

The issue highlights the importance of having a clear distinction between one-time troubleshooting and reusable skills, and the need for a quality filter to prevent incorrect or misleading information from being saved.

Recommendation

Apply a workaround by implementing a manual review process for agent-created skills to ensure they meet the criteria for reusable skills, until a more automated quality filter can be developed.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING