---
title: "How to Port an Existing Skill from Hermes Agent to OpenCode"
url: https://daily.dev/posts/how-to-port-an-existing-skill-from-hermes-agent-to-opencode-mqpxkiaey
source_url: https://blog.devgenius.io/how-to-port-an-existing-skill-from-hermes-agent-to-opencode-f25ac520b7e5
type: article
source: "Dev Genius"
published: 2026-08-24T09:49:52.234Z
updated: 2026-08-24T09:50:20.111Z
tags: ["ai-agents", "opencode"]
reading_time: 4
upvotes: 0
comments: 0
language: en
---

> ## Documentation Index
> Fetch the complete documentation index at: https://daily.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# How to Port an Existing Skill from Hermes Agent to OpenCode

**[Dev Genius](https://daily.dev/sources/devgenius)** · 4 min read · 0 upvotes · 0 comments

## Summary

A practical walkthrough for porting an existing agent skill from Hermes Agent to OpenCode, since both use the same SKILL.md format with frontmatter plus optional references/ and scripts/ folders. It covers copying the skill folder, rewriting frontmatter fields (name, description, license, optional metadata and compatibility), fixing hard-coded paths and dependencies (since OpenCode only loads skills from within the project worktree), and testing the ported skill by starting a new OpenCode session and checking trigger words. It also touches on licensing etiquette when republishing a ported skill to ClawHub.

## Full article

daily.dev links to this article rather than hosting it. Read it at the original source: <https://blog.devgenius.io/how-to-port-an-existing-skill-from-hermes-agent-to-opencode-f25ac520b7e5>

## Questions this post answers

### How do I port a skill from Hermes Agent to OpenCode?

Copy the skill folder into .opencode/skills/ or ~/.config/opencode/skills/, rename it to avoid confusion with the original, and keep the description and license fields. Add an optional compatibility: opencode field and a metadata block crediting the original author, then rewrite the description with trigger keywords so OpenCode's skill router picks it up, since the router matches the description text rather than the filename.

_Developers building agent skill libraries can track opencode workflow guides like this on daily.dev._

### Why does my ported OpenCode skill fail to load its referenced files?

OpenCode only loads skills from inside the project worktree, so any hard-coded paths pointing outside the repo, like a Hermes Agent skill's ~/.hermes/... references, will break after porting. Relative references such as references/layouts/bento-grid.md keep working as long as the whole folder is copied, not just the SKILL.md file, so hard-coded paths should be replaced with relative paths or environment variables.

_Anyone debugging agent skill path errors can find porting fixes like this on daily.dev._

### Why isn't my custom skill triggering in OpenCode?

The skill router matches against the text in the description frontmatter field, not the filename or folder name, so a vague description means the skill never gets picked up. Fix this by tightening the description to include the exact action verbs and keywords a user would type, in multiple languages if relevant, then start a new OpenCode session since skills load at session start and are not hot-reloaded.

_Developers tuning agent skill triggers can find troubleshooting tips like this on daily.dev._

## Similar posts on daily.dev

- [How to Build Your Own Claude Code Skill](https://daily.dev/posts/how-to-build-your-own-claude-code-skill-xk4dwhksx) · freeCodeCamp · 12 upvotes · 0 comments
- [Introducing Skills Registry](https://daily.dev/posts/introducing-skills-registry-spriko7os) · portkey · 1 upvotes · 0 comments

---

Tags: [#ai-agents](https://daily.dev/tags/ai-agents), [#opencode](https://daily.dev/tags/opencode)

[View this post on daily.dev](https://daily.dev/posts/how-to-port-an-existing-skill-from-hermes-agent-to-opencode-mqpxkiaey)