New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Omh Running Work Board

by rlaope in rlaope/oh-my-hermes

[omh] Live view of running coding units: showing which coding units are running right now, on which runtime and model, with observed tokens and elapsed time.

MITAuto-check passed

Install Omh Running Work Board

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

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

GitHub CLI
$ gh skill install rlaope/oh-my-hermes omh-running-work-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-running-work-board .claude/skills/omh-running-work-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-running-work-board
GitHub stars
3.2k
Token cost
~1.4k tokens
SKILL.md length
702 words
Files
1
Skills in repo
143
Repo updated
First seen
Licence
MIT

At a glance

[omh] Live view of running coding units: showing which coding units are running right now, on which runtime and model, with observed tokens and elapsed time.

  • The user says: running-work-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
  • Running work board

What it does

Omh Running Work Board is an agent skill from rlaope/oh-my-hermes. [omh] Live view of running coding units: showing which coding units are running right now, on which runtime and model, with observed tokens and elapsed time. Use when the user says: running-work-board, running work board, which units are running, what models are running, 지금 뭐 돌고 있어, 뭐가 돌고 있어, 어떤 모델로 돌고 있어, 실행 중인 작업 보여줘.

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

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: running-work-board
  • Running work board
  • Which units are running
  • What models are running

Example prompts

  • “/omh-running-work-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.

    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 Running Work Board loads about 1.4k tokens when it runs. Until then it costs about 86 tokens; SKILL.md has 702 words of instructions outside code blocks.

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

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). 702 words, ~1,379 tokens.

Download SKILL.mdSave it as .claude/skills/omh-running-work-board/SKILL.md (or your agent's skills folder).
name
omh-running-work-board
description
[omh] Live view of running coding units: showing which coding units are running right now, on which runtime and model, with observed tokens and elapsed time. Use when the user says: running-work-board, running work board, which units are running, what models are running, 지금 뭐 돌고 있어, 뭐가 돌고 있어, 어떤 모델로 돌고 있어, 실행 중인 작업 보여줘.

Running Work Board

This is a Hermes-native running-work-board workflow skill.

Why This Exists

running-work-board exists because multi-session coding work was invisible: the runtime was tracked but the model was dropped, token counts had no write site at all, and a blocking dispatch could not report that it was still running. The board answers which model on which runtime, or says unknown.

Do Not Use When

  • The user wants to start, plan, or dispatch coding work rather than observe it.
  • The user wants review, CI, or merge evidence, which a status board never provides.
  • The user is asking about their own application's runtime status rather than OMH coding units.

Examples

Good example:

  • Prompt: what is running right now
  • Expected behavior: One line per unit: label, runtime, model, status, elapsed, tokens, with unknown printed where nothing was observed.
  • Why: The request is about observed local coding activity, not about starting work.

Bad example:

  • Prompt: is the deploy done and did CI pass
  • Expected behavior: Route to verification or CI evidence instead of the activity board.
  • Why: Observed activity is not result, review, CI, or merge evidence.

Completion Checklist

  • Runtime and model are named per unit, or explicitly reported as unknown.
  • Token counts and session references are observed values or the literal unknown, never estimates.
  • Elapsed time for an unfinished unit comes from its start marker, which cannot prove the unit is still alive.
  • The board is labelled observed activity, not result, verification, review, CI, or merge evidence.

Recovery Notes

  • If no units are found, say so plainly rather than implying nothing ever ran.
  • If a marker is stale because a process died, report it as observed-start-without-end instead of claiming the unit is running.
  • If tokens are unknown for a runtime with no structured output, say the runtime does not report them.

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 the user asks what coding work is running right now -- which unit, which runtime, which model, how long, how many tokens -- rather than asking to start, plan, or review work.

Strong routing signals: `running-work-board`, `running work board`, `which units are running`, `what models are running`, `지금 뭐 돌고 있어`, `뭐가 돌고 있어`, `어떤 모델로 돌고 있어`, `실행 중인 작업 보여줘`
Show full SKILL.md (293 more words)Show less

Catalog Metadata

Category: operator Phase: observability Hermes role: tracker Quality tier: evidence-gated Reasoning demand: light

Quality bar:

  • Name the workflow target, constraints, validation evidence, and stop condition.
  • Separate Hermes guidance from executor or wrapper behavior unless evidence proves the step happened.

Handoff policy:

Read local dispatch and progress artifacts directly and render the board; never dispatch or modify a unit from this workflow.

Required inputs:

  • local coding artifacts

Expected outputs:

  • per-unit runtime and model
  • observed tokens and elapsed
  • explicit unknowns

Artifact expectations:

  • metadata-only status board projection from local artifacts

Safety rules:

  • Do not imply hidden Hermes runtime behavior.
  • Use the smallest verification that can prove the claim.

Runtime Evidence

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-running-work-board of rlaope/oh-my-hermes.

Open the folder on GitHubat commit 7cd0d02

Compare with similar skills

Omh Running Work 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 Running Work Board compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Omh Running Work Board this skillrlaope/oh-my-hermes3.2k—~1.4kAutomated safety check: PassMIT
Boardalirezarezvani/claude-skills28k—~610Automated safety check: PassMIT
Unit Teststhedaviddias/Front-End-Checklist74k—~382Automated safety check: PassMIT
Warp Rust Unit Testswarpdotdev/warp65k1 repos~3.4kAutomated safety check: PassAGPL-3.0
Paperclip Boardpaperclipai/paperclip100k—~5.3kAutomated safety check: PassMIT
Writing Unit TestsTriliumNext/Trilium38k—~3.2kAutomated safety check: PassAGPL-3.0

Similar skills

  • Board

    alirezarezvani/claude-skills

    Read, write, and browse the AgentHub message board for agent coordination.

    28k GitHub stars~610 tokensUpdated 1 mo ago
    Agent WorkflowsAuto-check passed

  • Unit Tests

    thedaviddias/Front-End-Checklist

    A skill your agent uses when reviewing CI coverage, automated checks, or test strategy related to Write unit tests.

    74k GitHub stars~382 tokensUpdated 5 days ago
    Testing & QAAuto-check passed

  • Warp Rust Unit Tests

    warpdotdev/warp

    Guides writing, improving and running crate-level Rust unit tests in the Warp codebase, and says when a unit test is the wrong level.

    65k GitHub starsUsed in 1 repo~3.4k tokens
    Testing & QAAuto-check passed

  • Paperclip Board

    paperclipai/paperclip

    Manage a Paperclip company as a board member via chat. An agent skill from paperclipai/paperclip.

    100k GitHub stars~5.3k tokensUpdated today
    Auto-check passed

  • Writing Unit Tests

    TriliumNext/Trilium

    A skill your agent uses when writing, extending, or debugging Vitest unit tests anywhere in the Trilium monorepo — Preact components, jQuery widgets, client services, or the server/trilium-core…

    38k GitHub stars~3.2k tokensUpdated today
    Testing & QAAuto-check passed

  • Responsive Units

    thedaviddias/Front-End-Checklist

    A skill your agent uses when reviewing stylesheets, component styles, and responsive behavior related to Use relative units for responsive layouts.

    74k GitHub stars~472 tokensUpdated 5 days ago
    Frontend & DesignAuto-check passed

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

  • Omh Agent Debug

    rlaope/oh-my-hermes

    [omh] Agent is stuck, looping, or drifting: capture a stuck, looping, drifting, or repeatedly failing agent run, diagnose the likely failure pattern, and prepare the smallest safe recovery action.

    3.3k GitHub stars~2k 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.3k 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.3k 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.3k 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.3k GitHub stars~2.7k tokensUpdated today
    Auto-check passed

Questions about Omh Running Work Board

What does Omh Running Work Board do?

[omh] Live view of running coding units: showing which coding units are running right now, on which runtime and model, with observed tokens and elapsed time. Omh Running Work Board is an agent skill from rlaope/oh-my-hermes. [omh] Live view of running coding units: showing which coding units are running right now, on which runtime and model, with observed tokens and elapsed time.

When should I use Omh Running Work Board?

Omh Running Work Board fits situations like: the user says: running-work-board; running work board; which units are running; what models are running.

How do I install Omh Running Work Board in Claude Code?

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

How do I install Omh Running Work Board in Codex?

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

Can I use Omh Running Work 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-running-work-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-running-work-board, .gemini/skills/omh-running-work-board, .github/skills/omh-running-work-board and .opencode/skills/omh-running-work-board in your project.

What does Omh Running Work Board need to run?

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

Does Omh Running Work 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 Running Work 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 Running Work Board use?

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

About 1.4k tokens (SKILL.md is roughly 5.5k 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 Running Work Board?

Skills that share tags, products or a category with Omh Running Work Board: Board (alirezarezvani/claude-skills, 28k stars), Unit Tests (thedaviddias/Front-End-Checklist, 74k stars), Warp Rust Unit Tests (warpdotdev/warp, 65k stars) and Paperclip Board (paperclipai/paperclip, 100k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Omh Running Work 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.