Topic · Updated June 19, 2026
Hermes Skill Workflows
Short answer
Hermes Skill Workflows is a focused Workflow Trust topic for developers packaging repeated agent tasks. Start by inspecting source-visible repositories, reviewed workflow files, compatible agents, license signals, and maintenance evidence before running anything locally. The practical goal is not to certify a repository as safe, but to help readers decide whether it belongs in a reviewed workflow, pending review candidate, or hidden low-confidence bucket. For this topic, the main review concern is that skill bundles can hide broad tool assumptions.
Hermes skill workflows are useful when a repeated task can become a narrow, reviewable skill. The page should clarify inputs, tools, outputs, and whether the skill can write externally.
Who this topic helps
- Developers packaging repeated agent tasks.
- Teams comparing skills, hooks, and AGENTS.md files.
- Reviewers checking MCP and tool allowlists.
Start here
Use this page as a focused path into Workflow Trust. It groups source-visible workflow reviews, practical guides, and risk notes around one search intent instead of forcing readers through the full catalog first.
Related workflow reviews
Related guides
Risk notes
- Skill bundles can hide broad tool assumptions.
- Cron or scheduled tasks can repeat bad actions.
- Tool allowlists should be documented before installation.
Related questions
- What are hermes skill workflows?
- Which GitHub repositories are useful for hermes skill workflows?
- What risks should be checked before using hermes skill workflows?
Common search phrases
hermes skill workflows, hermes skill workflows GitHub source, hermes skill workflows risk review, hermes skill workflows compatible agents
FAQ
What should a Hermes skill workflow include?
A narrow task, required tools, permission notes, expected output, and a way to inspect or disable the workflow.
Can skills be sold as workflow apps?
Only when they are runnable, documented, tested, and clear about local keys and permissions.