skills.rest
ozby
ozbyCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

cancel

Cancel active OMX modes and clean up session state.

1|Updated Mar 17, 2025
Search Tags:#automation#tmux#state-management#workflows#cancel#omx#team-cleanup
One-click install
npx skills add https://github.com/ozby/node-pubsub --skill cancel-ozby
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cancel
Source: https://github.com/ozby/node-pubsub/tree/main/.codex/skills/cancel
Command: npx skills add https://github.com/ozby/node-pubsub --skill cancel-ozby

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Canceling active OMX modes to restore clean operational state across sessions and workflows.

Core Features & Use Cases

  • Graceful termination of Autopilot, Ralph, Ultrawork, UltraQA, Swarm, Ultrapilot, Pipeline, and Team modes.
  • Preserves progress for resume where applicable (Autopilot), and cleans up dependent states without affecting unrelated sessions.
  • Structured cancel reports and safe fallback for force cleanup.

Quick Start

Invoke /cancel to terminate the active OMX mode and clean up its session state.

Frequently Asked Questions about cancel

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

FAQPage Schema
How do I cancel active OMX modes and clean up session state?▼

Cancel active OMX modes by invoking the cancel command to terminate workflows and clear session state using state_clear. This safely restores clean operational state across all supported modes including autopilot, ralph, and swarm.

What is the best way to terminate OMX team mode and remove tmux directories?▼

Terminate OMX team mode by requesting force-wide cleanup, which handles team cleanup via tmux session termination and directory removal. This ensures dependent states are fully cleaned without affecting unrelated workspace sessions.

Does canceling OMX workflows preserve progress for resume?▼

Canceling OMX workflows preserves progress for resume where applicable, specifically for Autopilot mode. It cleans up dependent states gracefully without data loss, allowing workflows to be resumed from their last saved state.

Can I force cleanup all active OMX modes across the workspace at once?▼

You can force cleanup all active OMX modes across the workspace using optional force-wide cancellation. The Skill relies on state_list_active and state_get_status to determine active modes before applying state_clear for comprehensive cleanup.

What OMX modes are supported for graceful termination?▼

Supported OMX modes for graceful termination include autopilot, ralph, ultrawork, ecomode, ultraqa, swarm, ultrapilot, pipeline, and team. Per-session cancellation applies to each mode individually with structured cancel reports.

Why does OMX mode cancellation fail to clean up dependent states?▼

OMX mode cancellation may fail if session state tooling cannot determine active modes. Use force-wide cleanup as a safe fallback to ensure state_clear executes and dependent states are removed via tmux and directory cleanup.

Related Skills

Explore More Software Engineering Skills→
wmasfoewmasfoe

cancel

Cancel active OMX modes across sessions with dependency-aware state cleanup.

Community
Advanced
LinnanliLinnanli
1

cancel

Cancel active OMX modes and clean up related state across sessions.

Community
Advanced
koasis89koasis89

cancel

Cancel active OMX modes with session-aware state cleanup.

Community
Advanced
riethmayerriethmayer
2

cancel

Cancel active OMX modes and clean up associated state.

Community
Advanced