agentleFS
lza6lza6/claw-code-tingfeng/skills/hud/SKILL.md

hud

Skill5 starsChanged 12 days agoMITView on GitHub

Show or configure the OMX HUD (two-layer statusline)

9 other projects use a version of this, 1 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use ultragoal, ask and 2 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • Yeachan-HeoSkill

    ultragoal

    Create and execute durable repo-native multi-goal plans over Codex goal mode artifacts.

    Also in 3 projects that use this

  • dubwoahSkill

    ask

    Answer questions about the codebase without generating or modifying any code. Use when the user wants to understand how something works, find where something is defined, or explore the project structure. Invoked with /ask.

    Also in 4 projects that use this

  • javatarzSkill

    wiki

    Access and manage the local GitHub Wiki clone. Use this skill when you need to read wiki content (architecture, design docs, guides), update wiki documentation, check wiki status, or push wiki changes. The wiki contains high-level system design and architectural documentation.

    Also in 3 projects that use this

  • GitHubSkill

    autoresearch

    Autonomous iterative experimentation loop for any programming task. Guides the user through defining goals, measurable metrics, and scope constraints, then runs an autonomous loop of code changes, testing, measuring, and keeping/discarding results. Inspired by Karpathy''s autoresearch. USE FOR: autonomous improvement, iterative optimization, experiment loop, auto research, performance tuning, automated experimentation, hill climbing, try things automatically, optimize code, run experiments, autonomous coding loop. DO NOT USE FOR: one-shot tasks, simple bug fixes, code review, or tasks without a measurable metric.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

6 rules. 0 are common, 3 are distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 6 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Default preset is focused.

    line 60
  2. Distinctive:

    If the TUI statusline is not showing:

    line 102
  3. Distinctive:

    Ensure Codex CLI v0.101.0+ is installed

    line 103
  4. Very specific:

    Run omx setup to configure [tui] section

    line 104
  5. Very specific:

    If omx hud shows "No active modes":

    line 107
  6. Distinctive:

    Start a workflow (ralph, autopilot, etc.) and check again

    line 109

“Common” is measured: kept by at least 6 in 10 of the 6 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

clawd 路径适配(重要):本技能移植自 oh-my-codex,文中所有 ~/.codex/...、 .codex/skills/、CODEX_HOME 都是 Codex 时代的路径。在 clawd 里真实生效的是:

  • 技能位置:<项目>/skills/<name>/SKILL.md(支持分组子目录,如 skills/reverse/<sub>/SKILL.md,发现逻辑是递归的)
  • 运行期数据/配置:<项目>/.clawd/(sessions/、logs/、features.json 等)
  • 查当前实际发现到的技能:clawd hud 或直接调 skill 工具;诊断环境用 clawd doctor

只有当你确实在 Codex 里运行本技能时,~/.codex/... 那套路径才成立。 在 clawd 里照着 ~/.codex/... 找文件只会得到"不存在"。

HUD Skill

The OMX HUD uses a two-layer architecture:

  1. Layer 1 - Codex built-in statusLine: Real-time TUI footer showing model, git branch, and context usage. Configured via [tui] status_line in ~/.codex/config.toml. Zero code required.
  2. Layer 2 - omx hud CLI command: Shows OMX-specific orchestration state (ralph, ultrawork, autopilot, team, pipeline, ecomode, turns). Reads .omx/state/ files.

Quick Commands

CommandDescription
omx hudShow current HUD (modes, turns, activity)
omx hud --watchLive-updating display (polls every 1s)
omx hud --jsonRaw state output for scripting
omx hud --preset=minimalMinimal display
omx hud --preset=focusedDefault display
omx hud --preset=fullAll elements

Presets

minimal

[OMX] ralph:3/10 | turns:42

focused (default)

[OMX] ralph:3/10 | ultrawork | team:3 workers | turns:42 | last:5s ago

full

[OMX] ralph:3/10 | ultrawork | autopilot:execution | team:3 workers | pipeline:exec | turns:42 | last:5s ago | total-turns:156

Setup

omx setup automatically configures both layers:

  • Adds [tui] status_line to ~/.codex/config.toml (Layer 1)
  • Writes .omx/hud-config.json with default preset (Layer 2)
  • Default preset is focused; if HUD/statusline changes do not appear, restart Codex CLI once.

Layer 1: Codex Built-in StatusLine

Configured in ~/.codex/config.toml:

[tui]
status_line = ["model-with-reasoning", "git-branch", "context-remaining"]

Available built-in items (Codex CLI v0.101.0+): model-name, model-with-reasoning, current-dir, project-root, git-branch, context-remaining, context-used, five-hour-limit, weekly-limit, codex-version, context-window-size, used-tokens, total-input-tokens, total-output-tokens, session-id

Layer 2: OMX Orchestration HUD

The omx hud command reads these state files:

  • .omx/state/ralph-state.json - Ralph loop iteration
  • .omx/state/ultrawork-state.json - Ultrawork mode
  • .omx/state/autopilot-state.json - Autopilot phase
  • .omx/state/team-state.json - Team workers
  • .omx/state/pipeline-state.json - Pipeline stage
  • .omx/state/ecomode-state.json - Ecomode active
  • .omx/state/hud-state.json - Last activity (from notify hook)
  • .omx/metrics.json - Turn counts

Configuration

HUD config stored at .omx/hud-config.json:

{
  "preset": "focused"
}

Color Coding

  • Green: Normal/healthy
  • Yellow: Warning (ralph >70% of max)
  • Red: Critical (ralph >90% of max)

Troubleshooting

If the TUI statusline is not showing:

  1. Ensure Codex CLI v0.101.0+ is installed
  2. Run omx setup to configure [tui] section
  3. Restart Codex CLI

If omx hud shows "No active modes":

  • This is expected when no workflows are running
  • Start a workflow (ralph, autopilot, etc.) and check again

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.