Omh Operating Rhythm logo

Omh Operating Rhythm

CommunityPopular
rlaope
omh-operating-rhythm

[omh] Hermes Operating Rhythm workflow: meeting minutes, scrum/sprint records, retros, decisions, and follow-up history. Use when the user says: operating-rhythm, operating rhythm, meeting minutes, meeting history, scrum record, sprint planning, sprint review, sprint retrospective.

Overview

Publisherrlaope
Repositoryoh-my-hermes
Skill nameomh-operating-rhythm
Stars
2.7K
Forks
194
Bundled files
Instructions only
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by rlaope on GitHub. Read the source before you install it.

Installation

Install the Omh Operating Rhythm AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/rlaope/oh-my-hermes.git /tmp/oh-my-hermes
mkdir -p .claude/skills
cp -r /tmp/oh-my-hermes/agent-skills/omh-operating-rhythm .claude/skills/omh-operating-rhythm
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Omh Operating Rhythm in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Omh Operating Rhythm on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Omh Operating Rhythm is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Operating Rhythm

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

Why This Exists

operating-rhythm exists so recurring operating work has durable minutes, decisions, and follow-up history without pretending a meeting outcome was observed.

Do Not Use When

  • The user only needs a one-off meeting agenda before the meeting; use meeting-brief.
  • The request is a weekly status/risk summary rather than cadence history; use ops-review.
  • The user asks for report packaging, PPT outline, or reliability evidence review.

Examples

Good example:

  • Prompt: operating-rhythm 회의록 히스토리 관리하고 스크럼 스프린트 회고를 정리해줘.
  • Expected behavior: Create a prepared operating record with cadence, decisions, action items, and not-evidence markers for missing observed notes.
  • Why: The request is about recurring operating history, not a generic agenda or code handoff.

Bad example:

  • Prompt: operating-rhythm implement the action items from the retro.
  • Expected behavior: Route implementation to a plan or selected executor/runtime handoff after action items are accepted.
  • Why: Operating records can capture follow-ups, but implementation is a separate observed work stream.

Completion Checklist

  • Confirm the workflow target, evidence boundary, and stop condition are named.
  • Report which outputs are prepared, observed, blocked, or missing.
  • Name the smallest next verification or handoff instead of claiming completion from narration.

Recovery Notes

  • If required context is missing, ask one blocking question or route back to the narrower workflow.
  • If runtime or wrapper evidence is unavailable, keep the status as not_observed and expose the next observable action.

Use When

Use when Hermes should prepare or maintain recurring operating records such as meetings, scrums, sprint plans, retrospectives, decisions, and follow-ups.

Strong routing signals: `operating-rhythm`, `operating rhythm`, `meeting minutes`, `meeting history`, `scrum record`, `sprint planning`, `sprint review`, `sprint retrospective`, `retro history`, `decision log`, `action item history`, `회의록 관리`, `회의 히스토리`, `운영 리듬`, `스크럼`, `스프린트 회고`, `결정 기록`, `액션 아이템`

Catalog Metadata

Category: operations Phase: rhythm-history Quality tier: operations-gated Reasoning demand: light

Quality bar:

  • Name cadence, audience, time window, known notes, and missing evidence before producing a record.
  • Separate agenda/templates from observed minutes, decisions, and action items.
  • Record follow-up ownership only when supplied or explicitly mark it unknown.

Required inputs:

  • cadence or meeting type
  • audience or participants
  • time window
  • source notes or explicit missing-notes boundary

Expected outputs:

  • operation artifact
  • decision log
  • action item history
  • observed/prepared boundary

Artifact expectations:

  • operation_artifact/v1 under .omh/operations when a wrapper or CLI records it

Safety rules:

  • Do not treat a prepared record as proof that the meeting or scrum happened.
  • Do not mark decisions or action items accepted without supplied notes or owner acknowledgement.
  • Keep implementation follow-ups separate from operating history.

Runtime Evidence

Use the current host's own tools and subagent/task mechanism when available; otherwise run the same lanes sequentially or name the unavailable capability. A prepared plan, handoff, checklist, or skill installation is not execution, review, CI, merge-readiness, or merge evidence. Report actual tool results or not_observed / not_available; never invent dispatch or host accounting. Treat supplied context as advisory, not proof of hidden memory reads or writes. State scope, constraints, verification, and the stop condition before work. Supporting paths are relative to this skill directory; sibling skill paths are relative to its parent. Resolve them from the host-provided skill base directory ({baseDir} on hosts that provide it), never a hardcoded install location. A named workflow not installed here is unavailable, not permission to emulate its host-specific capabilities. Verify through the real surface before done.

Frequently asked questions

What does the Omh Operating Rhythm AI skill do?

[omh] Hermes Operating Rhythm workflow: meeting minutes, scrum/sprint records, retros, decisions, and follow-up history. Use when the user says: operating-rhythm, operating rhythm, meeting minutes, meeting history, scrum record, sprint planning, sprint review, sprint retrospective.

Why use Omh Operating Rhythm on TypingMind?

Because you install it once and use it with any model. Omh Operating Rhythm is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Omh Operating Rhythm in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/rlaope/oh-my-hermes/tree/main/agent-skills/omh-operating-rhythm. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Omh Operating Rhythm?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Omh Operating Rhythm?

As many as you like. As long as a model supports skills, you can use Omh Operating Rhythm with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Omh Operating Rhythm AI skill free?

Yes. It is published on GitHub by rlaope under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇