OH-MY-HERMES

oh-my-hermes

Name: oh-my-hermes
Author: rlaope

Oh My Hermes

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 Agent poster

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 ·
Documentation ·
Installation ·
Capabilities ·
Capability Impact ·
Agent Install ·
GitHub Pages site

[!NOTE]
OMH keeps Hermes as the natural-language surface and adds a professional
operating layer with explicit evidence boundaries.

Quick Start

Install the local command and managed skills:

curl -fsSL https://raw.githubusercontent.com/rlaope/oh-my-hermes/main/install.sh | sh
omh setup

Hermes skill tap path:

hermes skills tap add rlaope/oh-my-hermes
hermes skills install rlaope/oh-my-hermes/skills/oh-my-hermes --yes

or ask Your AI Agent:

Hey Agent, Install this >> https://github.com/rlaope/oh-my-hermes <<

Update and health check:

omh update
omh doctor

Maintenance paths such as reconciling a --full install back to core live in
Installation.

What OMH Adds

OMH packages 88 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.

Capability family	What it helps Hermes do
Plan and decide	Clarify ambiguous goals, prepare reviewed plans, and run durable goal loops.
Learn and gather	Find sources, explain papers, inspect data, and prepare source-backed briefs.
Create materials and visuals	Prepare websites, visual QA, images, decks, reports, documents, and deliverable packages with format-specific quality gates.
Delegate coding and ship	Prepare scoped, skill-aware coding handoffs for Codex, Claude Code, Hermes runtime, or another selected executor.
Operate and observe	Review setup, service quality, releases, incidents, automation, tools, sessions, and workflow learning.
Retain knowledge	Build reviewed project memory and connect external knowledge systems through provider-neutral boundaries.

The full generated catalog, triggers, harnesses, and evidence rules live in
Workflow Reference.

Highlights

Capability	Try it with	What it does
🧭 Clarify and plan	`$deep-interview` · `$ralplan` · `$strategy-brief`	Turns an ambiguous request into explicit goals, constraints, tradeoffs, acceptance criteria, and a plan that can be handed off.
⚡ Build with leverage	`$ultrawork` · `$ultragoal` · `$team` · `$loop`	Scales from fast parallel work to durable multi-step execution while keeping ownership, checkpoints, and verification visible.
🔬 Research and learn	`$best-practice-research` · `$web-research` · `$research-brief`	Finds and synthesizes source-backed evidence with freshness, source-quality, and unresolved-uncertainty boundaries.
🛠️ Code and ship safely	`$request-to-handoff` · `$code-review` · `$ultraqa`	Prepares executor-neutral coding work, then makes review, QA, CI, and merge claims depend on observed evidence.
🎨 Create polished deliverables	`$design-quality-gate` · `$materials-package` · `$deliverable-package` · `$img-summary`	Shapes websites, visuals, reports, decks, documents, PDFs, posters, and packages around content, taste, accessibility, and render-quality gates.
🧠 Remember and operate	`$memory` · `$ops-observability-card` · `$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 mcp` · `omh plugin` · `$agent-board`	Exposes local metadata-only contracts for Hermes and compatible hosts while keeping host load, tool use, and external-provider access separately observable.

Built For Real Work

OMH orchestrating coding agents and creative tools

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.

🔌 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.

Documentation

Development

For a source checkout:

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. Follow
@rlaope for project updates.