skills.rest
Orinks
OrinksCOMMUNITY
Explore all skills by this author →
GitHub

cancel

Cancel active OMX modes and generate a structured cancel report.

24|2|Updated Mar 12, 2025
Search Tags:#automation#cleanup#tmux#session#state-management#cancel#omx
One-click install
npx skills add https://github.com/Orinks/AccessiWeather --skill cancel-orinks
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cancel
Source: https://github.com/Orinks/AccessiWeather/tree/main/.codex/skills/cancel
Command: npx skills add https://github.com/Orinks/AccessiWeather --skill cancel-orinks

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The cancel skill ensures safe, deterministic exit from any OMX mode by properly resetting state and preserving work where possible.

Core Features & Use Cases

  • Detects the active OMX mode across sessions and coordinates a staged shutdown.
  • Supports forceful global cleanup that clears legacy state and terminates lingering team sessions.
  • Generates a structured cancel report and leaves the workspace in a known, clean state for a fresh start.

Quick Start

Use /cancel to terminate any active OMX mode and perform safe cleanup of related state.

Frequently Asked Questions about cancel

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

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

To cancel active OMX modes and clean up state, use this skill to execute a staged shutdown across all supported sessions. It validates the session context via state tools and produces a structured cancel report to ensure a deterministic, safe exit.

What is the best way to clear legacy OMX state and terminate lingering tmux sessions?▼

The best way to clear legacy OMX state and terminate lingering tmux sessions is to trigger a forceful global cleanup. This approach clears legacy state and terminates lingering team sessions, leaving your workspace in a known, clean state for a fresh start.

How does state validation work when terminating OMX modes across multiple sessions?▼

State validation during OMX mode termination works by checking the session context via state tools before executing the shutdown. This mechanism respects per-session scope to ensure consistent termination and prevent unintended disruption of other active processes.

Do I need to manually manage session scope when running an OMX cleanup?▼

No, you do not need to manually manage session scope during an OMX cleanup. The skill automatically validates session context and respects per-session scope, coordinating a safe shutdown that preserves your work where possible without requiring manual intervention.

Why does my OMX workspace retain stale state after terminating an active mode?▼

Your OMX workspace may retain stale state if a standard termination fails to clear legacy state or lingering team sessions. Using a force-wide global cleanup ensures all related state is properly reset and leaves the workspace in a known, clean state.

Related Skills

Explore More Software Engineering Skills→
LinnanliLinnanli
1

cancel

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

Community
Advanced
YeaChan05YeaChan05

cancel

Cancel active OMX modes and emit a structured cancel report.

Community
Advanced
LinnanliLinnanli
1

worker

Executes inbox-driven tasks with startup ACKs and lifecycle management for Codex-based teams.

Community
Intermediate
ozbyozby
1

cancel

Cancel active OMX modes and clean up session state.

Community
Advanced