hermes - 💡(How to fix) Fix [Bug]: Can't invoke my peronal skills anymore [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#19040Fetched 2026-05-03 04:52:45
View on GitHub
Comments
0
Participants
1
Timeline
4
Reactions
0
Author
Participants
Timeline (top)
labeled ×4

Error Message

Additional Logs / Traceback (optional)

Root Cause

Root Cause Analysis (optional)

Code Example

n/a

---
RAW_BUFFERClick to expand / collapse

Bug Description

Hermes seems to have faultily moved my skills

previously: ~/.hermes/skils/me/<skill-name>/SKILL.md

now: ~/.hermes/skills/me/me-personal-workflows/references/<skill-name>.md

I can't invoke them via /command anymore

Are there any instructions on how to undo this?

Steps to Reproduce

Update hermes

Expected Behavior

Don't touch my skills

Actual Behavior

Moved my skills, can't invoke my own skills anymore

Affected Component

CLI (interactive chat)

Messaging Platform (if gateway-related)

No response

Debug Report

n/a

Operating System

Debian 13

Python Version

Python 3.13.5

Hermes Version

Hermes Agent v0.12.0 (2026.4.30)

Additional Logs / Traceback (optional)

Root Cause Analysis (optional)

No response

Proposed Fix (optional)

No response

Are you willing to submit a PR for this?

  • I'd like to fix this myself and submit a PR

extent analysis

TL;DR

Manually moving the skills back to their original location or updating the invocation path may resolve the issue with invoking skills via /command.

Guidance

  • Verify the new location of the skills files (~/.hermes/skills/me/me-personal-workflows/references/<skill-name>.md) and check if the file contents are intact.
  • Try moving the skills files back to their original location (~/.hermes/skils/me/<skill-name>/SKILL.md) to see if it resolves the invocation issue.
  • If moving the files is not feasible, investigate updating the invocation path in the Hermes configuration to point to the new location.
  • Check the Hermes documentation for any configuration options or environment variables that may control the skills directory or invocation path.

Example

No code snippet is provided as the issue does not imply a specific code change.

Notes

The solution may depend on the internal workings of Hermes and its configuration options, which are not fully described in the issue. Additionally, the issue may be related to a version-specific change in Hermes.

Recommendation

Apply workaround: Manually moving the skills files or updating the invocation path may be the most straightforward solution until an official fix or documentation update is available.

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

hermes - 💡(How to fix) Fix [Bug]: Can't invoke my peronal skills anymore [1 participants]