cancel

Cancel active OMX modes and produce a structured cancellation report.

Updated Mar 21, 2026
One-click install
npx skills add https://github.com/gtpgg1013/claude-skills-collection --skill cancel-gtpgg1013
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cancel
Source: https://github.com/gtpgg1013/claude-skills-collection/tree/main/skills/agents/cancel
Command: npx skills add https://github.com/gtpgg1013/claude-skills-collection --skill cancel-gtpgg1013

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Canceling an active OMX mode can be error-prone and leave systems in an inconsistent state. This skill provides a reliable way to terminate active modes and clean up state.

Core Features & Use Cases

  • Detects which OMX mode is active and targets the correct cleanup path (Autopilot, Ralph, Ultrawork, Ecomode, UltraQA, Swarm, Ultrapilot, Pipeline, Team).
  • Performs per-session cleanup when possible, with a force option that clears all legacy state across sessions.
  • Produces a structured cancellation report and preserves resume-ready state for Autopilot.

Quick Start

Run /cancel to terminate the current OMX session's active mode.

Frequently Asked Questions about cancel

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

FAQPage Schema
How do I cancel an active OMX mode and reset the system state?

To cancel an active OMX mode, run a single command to terminate the session and trigger dependency-aware cleanup. This restores a clean system state by executing per-session termination and generating a structured cancellation report.

What OMX modes can I terminate using a state-reset command?

You can terminate Autopilot, Ralph, Ultrawork, Ecomode, UltraQA, Swarm, Ultrapilot, Pipeline, and Team modes. The command detects the active mode and targets the correct per-session cleanup path to ensure proper termination.

How do I force clear all legacy state across OMX sessions?

You can use the --force option to perform broad resets that clear all legacy state across sessions. This overrides per-session cleanup to ensure a comprehensive state reset across all active and residual OMX modes.

Why does an OMX mode cancel leave my system in an inconsistent state?

Standard OMX cancellation can be error-prone and leave inconsistent state without proper team-aware cleanup. Applying a structured cancellation command ensures dependency-aware termination steps are followed for a reliable state reset.

Can I preserve a resume-ready state when canceling Autopilot mode?

Yes, the OMX cancellation process preserves resume-ready state specifically for Autopilot mode. While performing team-aware cleanup and terminating the active session, it safeguards the necessary data to resume Autopilot later.