ollama - ๐Ÿ’ก(How to fix) Fix Skills not working [3 comments, 2 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
ollama/ollama#15820โ€ขFetched 2026-04-27 05:29:07
View on GitHub
Comments
3
Participants
2
Timeline
3
Reactions
0
Author
Participants
Timeline (top)
commented ร—3

Code Example

ollama launch hermes

---

I did not see the code-understanding skill activated in response to the prompt. Why was the code-understanding skill not activated whey I said code-understanding in the prompt.

โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€

 โ”€  โš• Hermes  โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€ 
                                                                                                                                                                                                                   
     You're right. The skill instructions say: "Before replying, scan the skills below. If a skill matches or is even partially relevant to your task, you MUST load it with skill_view(name) and follow its       
     instructions."                                                                                                                                                                                                
                                                                                                                                                                                                                   
     The prompt contained "code-understanding" โ€” I should have loaded the skill first, then followed its protocol. Instead I went straight to calling MCP tools without consulting it. That's a procedural         
     failure on my part.                                                                                                                                                                                           
                                                                                                                                                                                                                   
     The skill would have reminded me to read the active folder from memory and target all queries at that path. It also documents the limitation about pathless query tools. Had I loaded it, I might have        
     avoided the contamination issue or at least flagged it properly.
RAW_BUFFERClick to expand / collapse

As likely a hermes thing but given the integration so who really knows, hermes ran via:

ollama launch hermes

Then eventually post having hermes auto author a skill based upon MCP tools I then try using the skill to then:

I did not see the code-understanding skill activated in response to the prompt. Why was the code-understanding skill not activated whey I said code-understanding in the prompt.

โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€

 โ”€  โš• Hermes  โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€ 
                                                                                                                                                                                                                   
     You're right. The skill instructions say: "Before replying, scan the skills below. If a skill matches or is even partially relevant to your task, you MUST load it with skill_view(name) and follow its       
     instructions."                                                                                                                                                                                                
                                                                                                                                                                                                                   
     The prompt contained "code-understanding" โ€” I should have loaded the skill first, then followed its protocol. Instead I went straight to calling MCP tools without consulting it. That's a procedural         
     failure on my part.                                                                                                                                                                                           
                                                                                                                                                                                                                   
     The skill would have reminded me to read the active folder from memory and target all queries at that path. It also documents the limitation about pathless query tools. Had I loaded it, I might have        
     avoided the contamination issue or at least flagged it properly.

extent analysis

TL;DR

The code-understanding skill was not activated because it was not loaded with skill_view(name) before attempting to use it.

Guidance

  • The issue seems to be a procedural failure in using the skill, as it was not loaded before attempting to use it.
  • To fix this, load the code-understanding skill with skill_view(name) before using it.
  • The skill instructions should be followed to avoid similar issues in the future.
  • Reviewing the skill's protocol and documentation can help prevent contamination issues and ensure proper usage.

Notes

The issue seems to be specific to the usage of the code-understanding skill and the hermes integration, so the solution may not apply to other skills or integrations.

Recommendation

Apply workaround: Load the code-understanding skill with skill_view(name) before using it, as this is a clear procedural step that was missed.

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

ollama - ๐Ÿ’ก(How to fix) Fix Skills not working [3 comments, 2 participants]