status

Report active OMG modes and progress from local state files.

Updated Feb 23, 2026
One-click install
npx skills add https://github.com/cheafi/Trading-bot-CC --skill status-cheafi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: status
Source: https://github.com/cheafi/Trading-bot-CC/tree/main/.github/skills/status
Command: npx skills add https://github.com/cheafi/Trading-bot-CC --skill status-cheafi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It resolves uncertainty about which OMG modes are currently active and how far each one has progressed.

Core Features & Use Cases

  • Active mode detection: Reads .omg/state/ to discover which execution modes are running (e.g., omg-autopilot, ralph, ultrawork, ultraqa, team, self-improve).
  • Progress-focused reporting: Summarizes key counters such as phases/stories/cycles, tasks completed, workers active, and notable last failures.
  • Operational verification: Helps confirm correct state after a cancel or resume by showing the current state across modes.
  • Verbose diagnostics: Optionally includes full state JSON, recent git log (last 5 commits), and an .omg/ directory listing for deeper troubleshooting.

Quick Start

Ask: status --verbose to get a detailed snapshot of every active OMG mode, including full state JSON and recent commit context.

Frequently Asked Questions about status

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check the current status of active automation workflows?

Status reports OMG mode status by scanning local `.omg/state/` files to discover active execution modes like omg-autopilot, ralph, and ultrawork. It summarizes each mode's progress indicators including phases, cycles, and workers active.

How do I monitor progress indicators for running agents and pipelines?

Monitor agents and pipelines by reading local state JSON files to summarize key counters. Status reports phases, stories, cycles completed, tasks finished, workers active, and notable last failures across all active OMG execution modes.

Can I get verbose diagnostics for workflow monitoring and debugging?

Yes, you can get verbose diagnostics for workflow monitoring by requesting the `--verbose` option. Status optionally emits full state JSON, recent git commits (last 5), and an `.omg/` directory listing for deeper troubleshooting.

Does state inspection require any external dependencies or components?

State inspection requires no external dependencies or components. Status operates independently by parsing specific state JSON filenames found in the local `.omg/state/` directory to produce a formatted human-readable summary of active execution modes.

How do I verify operational state after canceling or resuming automation cycles?

To verify operational state after canceling or resuming automation cycles, status scans `.omg/state/` files to show the current state across all modes. This confirms correct state recovery across omg-autopilot, ralph, team pipelines, and ultraqa cycles.