Hermes Desktop, with oh-my-hermes.
Pick a workflow; Hermes clarifies before it builds.
|
Hermes CLI, with oh-my-hermes.
The same workflows, in your terminal.
|
Hermes messenger app, with oh-my-hermes.
Ask in a thread; the run reports back there.
|
omh setup, one command.
Installs the workflows and connects them to Hermes.
|
# oh-my-hermes
English |
한국어 |
日本語 |
中文
Install once. Keep Hermes. Add a stronger operating layer.
Planning, research, creation, coding handoffs, operations, and project memory with explicit evidence boundaries.
oh-my-hermes (OMH) turns a normal request in
Hermes Agent into
a clear capability, a useful next step, and an honest statement of what has
or has not happened. It strengthens the Hermes workflow you already use
instead of replacing Hermes or hiding a coding executor behind it.
OMH is the operating layer above individual Hermes-native skills: it frames
the problem, selects the workflow and evidence gates, and uses native skills
as capabilities within that governed path rather than as competing top-level
owners.
[Website](https://rlaope.github.io/oh-my-hermes/) ·
[Documentation](docs/README.md) ·
[Installation](docs/INSTALLATION.md) ·
[Capabilities](docs/CAPABILITIES.md) ·
[Capability Impact](docs/CAPABILITY_IMPACT.md) ·
[Agent Install](INSTALL_FOR_AGENTS.md) ·
[GitHub Pages site](site/index.html)
> [!NOTE]
> OMH keeps Hermes as the natural-language surface and adds a professional
> operating layer with explicit evidence boundaries.
>
>
> 
>
>
>
> 
>
> [!TIP]
> Be with us!
>
>
>
>  |
> Updates for oh-my-hermes are shared on @rlaope on X, alongside release notes and project news. |
>
>
>  |
> Follow @rlaope on GitHub for more projects, releases, and ongoing work. |
>
>
>  |
> Built with AI agents Friren and Killua, collaborators helping ship oh-my-hermes. |
>
>
>  |
> Thank you to Nous Research for creating Hermes Agent. |
>
>
>
>
> 
>
## Quick Start
**Install the local command and managed skills:**
```sh
curl -fsSL https://raw.githubusercontent.com/rlaope/oh-my-hermes/main/install.sh | sh
omh setup
```
**Hermes skill tap path:**
```sh
hermes skills tap add rlaope/oh-my-hermes
hermes skills install rlaope/oh-my-hermes/skills/omh-routing --yes
```
**or ask Your AI Agent:**
```text
Hey Agent, Install this >> https://github.com/rlaope/oh-my-hermes <<
```
**Update and health check:**
```sh
omh update
omh doctor
```
Maintenance paths such as reconciling a `--full` install back to core live in
[Installation](docs/INSTALLATION.md#reconciling-an-existing-full-install-back-to-core).
## What OMH Adds
### Mixture of Models
OMH packages **103 installable workflow skills** behind six human-readable
capability families. The family is the front door; exact skill names remain
available when a wrapper or operator needs precise control.
The full generated catalog, triggers, harnesses, and evidence rules live in
[Workflow Reference](docs/WORKFLOWS.md).
**Highlights**
| Capability | Try it with | What it does |
| --- | --- | --- |
| 🧭 **Clarify and plan** | `ulw-interview` · `ulw-plan` · `omh-decide` | Turns an ambiguous request into explicit goals, constraints, tradeoffs, acceptance criteria, and a plan that can be handed off. |
| ⚡ **Build with leverage** | `ulw-work` · `ulw-goal` · `ulw-team` · `ulw-loop` | Scales from fast parallel work to durable multi-step execution while keeping ownership, checkpoints, and verification visible. |
| 🔬 **Research and learn** | `ulw-research` · `omh-best-practice-research` · `omh-research-brief` | Finds and synthesizes source-backed evidence with freshness, source-quality, and unresolved-uncertainty boundaries. |
| 🛠️ **Code and ship safely** | `ulw-process` · `omh-code-review` · `ulw-qa` | Prepares executor-neutral coding work, then makes review, QA, CI, and merge claims depend on observed evidence. |
| 🎨 **Create polished deliverables** | `omh-design-quality-gate` · `omh-materials-package` · `omh-deliverable-package` · `omh-image-cards` | Shapes websites, visuals, reports, decks, documents, PDFs, posters, and packages around content, taste, accessibility, and render-quality gates. |
| 🧠 **Remember and operate** | `omh-memory-new` · `omh-memory-sync` · `omh-ops-observability-card` · `omh-doctor` | Keeps project memory review-first, surfaces operational readiness, and gives the next repair action without inventing provider or system state. |
| 🔌 **Connect without hiding boundaries** | `omh-toolbelt-readiness` · `omh-external-connector-readiness` · `omh-agent-board` | Checks whether a needed tool, connector, or agent surface is really available before work depends on it, and keeps host load, tool use, and external-provider access separately observable. |
## Built For Real Work
> **OMH (Oh-My-Hermes)** — Anyone can use hermes-agent professionally.
> The powerful intelligence harness for your AI Agent.
**🧭 A stronger router, not a command dump.** English, Korean, Japanese,
Chinese, Spanish, French, German, and Hindi operator requests can be
classified locally without a translation API. OMH returns the recommended
family, skill, owner, next action, and what is still not evidence.
**🤝 Better coding handoffs.** OMH can include repository constraints, accepted
scope, worktree and session-isolation guidance, locally available skills,
acceptance criteria, review expectations, and verification gates. Codex, Claude
Code, Hermes, and generic executors remain explicit owners rather than hidden
defaults.
**🎨 Quality-aware creation.** Frontend, accessibility, image, report, slide,
document, spreadsheet, PDF, poster, and shareable-package requests are routed
through specialized production and QA guidance. A prepared brief is never
presented as a generated or visually verified artifact.
**🔍 Evidence before claims.** OMH separates prepared intent, observed runtime
events, and verified results. A handoff can be ready without claiming that an
executor ran, a review passed, CI succeeded, a deployment completed, or a PR
was merged.
**🧠 Review-first project memory.** OMH keeps project-memory candidates separate
from approved records and recalls only reviewed, prepared context into future
handoffs. It does not pretend to read or mutate opaque Hermes memory.
**💬 Project-aware clarification, without automatic routing.** In
natural-language Hermes chat, reviewed terminology from the current repository
can improve one ambiguous wrapper question. OMH derives the current project
internally; users do not provide a domain scope, and the context is not
persisted. The clarification does not change the selected route or mean that
planning, execution, review, CI, or merge work happened.
**🔌 Provider-neutral operations.** Metric, wiki, browser, image, video, and
connector systems sit behind explicit external-provider contracts. OMH can
validate and analyze supplied data without pretending that a provider was
connected or called.
**🏛️ Hermes-native, executor-neutral architecture.** Hermes remains the chat,
clarification, planning, research, and status surface. The selected executor
owns implementation, while OMH supplies the local contracts, routing, memory,
quality gates, and evidence boundaries around that work.
**🧱 Local-first control plane.** Core OMH routing, catalogs, manifests, and
claim rules are deterministic local surfaces. External calls and provider
access stay explicit integrations rather than hidden behavior inside the core.
## Evidence Before Claims
OMH separates useful preparation from observed results:
| State | Meaning |
| --- | --- |
| Prepared | A route, plan, prompt, artifact contract, or handoff is ready. |
| Observed | A wrapper or runtime recorded that an action or result occurred. |
| Verified | A matching test, review, served-surface check, or other required gate passed. |
`prepared_not_observed` is not execution, provider access, artifact generation,
review, CI, deployment, merge readiness, or a merge. Capability impact is
reported across separate dimensions rather than collapsed into one marketing
score. See [Capability Impact](docs/CAPABILITY_IMPACT.md).
## Documentation
- [Documentation map](docs/README.md)
- [Installation and updates](docs/INSTALLATION.md)
- [Product direction and boundaries](docs/DIRECTION.md)
- [Architecture](docs/ARCHITECTURE.md)
- [Capability manifests](docs/CAPABILITIES.md)
- [Workflow reference](docs/WORKFLOWS.md)
- [Roles](docs/ROLES.md)
- [Application cases](docs/APPLICATION_CASES.md)
- [Release and development](docs/RELEASE.md)
## Development
For a source checkout:
```sh
PYTHONPATH=tests uv run python -m unittest discover -s tests -v
uv run python -m compileall -q src tests
uv run python -m omh.cli docs workflows --check
git diff --check
```
OMH is developed in the open as part of
[Team Art & Engineering](https://rlaope.github.io/artengine-lab/). Follow
[@rlaope](https://github.com/rlaope) for project updates.