Shogun Bloom Config
yohey-w/multi-agent-shogun
Interactive wizard: guided questions with multiple-choice options about subscriptions, then outputs a ready-to-paste capabilitytiers YAML + fixed agent model assignments.
[omh] Explaining OMH itself: current-source-first documentation for OMH itself: product identity, public capability catalog, model routing, local state, and long-term memory.
Install Omh Docs
$ npx skills add rlaope/oh-my-hermes --skill omh-docs -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install rlaope/oh-my-hermes omh-docs --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/rlaope/oh-my-hermes.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/omh-docs .claude/skills/omh-docs && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "omh-docs" agent skill from https://github.com/rlaope/oh-my-hermes/tree/main/skills/omh-docs into .claude/skills/omh-docs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "omh-docs", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/rlaope/oh-my-hermes/tree/main/skills/omh-docsType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add rlaope/oh-my-hermes --skill omh-docs -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install rlaope/oh-my-hermes omh-docs --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/rlaope/oh-my-hermes.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/omh-docs .agents/skills/omh-docs && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "omh-docs" agent skill from https://github.com/rlaope/oh-my-hermes/tree/main/skills/omh-docs into .agents/skills/omh-docs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "omh-docs", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add rlaope/oh-my-hermes --skill omh-docs -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install rlaope/oh-my-hermes omh-docs --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/rlaope/oh-my-hermes.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/omh-docs .cursor/skills/omh-docs && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "omh-docs" agent skill from https://github.com/rlaope/oh-my-hermes/tree/main/skills/omh-docs into .cursor/skills/omh-docs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "omh-docs", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/rlaope/oh-my-hermes.git --path skills/omh-docs--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add rlaope/oh-my-hermes --skill omh-docs -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install rlaope/oh-my-hermes omh-docs --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/rlaope/oh-my-hermes.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/omh-docs .gemini/skills/omh-docs && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "omh-docs" agent skill from https://github.com/rlaope/oh-my-hermes/tree/main/skills/omh-docs into .gemini/skills/omh-docs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "omh-docs", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install rlaope/oh-my-hermes omh-docsInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add rlaope/oh-my-hermes --skill omh-docs -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/rlaope/oh-my-hermes.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/omh-docs .github/skills/omh-docs && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "omh-docs" agent skill from https://github.com/rlaope/oh-my-hermes/tree/main/skills/omh-docs into .github/skills/omh-docs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "omh-docs", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add rlaope/oh-my-hermes --skill omh-docs -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install rlaope/oh-my-hermes omh-docs --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/rlaope/oh-my-hermes.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/omh-docs .opencode/skills/omh-docs && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "omh-docs" agent skill from https://github.com/rlaope/oh-my-hermes/tree/main/skills/omh-docs into .opencode/skills/omh-docs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "omh-docs", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
omh-docs- GitHub stars
- 3.2k
- Token cost
- ~1.5k tokens
- SKILL.md length
- 759 words
- Files
- 5 (incl. references)
- Skills in repo
- 143
- Repo updated
- First seen
- Licence
- MIT
At a glance
[omh] Explaining OMH itself: current-source-first documentation for OMH itself: product identity, public capability catalog, model routing, local state, and long-term memory.
- Works in 4 steps: Classify the question as a… → Retrieve only the sources needed for the… → Disclose the source URL or command/path… → …
- The user says: product-docs
- SKILL.md covers Default Behavior, Source Route, Public Product vs Local Install and Safety and Mutation Boundary, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Omh Docs is an agent skill from rlaope/oh-my-hermes. [omh] Explaining OMH itself: current-source-first documentation for OMH itself: product identity, public capability catalog, model routing, local state, and long-term memory. Use when the user says: product-docs, OMH documentation, oh-my-hermes documentation, what is OMH, what is oh-my-hermes, how does OMH work, OMH capability catalog, OMH skill catalog.
Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including reference files (for example `references/capability-map.md`, `references/long-term-memory.md` and `references/model-routing-and-local-state.md`).
It sits in AI & LLM Engineering, covering Model routing and gateways and Agent memory. The repository describes itself as: All in one plugin for Hermes Agent ⚚ the coding intelligence, a long-term memory system and model optimized workflow packages. The licence is MIT.
When your agent uses it
- The user says: product-docs
- OMH documentation
- Oh-my-hermes documentation
- What is oh-my-hermes
Example prompts
- “/omh-docs”
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Classify the question as a public-product fact, a current-local-install
- Retrieve only the sources needed for the question. Current public facts must
- Disclose the source URL or command/path and the relevant ref, version, or
- Answer the one-shot question directly. Do not create a durable artifact
What it can do on your machine
Read from SKILL.md and the folder at commit f772a94. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Omh Docs loads about 1.5k tokens when it runs, and up to ~4.3k if it reads all its reference files. Until then it costs about 91 tokens; SKILL.md has 759 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check: notes
The automated check noted patterns worth knowing about, such as sudo or a known installer.
- NoteMentions a .env fileSKILL.md:72
print credentials, tokens, auth files, `.env` values, provider
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from rlaope/oh-my-hermes at commit f772a94, republished under its MIT licence (© rlaope). 759 words, ~1,540 tokens.
Download SKILL.mdSave it as
.claude/skills/omh-docs/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.- name
- omh-docs
- description
- [omh] Explaining OMH itself: current-source-first documentation for OMH itself: product identity, public capability catalog, model routing, local state, and long-term memory. Use when the user says: product-docs, OMH documentation, oh-my-hermes documentation, what is OMH, what is oh-my-hermes, how does OMH work, OMH capability catalog, OMH skill catalog.
OMH Docs
Use this skill to answer questions about OMH itself from current sources. It defaults to passive inspection; it is not a generic documentation writer, workflow picker, or settings workflow.
Default Behavior
- Classify the question as a public-product fact, a current-local-install fact, or both. Keep those claim sets separate in the answer.
- Retrieve only the sources needed for the question. Current public facts must
come from official
rlaope/oh-my-hermessources; current local facts must come from passive CLI output, or narrowly scoped non-secret metadata. If a diagnostic command records state, disclose that side effect before running it. - Disclose the source URL or command/path and the relevant ref, version, or commit. If freshness cannot be established or official sources conflict, name that boundary.
- Answer the one-shot question directly. Do not create a durable artifact unless the user requests one.
For a public catalog count, inspect the generated catalog on the current
official ref. For an installed count, run omh list --json and count only that
installation manifest. Never quote a remembered or embedded count.
Source Route
For public/product questions, start with live GitHub repository metadata and
the current default branch, then read the relevant current source. Load
references/product-and-sources.md for the full official-source hierarchy,
product identity, conflict handling, and disclosure shape.
For current capability and public skill-name questions, load
references/capability-map.md. It covers the six public capability families,
representative exact skill names, catalog retrieval, and the public ULW labels.
For model routing or this machine's installation, load
references/model-routing-and-local-state.md. It separates published routing
behavior from passive local inspection, the state-writing omh doctor --json
diagnostic, and safe inspection of the resolved OMH home (~/.omh by default,
but overridable).
For retained knowledge or memory questions, load
references/long-term-memory.md. It distinguishes reviewed OMH project memory
from Hermes private long-term memory and points to docs/MEMORY.md and
docs/MEMORY_CONTEXT.md.
Public Product vs Local Install
- Public-product facts describe the current official repository at a disclosed branch, tag, version, or commit. A local checkout does not silently replace that source.
- Local-install facts describe only the inspected machine/profile at a disclosed OMH version or commit. Documented paths can be absent because install profiles and enabled features differ.
- When both matter, report them under separate labels before explaining any difference.
Safety and Mutation Boundary
Never read or print credentials, tokens, auth files, .env values, provider
secrets, raw private logs, or unrelated user content. Do not broaden a metadata
question into a home-directory scan.
If the user asks to set up, install, update, repair, change settings, edit
memory, or modify code, name the appropriate specialized public workflow such
as omh-doctor, omh-skill, omh-model-setup, or omh-memory-sync, then stop
before mutation unless that separate action is authorized.
Show full SKILL.md (317 more words)Show less
Answer Contract
- Lead with the answer, then the public-product and local-install evidence that supports it.
- When both scopes matter, label the evidence
public_productandcurrent_local_installbefore explaining differences. - Cite the exact official source or disclosed local observation used.
- State version, branch, tag, or commit and the retrieval boundary.
- Name missing or conflicting evidence instead of filling it from recall.
- Mention execution/review status boundaries only when the question actually asks about status; they are not the center of this documentation skill.
Workflow Lane
- Current lane: Research and company ops. Stay read-only and return to the router when the request belongs to another workflow.
- Shared product, routing, compatibility, and evidence rules:
omh-routing/references/skill-common-rail.md.
Completion Checklist
- Answer only from disclosed current sources or bounded local observations.
- Treat wrapper metadata-only memory comparisons as advisory local context, not proof of Hermes-memory mutation or raw-entry exposure.
- Record observed delegation results; otherwise return
not_availableornot_observed. - Prepared OMH routing is not execution, review, CI, or merge evidence.
- Preserve workflow intent and stop conditions; verify before claiming completion.
- Reply in the user's own words and the host's own voice: its SOUL.md persona owns reply language, tone, speech level, and sentence endings, progress updates included (where it sets no language, use the one the user wrote in), and OMH shapes structure and content only; OMH's record terms (surface, lane, wrapper, handoff, evidence boundary, not_observed) stay in records and tool calls, never in the sentence the user reads unless they ask about one; and when a stop condition or a decision the user owns ends the turn, offer the next action as a question rather than declaring what will not be done.
- Use Hermes-native subagent/delegation features when available: native subagents -> Hermes delegation when available, otherwise sequential lanes.
Recovery Notes
- If official retrieval fails, disclose the gap and use only versioned fallback evidence.
- If local metadata is absent, report that scoped absence without expanding into private content or mutation.
© rlaope, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 4 other files (references) in skills/omh-docs of rlaope/oh-my-hermes.
- SKILL.md
- references/capability-map.md
- references/long-term-memory.md
- references/model-routing-and-local-state.md
- references/product-and-sources.md
Open the folder on GitHubat commit f772a94
Compare with similar skills
Omh Docs next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Omh Docs this skillrlaope/oh-my-hermes | 3.2k | — | ~1.5k | Automated safety check: Notes | MIT | |
| Shogun Bloom Configyohey-w/multi-agent-shogun | 1.4k | — | ~3.1k | Automated safety check: Pass | MIT | |
| Hermes Memory Providersmnemosyne-oss/mnemosyne | 3.4k | — | ~1.8k | Automated safety check: Pass | MIT | |
| Codemie Analyticscodemie-ai/codemie-code | 294 | — | ~7.5k | Automated safety check: Pass | Apache-2.0 | |
| Model Routernidhi-singh02/agent-router | 110 | — | ~1.2k | Automated safety check: Pass | MIT | |
| Ownmem Dashboardgrpcer/ownmem | 423 | — | ~563 | Automated safety check: Pass | Apache-2.0 |
Similar skills
Hermes Memory Providers
mnemosyne-oss/mnemosyne
Install and configure Mnemosyne as a Hermes Agent memory provider — local SQLite with vector search, episodic consolidation, and temporal knowledge graphs.
Codemie Analytics
codemie-ai/codemie-code
CodeMie Analytics expert — use this skill whenever the user asks about CodeMie usage data, AI adoption metrics, user leaderboards, CLI insights, spending, LiteLLM costs, token usage, or wants to…
Model Router
nidhi-singh02/agent-router
A skill your agent uses when the user asks to pick a model, subscription, or reasoning effort, or to run router status, usage refresh, or resume a router session.
Ownmem Dashboard
grpcer/ownmem
Open OwnMem Console, the local dashboard for this repository's memory.
Codex Model Routing Team
zjp1997720/codex-model-routing-team
在 Codex App 中为复杂、可并行的知识工作或编程任务自动创建多个可指定模型与推理强度的后台任务，由主 Agent 负责规划、分工、集成和验收。用于多来源调研、多章节内容、复杂 Skill/PPT、跨模块开发、独立验证或 2 个以上互不依赖工作流；也用于用户明确要求模型路由、后台 Worker、Agents Team…
More from rlaope/oh-my-hermes
All 143 skills in this repoOmh Accessibility Audit
rlaope/oh-my-hermes
[omh] Screen-reader or keyboard accessibility gaps: prepare WCAG, keyboard, focus, screen-reader, target-size, and reflow evidence gates for UI surfaces.
Omh Agent Evaluation
rlaope/oh-my-hermes
[omh] Choosing between coding agents on evidence: compare executor or agent choices on reproducible tasks using quality, cost, time, tool, and evidence metrics.
Omh Agent Instructions
rlaope/oh-my-hermes
[omh] Agent instruction file for a repo -- AGENTS.md, CLAUDE.md, a Cursor rule: write or update what an agent cannot derive from the code, inside a marked region, with every command verified or…
Omh Agent Ops Review
rlaope/oh-my-hermes
[omh] AI agent progress for managers: help managers inspect AI-agent progress, blockers, quality gates, and throughput levers.
Omh AI Slop Cleaner
rlaope/oh-my-hermes
[omh] Messy or AI-generated code to clean up: delete AI-generated slop, dead code, and duplication while observable behavior stays identical.
Omh App Debugging
rlaope/oh-my-hermes
[omh] Application code misbehaves -- a wrong value, a flaky test, a lost update: reproduce it first, form competing hypotheses, discriminate them with the cheapest observation, and only then fix the…
Related
Categories
Questions about Omh Docs
What does Omh Docs do?
[omh] Explaining OMH itself: current-source-first documentation for OMH itself: product identity, public capability catalog, model routing, local state, and long-term memory. Omh Docs is an agent skill from rlaope/oh-my-hermes. [omh] Explaining OMH itself: current-source-first documentation for OMH itself: product identity, public capability catalog, model routing, local state, and long-term memory.
When should I use Omh Docs?
Omh Docs fits situations like: the user says: product-docs; OMH documentation; oh-my-hermes documentation; what is oh-my-hermes.
How do I install Omh Docs in Claude Code?
Run `npx skills add rlaope/oh-my-hermes --skill omh-docs -a claude-code`. Or copy the skill folder (skills/omh-docs in rlaope/oh-my-hermes) into .claude/skills/omh-docs in your project. Claude Code loads it when a task matches its description.
How do I install Omh Docs in Codex?
Run `npx skills add rlaope/oh-my-hermes --skill omh-docs -a codex`. Or copy the skill folder (skills/omh-docs in rlaope/oh-my-hermes) into .agents/skills/omh-docs in your project. Codex loads it when a task matches its description.
Can I use Omh Docs in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add rlaope/oh-my-hermes --skill omh-docs -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/omh-docs, .gemini/skills/omh-docs, .github/skills/omh-docs and .opencode/skills/omh-docs in your project.
What does Omh Docs need to run?
SKILL.md names no scripts, command-line tools or credentials: Omh Docs is instructions for the agent only.
Does Omh Docs access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Omh Docs safe to install?
Our automated static check of SKILL.md found notes only (mentions a .env file), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
What licence does Omh Docs use?
Omh Docs is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Omh Docs use?
About 1.5k tokens (SKILL.md is roughly 6.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 2.8k tokens, read only when the agent opens those files.
What are the alternatives to Omh Docs?
Skills that share tags, products or a category with Omh Docs: Shogun Bloom Config (yohey-w/multi-agent-shogun, 1.4k stars), Hermes Memory Providers (mnemosyne-oss/mnemosyne, 3.4k stars), Codemie Analytics (codemie-ai/codemie-code, 294 stars) and Model Router (nidhi-singh02/agent-router, 110 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Omh Docs?
rlaope (a GitHub user) maintains it in rlaope/oh-my-hermes, which has 3,207 GitHub stars. The repository holds 143 skills in this directory. The repository was last updated on October 8, 2026.
Source: rlaope/oh-my-hermes on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.