cancel

Detect and terminate active OMX modes with state cleanup.

Updated Apr 2, 2026
One-click install
npx skills add https://github.com/tuandzung/flink-k8s-ui --skill cancel-tuandzung
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cancel
Source: https://github.com/tuandzung/flink-k8s-ui/tree/main/.codex/skills/cancel
Command: npx skills add https://github.com/tuandzung/flink-k8s-ui --skill cancel-tuandzung

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires state-tools, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides an intelligent cancellation mechanism for OMX modes, ensuring that all active OMX modes are properly terminated and state cleanup is performed to prevent inconsistencies and errors in the system.

Core Features & Use Cases

  • Detects Active OMX Modes: Automatically identifies which OMX mode is active (e.g., Autopilot, Ralph, Ultrawork) and proceeds to cancel it.
  • Mode-Specific Cancellation: Performs specific actions based on the OMX mode detected (e.g., stopping workflows, clearing states).
  • Force Clear All: Provides an option to force clear all sessions and legacy artifacts for complete reset of the workspace.
  • Session and State Management: Handles session-aware state cleanup to ensure only the relevant session files are removed.
  • Team Cleanup: Detects and terminates tmux-based team sessions, cleaning up related state files and artifacts.
  • Use Case: For a system that utilizes OMX modes for workflow automation, this Skill ensures that workflows can be safely and cleanly terminated when needed.

Quick Start

Invoke the cancel skill to cancel the active OMX mode by simply typing: /cancel

Frequently Asked Questions about cancel

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

FAQPage Schema
How do I terminate active OMX modes like Autopilot or Ultrawork safely?

To terminate active OMX modes safely, invoke an intelligent cancellation mechanism that detects the active workflow and performs mode-specific state cleanup. This ensures proper session termination and prevents system inconsistencies.

What is the best way to clean up tmux-based team sessions during workflow termination?

The best way to clean up tmux-based team sessions during workflow termination is to use a process that detects active team sessions, terminates them, and removes related state files and artifacts for a complete reset.

Why does my system experience state inconsistencies after stopping OMX workflows?

Your system experiences state inconsistencies after stopping OMX workflows because active modes require proper session-aware state management and cleanup to remove relevant session files and legacy artifacts completely.

Can I force clear all sessions and legacy artifacts for a complete system reset?

Yes, you can force clear all sessions and legacy artifacts for a complete workspace reset. This option removes all active states and legacy data to ensure a clean environment without residual configurations.

Does session-aware state cleanup require specific dependencies to manage OMX modes?

Yes, session-aware state cleanup requires specific dependencies like state-tools to handle team state termination capabilities and ensure only the relevant session files are removed during OMX mode cancellation.