skills.rest
wmasfoe
wmasfoeCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

cancel

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

Updated Apr 23, 2026
Search Tags:#cleanup#tmux#session#team#state#cancel#omx
One-click install
npx skills add https://github.com/wmasfoe/notch-pet --skill cancel-wmasfoe
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cancel
Source: https://github.com/wmasfoe/notch-pet/tree/main/.codex/skills/cancel
Command: npx skills add https://github.com/wmasfoe/notch-pet --skill cancel-wmasfoe

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

OMX mode chaos and stale session data degrade automation workflows. The cancel skill provides a safe, standardized way to terminate active OMX modes and reset state to a clean baseline, enabling reliable resumes and predictable outcomes.

Core Features & Use Cases

  • Session-aware cancellation that detects active modes across multiple sessions and stops them without disrupting unrelated work.
  • Support for forceful global cleanup to purge legacy state and reset the workspace when needed.
  • Team-aware cleanup with graceful shutdown, comprehensive reporting, and state cleanup for tmux-based collaborations.
  • Dependency-aware, staged cancellation that preserves useful progress (where applicable) and ensures safe cleanup of linked modes.
  • Detailed structured cancel reports to communicate results and next steps.

Quick Start

Initiate a cancellation with the cancel command to stop all active OMX modes and clean up related state.

Frequently Asked Questions about cancel

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

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

To stop active OMX modes and clean up session state safely, trigger a cancellation workflow that leverages state_list_active and state_get_status for dependency-aware termination. This ensures proper shutdown across autopilot, ultrawork, and other modes without disrupting unrelated work.

What is the best way to terminate OMX team sessions in tmux without losing clean state?▼

Terminating OMX team sessions in tmux requires a team-aware cleanup process that executes graceful shutdowns. This approach provides comprehensive reporting and clears session-scoped state, ensuring a clean baseline for future collaborations.

Does OMX mode cancellation support forceful global cleanup for legacy state?▼

Yes, OMX mode cancellation supports forceful global cleanup to purge legacy state. This force path resets the entire workspace environment when standard non-force termination is insufficient to clear stale automation data.

When should I use a force cancel instead of a standard session-aware termination?▼

You should use a force cancel when stale session data degrades automation workflows and standard session-aware termination fails. The force path purges legacy state globally, whereas the non-force path targets specific active modes safely.

How do I reset OMX automation workflows after an unexpected session disruption?▼

Resetting OMX automation workflows after a disruption involves canceling active modes to reset state to a clean baseline. This standardized cleanup enables reliable workflow resumes and predictable outcomes across affected sessions.

Related Skills

Explore More Software Engineering Skills→
SteveBronderSteveBronder
1

switch_modes-skl

Switch the active agent mode by updating a state file.

Community
Basic
pextacypextacy

cancel

Cancel active OMX modes and clean up session state.

Community
Advanced
tiankong0101-bytetiankong0101-byte

cancel

Cancel active OMC modes and clear their state safely.

Community
Advanced
HmbownHmbown
105

power-word-kill

Hard terminate a misbehaving process and document the kill decision.

Community
Advanced