Agent skill

Omh Agent Board

by rlaope in rlaope/oh-my-hermes

[omh] Coordinating several agents or profiles: coordinate multiple Hermes profiles or agents with task, handoff, heartbeat, blocker, and completion states.

MITAuto-check passedProductivity & Automation

Install Omh Agent Board

skills CLI
$ npx skills add rlaope/oh-my-hermes --skill omh-agent-board -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install rlaope/oh-my-hermes omh-agent-board --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/rlaope/oh-my-hermes.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/omh-agent-board .claude/skills/omh-agent-board && rm -rf skills-src

Use ~/.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/

Facts

Skill name
omh-agent-board
GitHub stars
3.2k
Token cost
~1.9k tokens
SKILL.md length
908 words
Files
1
Skills in repo
143
Repo updated
First seen
Licence
MIT

At a glance

[omh] Coordinating several agents or profiles: coordinate multiple Hermes profiles or agents with task, handoff, heartbeat, blocker, and completion states.

  • The user says: agent-board
  • SKILL.md covers Why This Exists, Do Not Use When, Examples and Completion Checklist, plus 5 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • Multi agent board

What it does

Omh Agent Board is an agent skill from rlaope/oh-my-hermes. [omh] Coordinating several agents or profiles: coordinate multiple Hermes profiles or agents with task, handoff, heartbeat, blocker, and completion states. Use when the user says: agent-board, agent board, kanban, multi-agent, multi agent, multi agent board, multiple hermes agents, multiple hermes profiles.

Its SKILL.md is about 1.9k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Productivity & Automation, covering Task management and Multi-agent orchestration. 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: agent-board
  • Multi agent board
  • Multiple hermes agents
  • Multiple hermes profiles

Example prompts

  • “/omh-agent-board”

What it can do on your machine

Read from SKILL.md and the folder at commit 7cd0d02. 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 (its code samples are bash).

    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 Agent Board loads about 1.9k tokens when it runs. Until then it costs about 81 tokens; SKILL.md has 908 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~81
When it runs · the whole SKILL.md, loaded when a task matches
~1.9k

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 passed

The automated check found no risky patterns in SKILL.md.

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 7cd0d02, republished under its MIT licence (© rlaope). 908 words, ~1,912 tokens.

Download SKILL.mdSave it as .claude/skills/omh-agent-board/SKILL.md (or your agent's skills folder).
name
omh-agent-board
description
[omh] Coordinating several agents or profiles: coordinate multiple Hermes profiles or agents with task, handoff, heartbeat, blocker, and completion states. Use when the user says: agent-board, agent board, kanban, multi-agent, multi agent, multi agent board, multiple hermes agents, multiple hermes profiles.

Agent Board

This is a Hermes-native agent-board workflow skill.

Why This Exists

agent-board exists so Hermes users can ask for this workflow in chat and get a structured, checkable answer instead of an improvised one.

Do Not Use When

  • The request is already handled by a narrower explicit skill with stronger evidence.
  • The user asks OMH to secretly run external platforms, connectors, schedulers, file exports, or runtime agents.
  • The only safe answer is to ask for missing authority, credentials, target, or observed evidence first.
  • A multi-lane implementation of an accepted plan is ultrawork, which prepares its durable lanes through this board.

Examples

Good example:

  • Prompt: agent-board coordinate PM, CTO, QA, and release agents on this launch checklist.
  • Expected behavior: Produce prepare_agent_board_card with required context, wrapper actions, and not-evidence boundaries.
  • Why: The prompt names a real workflow surface that Hermes can orchestrate without hiding execution.

Bad example:

  • Prompt: agent-board mark the other agent complete without an observed heartbeat or result.
  • Expected behavior: Report the missing observed evidence or authority instead of claiming the external step happened.
  • Why: Prepared OMH guidance is not platform, runtime, connector, file, memory, or delivery evidence.

Completion Checklist

  • Choose the coordination from the request: durable (restart survival, cross-profile pickup) prepares a kanban_* action on the named board; bounded_research prepares one delegate_task action. Never substitute one route for the other when its surface is missing.
  • Call omh_agent_board prepare, then invoke the returned native_action through the normal Hermes tool loop; OMH never calls a native tool itself and grants no host permission.
  • Report the request state exactly: prepared, unavailable (named missing_capabilities, zero native calls), denied, observed, or failed. A complete receipt implies no review approval, CI, or merge; a running readback is a claim, not dispatch proof.
  • Agent/operator reference: docs/AGENT-BOARD.md; wrapper actions example: examples/agent-board/native-actions.json.

Recovery Notes

  • If prepare returns unavailable, name the missing capability (tool, schema, hook, host identity, board binding, or native compare-and-swap) and keep the card prepared-only.
  • If a receipt is failed or requires_reconciliation, run an observed show on the same task before the next mutation; never retry a create automatically. Repeating a create with the same request_id returns the already observed task.
  • No native kanban_dispatch tool exists: dispatch stays unavailable and an operator claim is the observed path. A positive request_changes needs a review-claimed run from the host's own review dispatcher.

Workflow Lane

  • Current lane: Automation and status (achievements, workspace-audit, production-audit, live-incident-response, automation-blueprint, github-event-ops, github-issue-intake, buzz, +39 more) - schedules, status, health, and ops review.
  • If intent belongs to another lane, hand back to oh-my-hermes or name the adjacent workflow.
  • Shared product, routing, compatibility, and evidence rules: omh-routing/references/skill-common-rail.md.

Use When

Use when multiple Hermes profiles, agents, or targets need a board-shaped status contract for collaborative work.

Strong routing signals: `agent-board`, `agent board`, `kanban`, `multi-agent`, `multi agent`, `multi agent board`, `multiple hermes agents`, `multiple hermes profiles`, `hermes profiles`, `subagent`, `subagents`, `sub agent`, `sub agents`, `agent coordination`, `agent task board`, `task board`, `roles and board`, `role board`, `heartbeat`, `blocker`, `agent blocker`, `agent heartbeat`, `agent handoff`, `handoff board`, `interviewer reviewer builder`, `reviewer builder`, `칸반`, `멀티 에이전트`, `서브에이전트`, `서브 에이전트`, `여러 에이전트`, `Hermes agent 여러 명`, `여러 명이 같이 일`, `에이전트 보드`, `작업 배분`, `역할 배분`, `작업 보드`, `역할과 보드`, `역할 보드`
Show full SKILL.md (377 more words)Show less

Catalog Metadata

Category: agent-coordination Phase: board-status Hermes role: tracker Quality tier: workflow-surface-gated Reasoning demand: standard

Quality bar:

  • Name the user-facing workflow objective, required context, next action, and stop condition.
  • Separate prepared guidance from observed platform, runtime, connector, file, memory, or delivery evidence.
  • Expose missing tools, credentials, targets, or observations as user-visible gaps.

Handoff policy:

Keep this as Hermes-facing orchestration guidance first. Prepare executor, connector, gateway, or host-runtime handoff only when the user accepts that next step and observed evidence can be recorded.

Required inputs:

  • user request
  • target context
  • delivery or status expectation
  • known missing evidence

Expected outputs:

  • agent-board/v1 card or guidance
  • agent_board_request/v1 record from the omh_agent_board plugin tool
  • next action
  • prepared-vs-observed boundary

Artifact expectations:

  • agent-board/v1 metadata-only runtime or wrapper card when recorded
  • agent_board_state/v1 bounded board snapshot under the OMH home: request digests, receipts, and task references only; never raw bodies, comments, attachments, or host identity

Safety rules:

  • An agent board card is not proof that another Hermes agent accepted, executed, heartbeat-ed, or completed work unless target-specific evidence exists.
  • Do not claim connector, gateway, runtime, file generation, memory mutation, or host automation evidence from prepared guidance.

Runtime Evidence

Preferred harness for this skill: agent-board.

sh
omh runtime record --skill agent-board --harness agent-board --status started

Record observed delegation results; otherwise return not_available or not_observed. Prepared OMH routing is not execution, review, CI, merge-readiness, or merge evidence.

  • Treat wrapper memory/context summaries as advisory local context, not proof of opaque Hermes memory reads or changes. 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.

Shared product, compatibility, topology, memory, harness, and execution rules: omh-routing/references/skill-common-rail.md. Load it when applicable; otherwise name an unavailable capability.

© 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

Just SKILL.md in skills/omh-agent-board of rlaope/oh-my-hermes.

Open the folder on GitHubat commit 7cd0d02

Compare with similar skills

Omh Agent Board 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.

Omh Agent Board compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Omh Agent Board this skillrlaope/oh-my-hermes3.2k—~1.9kAutomated safety check: PassMIT
Superset Agent Standupsuperset-sh/superset15k—~712Automated safety check: PassCustom licence
Pi Messenger Crewnicobailon/pi-messenger719—~3.7kAutomated safety check: PassNone
AgentRQ Supervisoragentrq/agentrq1.1k—~2.7kAutomated safety check: PassAGPL-3.0
AI Fleet Project ExecutionSzotasz/marveen117—~14kAutomated safety check: PassMIT
Agent NetworkaAAaqwq/AGI-Super-Team105—~2kAutomated safety check: PassMIT

Similar skills

  • Superset Agent Standup

    superset-sh/superset

    Sweeps every Superset workspace, task and agent terminal to report what finished, what needs review and what is blocked, read-only, and can publish the digest as a page.

    15k GitHub stars~712 tokensUpdated yesterday
    Productivity & AutomationAuto-check passed
  • Pi Messenger Crew

    nicobailon/pi-messenger

    Orchestrator reference for pi-messenger Crew planning, task management, configuration, and agent coordination.

    719 GitHub stars~3.7k tokensUpdated 1 mo ago
    Productivity & AutomationAuto-check passed
  • AgentRQ Supervisor

    agentrq/agentrq

    Orchestrates work across specialized AgentRQ workspaces, breaking goals into tasks, assigning them to the right workspace agent, and tracking shared learning notes.

    1.1k GitHub stars~2.7k tokensUpdated today
    Productivity & AutomationAuto-check passed
  • AI fleet project execution (orchestrator=PM, marketing agent, backend dev agent, video agent).

    117 GitHub stars~14k tokensUpdated today
    Productivity & AutomationAuto-check passed
  • Agent Network

    aAAaqwq/AGI-Super-Team

    Multi-Agent group chat collaboration system inspired by DingTalk/Lark.

    105 GitHub stars~2k tokensUpdated 2 days ago
    Productivity & AutomationAuto-check passed
  • Kanban Video Orchestrator

    Luciole-Studio/Misaka-Agent

    Plan and run multi-agent video production pipelines. An agent skill from Luciole-Studio/Misaka-Agent.

    171 GitHub starsUsed in 2 repos~2.4k tokens
    Productivity & AutomationAuto-check: notes

More from rlaope/oh-my-hermes

All 143 skills in this repo
  • Omh 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.

    3.2k GitHub stars~2.8k tokensUpdated today
    Auto-check passed
  • 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.

    3.2k GitHub stars~2.1k tokensUpdated today
    Auto-check passed
  • 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…

    3.2k GitHub stars~2.2k tokensUpdated today
    Auto-check passed
  • 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.

    3.2k GitHub stars~1.9k tokensUpdated today
    Auto-check passed
  • 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.

    3.2k GitHub stars~2.7k tokensUpdated today
    Auto-check passed
  • 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…

    3.2k GitHub stars~2.3k tokensUpdated today
    Auto-check passed

Questions about Omh Agent Board

What does Omh Agent Board do?

[omh] Coordinating several agents or profiles: coordinate multiple Hermes profiles or agents with task, handoff, heartbeat, blocker, and completion states. Omh Agent Board is an agent skill from rlaope/oh-my-hermes. [omh] Coordinating several agents or profiles: coordinate multiple Hermes profiles or agents with task, handoff, heartbeat, blocker, and completion states.

When should I use Omh Agent Board?

Omh Agent Board fits situations like: the user says: agent-board; multi agent board; multiple hermes agents; multiple hermes profiles.

How do I install Omh Agent Board in Claude Code?

Run `npx skills add rlaope/oh-my-hermes --skill omh-agent-board -a claude-code`. Or copy the skill folder (skills/omh-agent-board in rlaope/oh-my-hermes) into .claude/skills/omh-agent-board in your project. Claude Code loads it when a task matches its description.

How do I install Omh Agent Board in Codex?

Run `npx skills add rlaope/oh-my-hermes --skill omh-agent-board -a codex`. Or copy the skill folder (skills/omh-agent-board in rlaope/oh-my-hermes) into .agents/skills/omh-agent-board in your project. Codex loads it when a task matches its description.

Can I use Omh Agent Board 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-agent-board -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-agent-board, .gemini/skills/omh-agent-board, .github/skills/omh-agent-board and .opencode/skills/omh-agent-board in your project.

What does Omh Agent Board need to run?

SKILL.md names no scripts, command-line tools or credentials: Omh Agent Board is instructions for the agent only.

Does Omh Agent Board 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 Agent Board safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Omh Agent Board use?

Omh Agent Board 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 Agent Board use?

About 1.9k tokens (SKILL.md is roughly 7.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Omh Agent Board?

Skills that share tags, products or a category with Omh Agent Board: Superset Agent Standup (superset-sh/superset, 15k stars), Pi Messenger Crew (nicobailon/pi-messenger, 719 stars), AgentRQ Supervisor (agentrq/agentrq, 1.1k stars) and AI Fleet Project Execution (Szotasz/marveen, 117 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Omh Agent Board?

rlaope (a GitHub user) maintains it in rlaope/oh-my-hermes, which has 3,243 GitHub stars. The repository holds 143 skills in this directory. The repository was last updated on October 10, 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.