cancel

Cancel active OMG modes with session-aware cleanup and forced file clearing.

Updated May 30, 2026
One-click install
npx skills add https://github.com/kwt00/oh-my-grok --skill cancel-kwt00
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cancel
Source: https://github.com/kwt00/oh-my-grok/tree/main/skills/cancel
Command: npx skills add https://github.com/kwt00/oh-my-grok --skill cancel-kwt00

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill provides an efficient way to cancel any active OMG mode, ensuring a clean exit from workflows and preserving the state for future use.

Core Features & Use Cases

  • Intelligent Mode Detection: Automatically identifies the active OMG mode and cancels it appropriately.
  • Session-aware Cleanup: Clears session-specific files while preserving progress for resumption.
  • Forced Clear Option: Erases all state files and legacy artifacts when needed.
  • Use Case: Suppose you are running an Ultrawork session and need to interrupt it. Using this Skill allows you to cancel the session and clean up all related state, ready for a fresh start.

Quick Start

Use the cancel skill to stop all active OMG modes with the command '/oh-my-grok:cancel'.

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 OMG mode and clean up session state?

To cancel an active OMG mode, invoke the cancel skill to automatically detect the workflow, perform graceful shutdown, and clear session-specific files for a clean exit.

Can I force clear legacy state files and artifacts after interrupting a workflow?

Yes, you can force clear legacy state files and artifacts by using the forced clear option, which erases all session-specific progress to prepare the environment for a fresh start.

What is the best way to gracefully shut down an Ultrawork session for later resumption?

The best way to gracefully shut down an Ultrawork session is using session-aware cleanup, which interrupts the workflow while preserving progress in state files for future resumption.

Does the cancel skill support autopilot and ralph workflow cancellation?

Yes, the cancel skill supports autopilot and ralph workflow cancellation by intelligently identifying the active session state and triggering the appropriate cleanup process.

Why do I need session-aware state management to stop OMG workflows?

Session-aware state management is required to stop OMG workflows because it ensures graceful shutdown and precise cleanup of active session files without corrupting preserved progress.

When should I use a forced clear instead of a graceful workflow cancellation?

Use a forced clear instead of graceful workflow cancellation when you need to completely erase all state files and legacy artifacts, discarding any resumption data for a fresh environment.