Skills

Omh Docs

[omh] Explaining OMH itself: current-source-first documentation for OMH itself: product...

Install

npx skills add rlaope/oh-my-hermes --skill omh-docs -g -a claude-code -y
Category
Writing
Updated
3d ago
License
MIT
Context cost
Mediumabout 1,579 tokens
Runs scripts
No, instructions only

What it does

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

Product Docs

This is an OMH product-docs workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).

Why This Exists

omh-docs gives Hermes one bounded, source-first way to explain OMH itself without turning product questions into generic workflow routing or silently changing the user's installation.

Do Not Use When

  • The user wants generic documentation writing, editing, or summarization unrelated to OMH.
  • The question is about OpenAI or Hermes Agent rather than OMH; use that product's official documentation skill.
  • The user wants setup or repair.
  • The user wants to install, update, remove, or edit catalog skills.
  • The user wants model or provider settings changed.

Examples

Good example:

  • Prompt: How does OMH model routing work, and which local settings can I inspect safely?
  • Expected behavior: Separate current public behavior from this installation, retrieve official sources plus passive local metadata, disclose refs or versions, and answer without changing settings.
  • Why: The request asks for current OMH self-knowledge and local-state explanation, not a configuration change.

Bad example:

  • Prompt: Rewrite my library's API documentation and publish it.
  • Expected behavior: Do not select omh-docs; this is generic documentation authoring plus an external mutation.
  • Why: The skill explains OMH itself and does not author or publish unrelated documentation.

Completion Checklist

  • Every mutable public claim cites an official current source and ref, version, or commit.
  • Local facts name the passive command, disclosed diagnostic, or metadata path and remain separate from public-product facts.
  • No prohibited secret, raw-log, or unrelated-content source was read or printed.
  • Any requested mutation was routed to a specialized workflow and not performed without separate authorization.

Recovery Notes

Read the whole SKILL.md on GitHub

More in Writing